Tosi Platform Status - Incident history https://status.tosi.net Tosi Platform Tue, 6 Oct 2026 09:00:00 +0000 MatchMaker infrastructure Type: Maintenance Affected Components: DE3, FI2, DE2, DE1, FI1, FI3 Sep 22, 06:57:36 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. The maintenance has no impact on existing VPN connections. Clients shall automatically re-connect to MatchMaker instances a couple of times as services are restarted. Type: Maintenance

Affected Components: , , , , ,

<p><small>Sep <var data-var='date'> 22</var>, <var data-var='time'>06:57:36</var> GMT+0</small><br><strong>Identified</strong> - We are planning for a scheduled maintenance during that time. The maintenance has no impact on existing VPN connections. Clients shall automatically re-connect to MatchMaker instances a couple of times as services are restarted..</p> ]]> Tue, 6 Oct 2026 09:00:00 +0000 https://status.tosi.net/maintenance/cmucbnpf01sgl0wpce5u53lbv https://status.tosi.net/maintenance/cmucbnpf01sgl0wpce5u53lbv Tosi Relays Type: Maintenance Duration: 2 days, 8 hours and 35 minutes Affected Components: relay4-eu-north, relay1-au-southwest, relay1-eu-central, relay1-eu-north, relay4-eu-central, relay7-eu-north, relay-as-4-west, relay6-eu-north, relay2-eu-west, relay-us-3-west, relay1-us-east, relay2-us-east, relay2-as-west, relay9.eu-north, relay-jp-1, relay2-as-southeast, relay8.eu-north, relay3-us-east, relay1-eu-west, relay3-eu-north, relay10-usa, relay-as-1-east, relay1-us-central, relay4-us-west, relay-eu-7-north, relay1-eu-northwest, relay-as-3-west, relay2-au-southwest, relay1-sa-east, relay2-eu-north, relay-eu-6-central, relay5-eu-north, relay1-af-south Sep 27, 10:03:26 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. Sep 27, 11:00:01 GMT+0 - Completed - Maintenance completed Type: Maintenance

Duration: 2 days, 8 hours and 35 minutes

Affected Components: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

<p><small>Sep <var data-var='date'> 27</var>, <var data-var='time'>10:03:26</var> GMT+0</small><br><strong>Identified</strong> - We are planning for a scheduled maintenance during that time..</p> <p><small>Sep <var data-var='date'> 27</var>, <var data-var='time'>11:00:01</var> GMT+0</small><br><strong>Completed</strong> - Maintenance completed.</p> ]]> Sun, 27 Sep 2026 11:00:00 +0000 https://status.tosi.net/maintenance/cmujnhvx7047o0wp4f1iwzq4w https://status.tosi.net/maintenance/cmujnhvx7047o0wp4f1iwzq4w Hub update repositories unreachable Type: Incident Duration: 19 hours and 10 minutes Affected Components: Tosi VCL 2.5.x Updates, Tosi VCL 2.6.x Updates, Tosi Hub 3.x Updates, Tosi Hub 4.x Updates Sep 21, 12:30:00 GMT+0 - Identified - Hub update repositories unreachable Sep 22, 07:40:00 GMT+0 - Resolved - Access to Hub update repositories restored. Incident was caused by a storage failure. Type: Incident

Duration: 19 hours and 10 minutes

Affected Components: , , ,

<p><small>Sep <var data-var='date'> 21</var>, <var data-var='time'>12:30:00</var> GMT+0</small><br><strong>Identified</strong> - Hub update repositories unreachable.</p> <p><small>Sep <var data-var='date'> 22</var>, <var data-var='time'>07:40:00</var> GMT+0</small><br><strong>Resolved</strong> - Access to Hub update repositories restored. Incident was caused by a storage failure..</p> ]]> Mon, 21 Sep 2026 12:30:00 +0000 https://status.tosi.net/incident/cmugnvayx000f13n6wv48w9xx https://status.tosi.net/incident/cmugnvayx000f13n6wv48w9xx MatchMaker infrastructure Type: Maintenance Duration: 4 hours Affected Components: FI2, DE3, DE2, DE1, FI1, FI3 Aug 31, 07:29:33 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. The maintenance has no impact on existing VPN connections. Clients shall automatically re-connect to MatchMaker instances a couple of times as services are restarted. Sep 1, 09:00:01 GMT+0 - Identified - Maintenance is now in progress Sep 1, 13:00:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 4 hours

Affected Components: , , , , ,

<p><small>Aug <var data-var='date'> 31</var>, <var data-var='time'>07:29:33</var> GMT+0</small><br><strong>Identified</strong> - We are planning for a scheduled maintenance during that time. The maintenance has no impact on existing VPN connections. Clients shall automatically re-connect to MatchMaker instances a couple of times as services are restarted..</p> <p><small>Sep <var data-var='date'> 1</var>, <var data-var='time'>09:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Sep <var data-var='date'> 1</var>, <var data-var='time'>13:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Tue, 1 Sep 2026 09:00:00 +0000 https://status.tosi.net/maintenance/cmtgx42ky04840ws2l8c4zqon https://status.tosi.net/maintenance/cmtgx42ky04840ws2l8c4zqon Tosi Control unavailability Type: Incident Duration: 1 hour and 35 minutes Affected Components: Tosi Control Aug 17, 04:35:00 GMT+0 - Investigating - We are currently investigating this incident. Aug 17, 06:00:00 GMT+0 - Identified - Issue identified with the database replication Aug 17, 06:10:00 GMT+0 - Resolved - Issue with database replication was resolved. The issues was caused by a replication process reaching maximum configured storage, eventually causing the database to stop accepting any activity. Aug 17, 11:04:55 GMT+0 - Resolved - The incident impacted Tosi Control usage and Clients authentication between **2026-08-16 10:20 EEST and 2026-08-17 09:10 EEST.** Customer data or active connections were not impacted by the outage. Clients may have faced a login issue if access token had expired during the outage. Type: Incident

Duration: 1 hour and 35 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 17</var>, <var data-var='time'>04:35:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Aug <var data-var='date'> 17</var>, <var data-var='time'>06:00:00</var> GMT+0</small><br><strong>Identified</strong> - Issue identified with the database replication.</p> <p><small>Aug <var data-var='date'> 17</var>, <var data-var='time'>06:10:00</var> GMT+0</small><br><strong>Resolved</strong> - Issue with database replication was resolved. The issues was caused by a replication process reaching maximum configured storage, eventually causing the database to stop accepting any activity..</p> <p><small>Aug <var data-var='date'> 17</var>, <var data-var='time'>11:04:55</var> GMT+0</small><br><strong>Resolved</strong> - The incident impacted Tosi Control usage and Clients authentication between **2026-08-16 10:20 EEST and 2026-08-17 09:10 EEST.** Customer data or active connections were not impacted by the outage. Clients may have faced a login issue if access token had expired during the outage..</p> ]]> Mon, 17 Aug 2026 04:35:00 +0000 https://status.tosi.net/incident/cmsx4ff2c002o0rpw8uw4vclq https://status.tosi.net/incident/cmsx4ff2c002o0rpw8uw4vclq MatchMaker infrastructure Type: Maintenance Duration: 2 hours and 45 minutes Affected Components: FI2, FI3, DE3, DE2, DE1, FI1 Aug 3, 07:36:15 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. The maintenance has no impact on existing VPN connections. Clients shall automatically re-connect to MatchMaker instances a couple of times as services are restarted. Aug 4, 09:00:01 GMT+0 - Identified - Maintenance is now in progress Aug 4, 11:45:08 GMT+0 - Completed - Maintenance has completed successfully. Type: Maintenance

Duration: 2 hours and 45 minutes

Affected Components: , , , , ,

<p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>07:36:15</var> GMT+0</small><br><strong>Identified</strong> - We are planning for a scheduled maintenance during that time. The maintenance has no impact on existing VPN connections. Clients shall automatically re-connect to MatchMaker instances a couple of times as services are restarted..</p> <p><small>Aug <var data-var='date'> 4</var>, <var data-var='time'>09:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Aug <var data-var='date'> 4</var>, <var data-var='time'>11:45:08</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> ]]> Tue, 4 Aug 2026 09:00:00 +0000 https://status.tosi.net/maintenance/cmscx0th007lc0kl8povkfof3 https://status.tosi.net/maintenance/cmscx0th007lc0kl8povkfof3 MatchMaker infrastructure Type: Maintenance Duration: 2 hours and 17 minutes Affected Components: FI2, FI3, DE3, DE1, DE2, FI1 Jun 30, 12:44:57 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. The maintenance has no impact on existing VPN connections. Clients shall automatically re-connect to MatchMaker instances a couple of times as services are restarted. Jul 14, 09:00:01 GMT+0 - Identified - Maintenance is now in progress Jul 14, 11:16:39 GMT+0 - Completed - Maintenance has completed successfully. Type: Maintenance

Duration: 2 hours and 17 minutes

Affected Components: , , , , ,

<p><small>Jun <var data-var='date'> 30</var>, <var data-var='time'>12:44:57</var> GMT+0</small><br><strong>Identified</strong> - We are planning for a scheduled maintenance during that time. The maintenance has no impact on existing VPN connections. Clients shall automatically re-connect to MatchMaker instances a couple of times as services are restarted..</p> <p><small>Jul <var data-var='date'> 14</var>, <var data-var='time'>09:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Jul <var data-var='date'> 14</var>, <var data-var='time'>11:16:39</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> ]]> Tue, 14 Jul 2026 09:00:00 +0000 https://status.tosi.net/maintenance/cmr0n2v3b088m0kph2kmz2mbk https://status.tosi.net/maintenance/cmr0n2v3b088m0kph2kmz2mbk Issue Impacting Access to Tosi Control and Tosi Client Login Type: Incident Duration: 10 minutes Affected Components: Tosi Control Jul 8, 10:50:00 GMT+0 - Investigating - A temporary issue was identified that impacted access to Tosi Control and prevented key registration and login for Tosi Client versions 4.4.0 and later. The issue was resolved within 10 minutes. Additional mitigation measures were implemented shortly afterward to help prevent recurrence. Jul 8, 11:00:00 GMT+0 - Resolved - This incident has been resolved. Access to Tosi Control, key registration, and Tosi Client login functionality have been fully restored. Type: Incident

Duration: 10 minutes

Affected Components:

<p><small>Jul <var data-var='date'> 8</var>, <var data-var='time'>10:50:00</var> GMT+0</small><br><strong>Investigating</strong> - A temporary issue was identified that impacted access to Tosi Control and prevented key registration and login for Tosi Client versions 4.4.0 and later. The issue was resolved within 10 minutes. Additional mitigation measures were implemented shortly afterward to help prevent recurrence..</p> <p><small>Jul <var data-var='date'> 8</var>, <var data-var='time'>11:00:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. Access to Tosi Control, key registration, and Tosi Client login functionality have been fully restored..</p> ]]> Wed, 8 Jul 2026 10:50:00 +0000 https://status.tosi.net/incident/cmrc0nxwy01ql0rqj2mvkqw58 https://status.tosi.net/incident/cmrc0nxwy01ql0rqj2mvkqw58 Enabling Tosi Client minimum version requirement Type: Maintenance Duration: 30 minutes Affected Components: FI2, FI3, DE3, DE1, DE2, FI1 Jun 30, 13:04:45 GMT+0 - Identified - We are planning to enable Tosi Client minimum version requirement. Clients will reconnect to MatchMaker as services are restarted. Existing VPN connections will remain active. Please see the knowledge base article for details: <https://serviceportal.tosi.net/serviceportal?id=kb%5Farticle%5Fview&sysparm%5Farticle=KB0010524> Jul 6, 13:00:01 GMT+0 - Identified - Maintenance is now in progress Jul 6, 13:30:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 30 minutes

Affected Components: , , , , ,

<p><small>Jun <var data-var='date'> 30</var>, <var data-var='time'>13:04:45</var> GMT+0</small><br><strong>Identified</strong> - We are planning to enable Tosi Client minimum version requirement. Clients will reconnect to MatchMaker as services are restarted. Existing VPN connections will remain active. Please see the knowledge base article for details: <https://serviceportal.tosi.net/serviceportal?id=kb%5Farticle%5Fview&sysparm%5Farticle=KB0010524>.</p> <p><small>Jul <var data-var='date'> 6</var>, <var data-var='time'>13:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Jul <var data-var='date'> 6</var>, <var data-var='time'>13:30:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Mon, 6 Jul 2026 13:00:00 +0000 https://status.tosi.net/maintenance/cmr0nsblz08ey0kphnkkwrege https://status.tosi.net/maintenance/cmr0nsblz08ey0kphnkkwrege Issue impacting use of Tosi Client and Tosi Control Type: Incident Duration: 1 minute Affected Components: Tosi Control Jul 3, 06:22:00 GMT+0 - Resolved - This incident has been resolved. Jul 3, 05:45:00 GMT+0 - Investigating - There is an issue in Tosi Control that is preventing use of Tosi Client 4.4.0 and newer, and possibly impacting use of Tosi Control. Issue is being resolved as soon as possible. Thank you for your patience. We are working on resolving the problem. Type: Incident

Duration: 1 minute

Affected Components:

<p><small>Jul <var data-var='date'> 3</var>, <var data-var='time'>06:22:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Jul <var data-var='date'> 3</var>, <var data-var='time'>05:45:00</var> GMT+0</small><br><strong>Investigating</strong> - There is an issue in Tosi Control that is preventing use of Tosi Client 4.4.0 and newer, and possibly impacting use of Tosi Control. Issue is being resolved as soon as possible. Thank you for your patience. We are working on resolving the problem..</p> ]]> Fri, 3 Jul 2026 05:45:00 +0000 https://status.tosi.net/incident/cmr4jry6o06up0rqfb2nb5sk1 https://status.tosi.net/incident/cmr4jry6o06up0rqfb2nb5sk1 MatchMaker Infrastructure Type: Maintenance Duration: 2 hours and 40 minutes Affected Components: FI2, FI3, DE3, DE1, DE2, FI1 Jun 2, 09:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. The maintenance has no impact on existing VPN connections. Clients shall automatically re-connect to MatchMaker instances a couple of times as services are restarted. Jun 2, 09:00:01 GMT+0 - Identified - Maintenance is now in progress Jun 2, 11:40:26 GMT+0 - Completed - Maintenance has completed successfully. Type: Maintenance

Duration: 2 hours and 40 minutes

Affected Components: , , , , ,

<p><small>Jun <var data-var='date'> 2</var>, <var data-var='time'>09:00:00</var> GMT+0</small><br><strong>Identified</strong> - We are planning for a scheduled maintenance during that time. The maintenance has no impact on existing VPN connections. Clients shall automatically re-connect to MatchMaker instances a couple of times as services are restarted..</p> <p><small>Jun <var data-var='date'> 2</var>, <var data-var='time'>09:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Jun <var data-var='date'> 2</var>, <var data-var='time'>11:40:26</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> ]]> Tue, 2 Jun 2026 09:00:00 +0000 https://status.tosi.net/maintenance/cmpqwosdi06tvqjcx47qsnk57 https://status.tosi.net/maintenance/cmpqwosdi06tvqjcx47qsnk57 Relay service maintenance Type: Maintenance Duration: 1 minute Affected Components: relay4-eu-north, relay1-au-southwest, relay1-eu-central, relay1-eu-north, relay4-eu-central, relay7-eu-north, relay-as-4-west, relay2-eu-west, relay-us-3-west, relay1-us-east, relay2-us-east, relay-jp-1, relay2-as-southeast, relay8.eu-north, relay3-us-east, relay1-eu-west, relay3-eu-north, relay10-usa, relay-as-1-east, relay1-us-central, relay4-us-west, relay-eu-7-north, relay1-eu-northwest, relay-as-3-west, relay2-au-southwest, relay1-sa-east, relay2-eu-north, relay-eu-6-central, relay5-eu-north, relay9.eu-north, relay6-eu-north, relay2-as-west, relay1-af-south May 31, 11:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. May 31, 11:00:01 GMT+0 - Completed - Maintenance is now in progress Type: Maintenance

Duration: 1 minute

Affected Components: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

<p><small>May <var data-var='date'> 31</var>, <var data-var='time'>11:00:00</var> GMT+0</small><br><strong>Identified</strong> - We are planning for a scheduled maintenance during that time..</p> <p><small>May <var data-var='date'> 31</var>, <var data-var='time'>11:00:01</var> GMT+0</small><br><strong>Completed</strong> - Maintenance is now in progress.</p> ]]> Sun, 31 May 2026 11:00:00 +0000 https://status.tosi.net/maintenance/cmptl689y07ubnpz3bwek13ov https://status.tosi.net/maintenance/cmptl689y07ubnpz3bwek13ov Tosi Control login is working very slowly Type: Incident Duration: 1 hour and 27 minutes Affected Components: Tosi Control May 26, 05:00:38 GMT+0 - Identified - Tosi Control login is currently working very slowly, this is impacting the Tosi Control service itself, and Tosi Client users with Tosi Client 4.4.0 and newer. Issue is being resolved as soon as possible. Thank you for your patience. We are working on resolving the problem. May 26, 06:27:42 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 1 hour and 27 minutes

Affected Components:

<p><small>May <var data-var='date'> 26</var>, <var data-var='time'>05:00:38</var> GMT+0</small><br><strong>Identified</strong> - Tosi Control login is currently working very slowly, this is impacting the Tosi Control service itself, and Tosi Client users with Tosi Client 4.4.0 and newer. Issue is being resolved as soon as possible. Thank you for your patience. We are working on resolving the problem..</p> <p><small>May <var data-var='date'> 26</var>, <var data-var='time'>06:27:42</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Tue, 26 May 2026 05:00:38 +0000 https://status.tosi.net/incident/cmpm8tgr608m7nrm7l99kybs0 https://status.tosi.net/incident/cmpm8tgr608m7nrm7l99kybs0 Matchmaker Infrastructure Type: Maintenance Duration: 2 hours and 56 minutes Affected Components: FI2, DE1, DE2, FI1 May 5, 09:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. The maintenance has no impact on existing VPN connections. Clients shall automatically re-connect to MatchMaker instances a couple of times as services are restarted. May 5, 09:00:01 GMT+0 - Identified - Maintenance is now in progress May 5, 11:56:09 GMT+0 - Completed - Maintenance has completed successfully. May 5, 12:00:00 GMT+0 - Completed - Schedule MatchMaker maintenance is now completed. All systems operational. Type: Maintenance

Duration: 2 hours and 56 minutes

Affected Components: , , ,

<p><small>May <var data-var='date'> 5</var>, <var data-var='time'>09:00:00</var> GMT+0</small><br><strong>Identified</strong> - We are planning for a scheduled maintenance during that time. The maintenance has no impact on existing VPN connections. Clients shall automatically re-connect to MatchMaker instances a couple of times as services are restarted..</p> <p><small>May <var data-var='date'> 5</var>, <var data-var='time'>09:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>May <var data-var='date'> 5</var>, <var data-var='time'>11:56:09</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> <p><small>May <var data-var='date'> 5</var>, <var data-var='time'>12:00:00</var> GMT+0</small><br><strong>Completed</strong> - Schedule MatchMaker maintenance is now completed. All systems operational..</p> ]]> Tue, 5 May 2026 09:00:00 +0000 https://status.tosi.net/maintenance/cmoqxly7b04m6njamwhy5hrws https://status.tosi.net/maintenance/cmoqxly7b04m6njamwhy5hrws MatchMaker Infrastucture Type: Maintenance Duration: 3 hours and 54 minutes Affected Components: FI2, DE1, DE2, FI1 Apr 26, 07:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. There will be short break when services are restarted. Clients shall automatically re-connect to MatchMaker instances a couple of times as services are restarted. Apr 26, 07:00:01 GMT+0 - Identified - Maintenance is now in progress Apr 26, 10:53:48 GMT+0 - Completed - Schedule MatchMaker maintenance is now completed. All systems operational. Type: Maintenance

Duration: 3 hours and 54 minutes

Affected Components: , , ,

<p><small>Apr <var data-var='date'> 26</var>, <var data-var='time'>07:00:00</var> GMT+0</small><br><strong>Identified</strong> - We are planning for a scheduled maintenance during that time. There will be short break when services are restarted. Clients shall automatically re-connect to MatchMaker instances a couple of times as services are restarted. .</p> <p><small>Apr <var data-var='date'> 26</var>, <var data-var='time'>07:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Apr <var data-var='date'> 26</var>, <var data-var='time'>10:53:48</var> GMT+0</small><br><strong>Completed</strong> - Schedule MatchMaker maintenance is now completed. All systems operational..</p> ]]> Sun, 26 Apr 2026 07:00:00 +0000 https://status.tosi.net/maintenance/cmnribo6n0bu73y8avroskt1k https://status.tosi.net/maintenance/cmnribo6n0bu73y8avroskt1k MatchMaker Infrastructure Type: Maintenance Duration: 1 hour Affected Components: FI2, DE1, DE2, FI1 Apr 16, 09:45:00 GMT+0 - Identified - We are planning for a short maintenance. There might be short break when services are restarted. Clients shall automatically re-connect to MatchMaker instances a couple of times as services are restarted. Apr 16, 09:45:01 GMT+0 - Identified - Maintenance is now in progress Apr 16, 10:45:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 1 hour

Affected Components: , , ,

<p><small>Apr <var data-var='date'> 16</var>, <var data-var='time'>09:45:00</var> GMT+0</small><br><strong>Identified</strong> - We are planning for a short maintenance. There might be short break when services are restarted. Clients shall automatically re-connect to MatchMaker instances a couple of times as services are restarted..</p> <p><small>Apr <var data-var='date'> 16</var>, <var data-var='time'>09:45:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Apr <var data-var='date'> 16</var>, <var data-var='time'>10:45:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Thu, 16 Apr 2026 09:45:00 +0000 https://status.tosi.net/maintenance/cmo1ajcto09k0vh8j2n6ykf1p https://status.tosi.net/maintenance/cmo1ajcto09k0vh8j2n6ykf1p MatchMaker infrastructure issues Type: Incident Duration: 12 hours and 49 minutes Affected Components: FI2, DE1, DE2, FI1 Apr 16, 05:46:11 GMT+0 - Resolved - This incident has been resolved. The outage was caused by a network failure at our data center provider, which took a critical server offline. A full RCA is in the works and due for delivery later today. Apr 16, 16:39:41 GMT+0 - Postmortem - ## **Executive summary** On 15 April, a network switch failure at our hosting provider’s data centre caused a disruption impacting all MatchMakers. Customers were unable to establish new VPN connections. Existing VPN connections were not impacted and remained active throughout the incident. The service degradation lasted approximately five hours, from **18:50 to 00:10 (UTC+3)**, after which the platform resumed normal operation. The issue was detected via automated alerts shortly after onset. On‑call engineers responded immediately, escalated the incident to the hosting provider, and worked to stabilise the service. Customer updates were provided via the public status page and email communications. The root cause was a network switch failure at the hosting provider’s data centre. This led to excessive reconnection attempts that exceeded other servers capacity for new connections. To prevent recurrence, we are eliminating single points of failure through duplicated connectivity, increasing system capacity and redundancy, and improving failover behaviour and escalation processes with the hosting provider. **Root Cause Analysis report** All systems were running normally until the incident. **Fault** At 18:52 (UTC+3), a network switch at the hosting data centre failed, isolating a critical MatchMaker server and blocking all traffic to and from it. Clients attempted to reconnect to other MatchMaker (MM) servers, triggering a sudden load spike. Those servers became unresponsive in sequence, resulting in all MM servers becoming unavailable. **Impact** Following the switch failure, remaining MM servers received a surge of reconnection attempts and progressively hung. Active MM connections dropped until recovery commenced about five hours later, once the isolated server was restored. Customers could not start new VPN connections during the outage. Existing connections stayed up. Impact was greater for US-based users due to local business hours. **Timeline** 18:52 – Network switch failed; critical MatchMaker server isolated (UTC+3). 19:00 – Monitoring alert to on‑call; investigation started (UTC+3). 19:27 – Public status page reported widespread MatchMaker unavailability (UTC+3). 22:43 – Customer notification sent via email (UTC+3). 23:08 – Network configuration corrected on the critical server (UTC+3). 23:56 – All servers accepting connections again (UTC+3). 00:10 – Connections stabilised; public status page updated (UTC+3). 00:16 – Recovery notification emailed to customers (UTC+3). 2026-04-16 (UTC+3) 08:45 – Public status page incident closed (UTC+3). **Follow-up** * Capacity & resilience: Add additional MM capacity and headroom; improve load balancing. * Failover: Improve network connectivity; validate automatic failover under load. * Process & comms: Speed up external comms and clarify roles and processes; ensure timely status page and email updates. Apr 15, 16:57:00 GMT+0 - Investigating - Issues with MatchMaker infrastructure, impacting new connection creation Apr 15, 20:37:10 GMT+0 - Identified - We have identified the root cause and are working on restoring all connectivity Apr 15, 21:11:56 GMT+0 - Monitoring - Issue should now be resolved and we are monitoring the aftermath Type: Incident

Duration: 12 hours and 49 minutes

Affected Components: , , ,

<p><small>Apr <var data-var='date'> 16</var>, <var data-var='time'>05:46:11</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. The outage was caused by a network failure at our data center provider, which took a critical server offline. A full RCA is in the works and due for delivery later today..</p> <p><small>Apr <var data-var='date'> 16</var>, <var data-var='time'>16:39:41</var> GMT+0</small><br><strong>Postmortem</strong> - ## **Executive summary** On 15 April, a network switch failure at our hosting provider’s data centre caused a disruption impacting all MatchMakers. Customers were unable to establish new VPN connections. Existing VPN connections were not impacted and remained active throughout the incident. The service degradation lasted approximately five hours, from **18:50 to 00:10 (UTC+3)**, after which the platform resumed normal operation. The issue was detected via automated alerts shortly after onset. On‑call engineers responded immediately, escalated the incident to the hosting provider, and worked to stabilise the service. Customer updates were provided via the public status page and email communications. The root cause was a network switch failure at the hosting provider’s data centre. This led to excessive reconnection attempts that exceeded other servers capacity for new connections. To prevent recurrence, we are eliminating single points of failure through duplicated connectivity, increasing system capacity and redundancy, and improving failover behaviour and escalation processes with the hosting provider. **Root Cause Analysis report** All systems were running normally until the incident. **Fault** At 18:52 (UTC+3), a network switch at the hosting data centre failed, isolating a critical MatchMaker server and blocking all traffic to and from it. Clients attempted to reconnect to other MatchMaker (MM) servers, triggering a sudden load spike. Those servers became unresponsive in sequence, resulting in all MM servers becoming unavailable. **Impact** Following the switch failure, remaining MM servers received a surge of reconnection attempts and progressively hung. Active MM connections dropped until recovery commenced about five hours later, once the isolated server was restored. Customers could not start new VPN connections during the outage. Existing connections stayed up. Impact was greater for US-based users due to local business hours. **Timeline** 18:52 – Network switch failed; critical MatchMaker server isolated (UTC+3). 19:00 – Monitoring alert to on‑call; investigation started (UTC+3). 19:27 – Public status page reported widespread MatchMaker unavailability (UTC+3). 22:43 – Customer notification sent via email (UTC+3). 23:08 – Network configuration corrected on the critical server (UTC+3). 23:56 – All servers accepting connections again (UTC+3). 00:10 – Connections stabilised; public status page updated (UTC+3). 00:16 – Recovery notification emailed to customers (UTC+3). 2026-04-16 (UTC+3) 08:45 – Public status page incident closed (UTC+3). **Follow-up** * Capacity & resilience: Add additional MM capacity and headroom; improve load balancing. * Failover: Improve network connectivity; validate automatic failover under load. * Process & comms: Speed up external comms and clarify roles and processes; ensure timely status page and email updates..</p> <p><small>Apr <var data-var='date'> 15</var>, <var data-var='time'>16:57:00</var> GMT+0</small><br><strong>Investigating</strong> - Issues with MatchMaker infrastructure, impacting new connection creation.</p> <p><small>Apr <var data-var='date'> 15</var>, <var data-var='time'>20:37:10</var> GMT+0</small><br><strong>Identified</strong> - We have identified the root cause and are working on restoring all connectivity.</p> <p><small>Apr <var data-var='date'> 15</var>, <var data-var='time'>21:11:56</var> GMT+0</small><br><strong>Monitoring</strong> - Issue should now be resolved and we are monitoring the aftermath.</p> ]]> Wed, 15 Apr 2026 16:57:00 +0000 https://status.tosi.net/incident/cmo0ieooa02pq38fduajqqc4m https://status.tosi.net/incident/cmo0ieooa02pq38fduajqqc4m de1.mm.tosibox.com is back up Type: Incident Affected Components: FI2, DE1, DE2, FI1 Apr 15, 16:29:52 GMT+0 - Investigating - de1.mm.tosibox.com is down at the moment. This incident was automatically created by Instatus monitoring. Apr 15, 17:37:36 GMT+0 - Investigating - We are currently investigating this incident. Apr 15, 19:05:38 GMT+0 - Resolved - DE1 is back up. This incident was automatically resolved by Instatus monitoring. Type: Incident

Affected Components: , , ,

<p><small>Apr <var data-var='date'> 15</var>, <var data-var='time'>16:29:52</var> GMT+0</small><br><strong>Investigating</strong> - de1.mm.tosibox.com is down at the moment. This incident was automatically created by Instatus monitoring..</p> <p><small>Apr <var data-var='date'> 15</var>, <var data-var='time'>17:37:36</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Apr <var data-var='date'> 15</var>, <var data-var='time'>19:05:38</var> GMT+0</small><br><strong>Resolved</strong> - DE1 is back up. This incident was automatically resolved by Instatus monitoring..</p> ]]> Wed, 15 Apr 2026 16:29:52 +0000 https://status.tosi.net/incident/cmo09ncjf0hh058u9xsb2dd47 https://status.tosi.net/incident/cmo09ncjf0hh058u9xsb2dd47 de2.mm.tosibox.com is back up Type: Incident Apr 15, 16:22:23 GMT+0 - Investigating - de2.mm.tosibox.com is down at the moment. This incident was automatically created by Instatus monitoring. Apr 15, 18:56:52 GMT+0 - Resolved - DE2 is back up. This incident was automatically resolved by Instatus monitoring. Type: Incident

<p><small>Apr <var data-var='date'> 15</var>, <var data-var='time'>16:22:23</var> GMT+0</small><br><strong>Investigating</strong> - de2.mm.tosibox.com is down at the moment. This incident was automatically created by Instatus monitoring..</p> <p><small>Apr <var data-var='date'> 15</var>, <var data-var='time'>18:56:52</var> GMT+0</small><br><strong>Resolved</strong> - DE2 is back up. This incident was automatically resolved by Instatus monitoring..</p> ]]> Wed, 15 Apr 2026 16:22:22 +0000 https://status.tosi.net/incident/cmo09dpqw0ieuupwlzom480ss https://status.tosi.net/incident/cmo09dpqw0ieuupwlzom480ss hel2.mm.tosibox.com is back up Type: Incident Apr 15, 16:16:30 GMT+0 - Investigating - hel2.mm.tosibox.com is down at the moment. This incident was automatically created by Instatus monitoring. Apr 15, 20:19:44 GMT+0 - Resolved - FI2 is back up. This incident was automatically resolved by Instatus monitoring. Type: Incident

<p><small>Apr <var data-var='date'> 15</var>, <var data-var='time'>16:16:30</var> GMT+0</small><br><strong>Investigating</strong> - hel2.mm.tosibox.com is down at the moment. This incident was automatically created by Instatus monitoring..</p> <p><small>Apr <var data-var='date'> 15</var>, <var data-var='time'>20:19:44</var> GMT+0</small><br><strong>Resolved</strong> - FI2 is back up. This incident was automatically resolved by Instatus monitoring..</p> ]]> Wed, 15 Apr 2026 16:16:29 +0000 https://status.tosi.net/incident/cmo09657i0e30y3isxpm937m7 https://status.tosi.net/incident/cmo09657i0e30y3isxpm937m7 tb3.tosibox.com is back up Type: Incident Apr 15, 15:57:41 GMT+0 - Investigating - tb3.tosibox.com is down at the moment. This incident was automatically created by Instatus monitoring. Apr 15, 21:09:08 GMT+0 - Resolved - FI1 is back up. This incident was automatically resolved by Instatus monitoring. Type: Incident

<p><small>Apr <var data-var='date'> 15</var>, <var data-var='time'>15:57:41</var> GMT+0</small><br><strong>Investigating</strong> - tb3.tosibox.com is down at the moment. This incident was automatically created by Instatus monitoring..</p> <p><small>Apr <var data-var='date'> 15</var>, <var data-var='time'>21:09:08</var> GMT+0</small><br><strong>Resolved</strong> - FI1 is back up. This incident was automatically resolved by Instatus monitoring..</p> ]]> Wed, 15 Apr 2026 15:57:40 +0000 https://status.tosi.net/incident/cmo08hy060exgbt0mk3uppp5v https://status.tosi.net/incident/cmo08hy060exgbt0mk3uppp5v MatchMaker instance database Type: Incident Duration: 3 days, 3 hours and 28 minutes Affected Components: FI2, DE1, DE2, FI1 Apr 7, 13:25:00 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Apr 7, 09:40:00 GMT+0 - Identified - During the monthly maintenance window, we identified an issue with the database instance of one MatchMaker. The full impact of the issue is still under investigation. We implemented a fix and are currently monitoring the result. A detailed analysis shall be provided once the root cause is fully clear. Apr 9, 12:36:47 GMT+0 - Monitoring - Updated the impact based on current understanding of the problem visibility to clients. From clients perspective, all services should be operational. We are still monitoring the issue. Apr 10, 13:07:39 GMT+0 - Resolved - Environment is considered stable with a workaround in place. We have scheduled for a new maintenance break to restore the system into a state where the current workaround is not needed anymore. Type: Incident

Duration: 3 days, 3 hours and 28 minutes

Affected Components: , , ,

<p><small>Apr <var data-var='date'> 7</var>, <var data-var='time'>13:25:00</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Apr <var data-var='date'> 7</var>, <var data-var='time'>09:40:00</var> GMT+0</small><br><strong>Identified</strong> - During the monthly maintenance window, we identified an issue with the database instance of one MatchMaker. The full impact of the issue is still under investigation. We implemented a fix and are currently monitoring the result. A detailed analysis shall be provided once the root cause is fully clear..</p> <p><small>Apr <var data-var='date'> 9</var>, <var data-var='time'>12:36:47</var> GMT+0</small><br><strong>Monitoring</strong> - Updated the impact based on current understanding of the problem visibility to clients. From clients perspective, all services should be operational. We are still monitoring the issue. .</p> <p><small>Apr <var data-var='date'> 10</var>, <var data-var='time'>13:07:39</var> GMT+0</small><br><strong>Resolved</strong> - Environment is considered stable with a workaround in place. We have scheduled for a new maintenance break to restore the system into a state where the current workaround is not needed anymore..</p> ]]> Tue, 7 Apr 2026 09:40:00 +0000 https://status.tosi.net/incident/cmnowrsj813mpyn6v0tjvhiqg https://status.tosi.net/incident/cmnowrsj813mpyn6v0tjvhiqg Matchmaker Infrastructure Type: Maintenance Duration: 4 hours and 40 minutes Affected Components: FI2, DE1, DE2, FI1 Apr 7, 09:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. The maintenance has no impact on existing VPN connections. Clients shall automatically re-connect to MatchMaker instances a couple of times as services are restarted. Apr 7, 09:00:01 GMT+0 - Identified - Maintenance is now in progress Apr 7, 13:40:00 GMT+0 - Completed - Schedule MatchMaker maintenance is now completed. All systems operational. There was an issue faced during maintenance, for which we've created a separate incident. Type: Maintenance

Duration: 4 hours and 40 minutes

Affected Components: , , ,

<p><small>Apr <var data-var='date'> 7</var>, <var data-var='time'>09:00:00</var> GMT+0</small><br><strong>Identified</strong> - We are planning for a scheduled maintenance during that time. The maintenance has no impact on existing VPN connections. Clients shall automatically re-connect to MatchMaker instances a couple of times as services are restarted..</p> <p><small>Apr <var data-var='date'> 7</var>, <var data-var='time'>09:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Apr <var data-var='date'> 7</var>, <var data-var='time'>13:40:00</var> GMT+0</small><br><strong>Completed</strong> - Schedule MatchMaker maintenance is now completed. All systems operational. There was an issue faced during maintenance, for which we've created a separate incident..</p> ]]> Tue, 7 Apr 2026 09:00:00 +0000 https://status.tosi.net/maintenance/cmnocagpi00fmdb8cqixpqivn https://status.tosi.net/maintenance/cmnocagpi00fmdb8cqixpqivn MatchMaker Infrastructure Type: Maintenance Duration: 3 hours Affected Components: , FI2, DE1, DE2, relay3-us-east, relay10-usa, FI1, MatchMaker → Mar 3, 10:00:01 GMT+0 - Identified - Maintenance is now in progress Mar 3, 10:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. There will be short break to iOS - client connections when services are restarted. The maintenance has no impact on other existing VPN connections. Clients shall automatically re-connect to MatchMaker instances a couple of times as services are restarted. Mar 3, 13:00:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 3 hours

Affected Components: , , , , , ,

<p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>10:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>10:00:00</var> GMT+0</small><br><strong>Identified</strong> - We are planning for a scheduled maintenance during that time. There will be short break to iOS - client connections when services are restarted. The maintenance has no impact on other existing VPN connections. Clients shall automatically re-connect to MatchMaker instances a couple of times as services are restarted..</p> <p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>13:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Tue, 3 Mar 2026 10:00:00 +0000 https://status.tosi.net/maintenance/cmm99ihis08y8v3hsylli5fqu https://status.tosi.net/maintenance/cmm99ihis08y8v3hsylli5fqu Connectivity issue in Tosi Client for iOS version 2.5.0 Type: Incident Duration: 30 days, 22 hours and 20 minutes Feb 20, 15:43:05 GMT+0 - Investigating - We are currently investigating an issue affecting some users of the Tosi Client version 2.5.0 for iOS. In certain cases, the client reports a successful connection to the Gateway, but accessing services in a web browser through that connection may fail. This issue is limited to the iOS version of the client; Android users are not affected. Only a subset of iOS users appears to be impacted, and most customers continue to operate normally. We do not currently have a workaround or fix available, but our engineering team is actively working on the issue. We are planning a 2.5.1 hotfix release to address the problem as soon as a verified fix is available. Mar 3, 14:52:42 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Mar 23, 14:02:41 GMT+0 - Identified - We’ve identified the root cause and implemented a partial server-side fix. Tosi Client for iOS users do not need to take any action. We are still investigating connectivity issues on certain operator networks that impact limited amount of users and expect to deploy a final server-side fix shortly. Apr 26, 13:02:00 GMT+0 - Resolved - Tosi Client for iOS version 2.5.1 has been released with a fix for this issue. This incident has been resolved. Type: Incident

Duration: 30 days, 22 hours and 20 minutes

<p><small>Feb <var data-var='date'> 20</var>, <var data-var='time'>15:43:05</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating an issue affecting some users of the Tosi Client version 2.5.0 for iOS. In certain cases, the client reports a successful connection to the Gateway, but accessing services in a web browser through that connection may fail. This issue is limited to the iOS version of the client; Android users are not affected. Only a subset of iOS users appears to be impacted, and most customers continue to operate normally. We do not currently have a workaround or fix available, but our engineering team is actively working on the issue. We are planning a 2.5.1 hotfix release to address the problem as soon as a verified fix is available..</p> <p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>14:52:42</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Mar <var data-var='date'> 23</var>, <var data-var='time'>14:02:41</var> GMT+0</small><br><strong>Identified</strong> - We’ve identified the root cause and implemented a partial server-side fix. Tosi Client for iOS users do not need to take any action. We are still investigating connectivity issues on certain operator networks that impact limited amount of users and expect to deploy a final server-side fix shortly..</p> <p><small>Apr <var data-var='date'> 26</var>, <var data-var='time'>13:02:00</var> GMT+0</small><br><strong>Resolved</strong> - Tosi Client for iOS version 2.5.1 has been released with a fix for this issue. This incident has been resolved..</p> ]]> Fri, 20 Feb 2026 15:43:05 +0000 https://status.tosi.net/incident/cmlv277fq000q8n90nglvnmw6 https://status.tosi.net/incident/cmlv277fq000q8n90nglvnmw6 relay1-af-south.tosibox.com is down Type: Incident Affected Components: relay1-af-south Feb 14, 20:34:56 GMT+0 - Investigating - is down at the moment. This incident was automatically created by Instatus monitoring. Feb 14, 20:59:32 GMT+0 - Resolved - relay1-af-south is back up. This incident was automatically resolved by Instatus monitoring. Feb 15, 06:08:34 GMT+0 - Resolved - Investigating the root cause. No impact on VPN connections as other relays were fully operational. Feb 16, 08:48:56 GMT+0 - Resolved - The issue was caused by an outage in the service provider’s network. Type: Incident

Affected Components:

<p><small>Feb <var data-var='date'> 14</var>, <var data-var='time'>20:34:56</var> GMT+0</small><br><strong>Investigating</strong> - is down at the moment. This incident was automatically created by Instatus monitoring..</p> <p><small>Feb <var data-var='date'> 14</var>, <var data-var='time'>20:59:32</var> GMT+0</small><br><strong>Resolved</strong> - relay1-af-south is back up. This incident was automatically resolved by Instatus monitoring..</p> <p><small>Feb <var data-var='date'> 15</var>, <var data-var='time'>06:08:34</var> GMT+0</small><br><strong>Resolved</strong> - Investigating the root cause. No impact on VPN connections as other relays were fully operational..</p> <p><small>Feb <var data-var='date'> 16</var>, <var data-var='time'>08:48:56</var> GMT+0</small><br><strong>Resolved</strong> - The issue was caused by an outage in the service provider’s network..</p> ]]> Sat, 14 Feb 2026 20:34:56 +0000 https://status.tosi.net/incident/cmlmrze9b004ry3nhsdcq07tf https://status.tosi.net/incident/cmlmrze9b004ry3nhsdcq07tf relay-as-3-west.tosibox.com is down Type: Incident Affected Components: relay-as-3-west Feb 4, 04:49:36 GMT+0 - Identified - We are continuing to work on a fix for this incident. Other relays operational. No impact on service. Feb 4, 06:14:05 GMT+0 - Resolved - relay-as-3-west is back up. This incident was automatically resolved by Instatus monitoring. Feb 4, 08:57:41 GMT+0 - Resolved - Issue was caused by a routing problem in the Data Center where the relay is hosted. Feb 4, 00:09:01 GMT+0 - Investigating - is down at the moment. This incident was automatically created by Instatus monitoring. Type: Incident

Affected Components:

<p><small>Feb <var data-var='date'> 4</var>, <var data-var='time'>04:49:36</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident. Other relays operational. No impact on service..</p> <p><small>Feb <var data-var='date'> 4</var>, <var data-var='time'>06:14:05</var> GMT+0</small><br><strong>Resolved</strong> - relay-as-3-west is back up. This incident was automatically resolved by Instatus monitoring..</p> <p><small>Feb <var data-var='date'> 4</var>, <var data-var='time'>08:57:41</var> GMT+0</small><br><strong>Resolved</strong> - Issue was caused by a routing problem in the Data Center where the relay is hosted..</p> <p><small>Feb <var data-var='date'> 4</var>, <var data-var='time'>00:09:01</var> GMT+0</small><br><strong>Investigating</strong> - is down at the moment. This incident was automatically created by Instatus monitoring..</p> ]]> Wed, 4 Feb 2026 00:09:01 +0000 https://status.tosi.net/incident/cml79scq8000fnrjsfkt0wf56 https://status.tosi.net/incident/cml79scq8000fnrjsfkt0wf56 MatchMaker Infrastructure Type: Maintenance Duration: 3 hours Affected Components: , FI2, DE1, DE2, FI1, MatchMaker → Feb 3, 10:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. The maintenance has no impact on existing VPN connections. Clients shall automatically re-connect to MatchMaker instances a couple of times as services are restarted. Feb 3, 10:00:01 GMT+0 - Identified - Maintenance is now in progress Feb 3, 13:00:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 3 hours

Affected Components: , , , ,

<p><small>Feb <var data-var='date'> 3</var>, <var data-var='time'>10:00:00</var> GMT+0</small><br><strong>Identified</strong> - We are planning for a scheduled maintenance during that time. The maintenance has no impact on existing VPN connections. Clients shall automatically re-connect to MatchMaker instances a couple of times as services are restarted..</p> <p><small>Feb <var data-var='date'> 3</var>, <var data-var='time'>10:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Feb <var data-var='date'> 3</var>, <var data-var='time'>13:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Tue, 3 Feb 2026 10:00:00 +0000 https://status.tosi.net/maintenance/cml69w92w01sejr0d0cbjya2w https://status.tosi.net/maintenance/cml69w92w01sejr0d0cbjya2w