Mitto Outage History

Started Oct 16, 2026, 12:30 PM UTC· resolved Oct 16, 2026, 12:30 PM UTC

1. resolved Oct 16, 2026, 12:30 PM UTC

   Hi Team. We received the following update related to Sender ID registrations in Finland: Until now, unregistered Sender IDs were being delivered as “Tuntematon”. Traficom Regulation M28-L requires telecommunication operators to replace the previously used “Tuntematon” sender ID with “spam” from 2 November 2026. All unregistered sender IDs will be converted to “Roskaposti” (spam) only when an unauthorized sender ID is used in message traffic. We kindly ask you to inform your clients to pay particular attention to Sender ID authorization when a Finnish telephone number is used as the sender ID (Finnish telephone number used as numeric Sender ID). Under the Regulation, messages sent from an unauthorized number will be blocked from 2 November 2026. The operator recommends blocking such messages before they are submitted through their interface. Kind regards.

Read the full incident report →

Started Oct 06, 2026, 10:19 AM UTC· resolved Oct 06, 2026, 11:48 AM UTC

1. investigating Oct 06, 2026, 10:19 AM UTC

   Please be advised that currently there is a degradation in delivery towards Iran, RighTel (432-20) You may experience irregular delivery with inconsistent delivery times while sending towards the specified network. Our dedicated team is working with the MNO to resolve the situation at hand, no estimated time of resolution can be provided yet. Start: 2026-10-06 11:20 CEST End: Ongoing Thank you for understanding.

2. investigating Oct 06, 2026, 11:46 AM UTC

   We are continuing to investigate this issue.

3. resolved Oct 06, 2026, 11:48 AM UTC

   This degradation has been resolved. We will continue to monitor the traffic with the operator to ensure no further issues are observed. Start: 2026-06-16 07:00 CEST End: 2026-06-16 10:15 CEST Thank you for understanding.

Read the full incident report →

Started Oct 04, 2026, 04:34 PM UTC· resolved Oct 04, 2026, 04:34 PM UTC

1. resolved Oct 04, 2026, 04:34 PM UTC

   NEW NUMBER RANGES Destination: Iran, ShatelMobile MCC: 432 MNC: 08 Please be advised that Iran, ShatelMobile (432-08) added a new subscriber number range. New number ranges: Country Code (CC) National Destination Code (NDC) SN Range Start SN Range Stop 98 99810 68300 68399 Would you please implement new number ranges in your system? Thank you in advance.

Read the full incident report →

Started Sep 21, 2026, 01:07 AM UTC· resolved Sep 21, 2026, 03:20 AM UTC

1. investigating Sep 21, 2026, 01:07 AM UTC

   Please be advised that currently there is a degradation in delivery towards Iran, Irancell (432-35) You may experience irregular delivery with inconsistent delivery times while sending towards the specified network. Our dedicated team is working with the MNO to resolve the situation at hand, no estimated time of resolution can be provided yet. Start: 2026-09-21 00:30 CEST End: Ongoing Thank you for understanding.

2. resolved Sep 21, 2026, 03:20 AM UTC

   This degradation has been resolved. We will continue to monitor the traffic with the operator to ensure no further issues are observed. Start: 2026-09-21 00:30 CEST End: 2026-09-21 03:20 CEST Thank you for understanding.

Read the full incident report →

Started Sep 18, 2026, 03:08 AM UTC· resolved Sep 29, 2026, 09:13 AM UTC

1. investigating Sep 18, 2026, 03:08 AM UTC

   Please be advised that currently there is a degradation in delivery towards Iran, RighTel (432-20) You may experience irregular delivery with inconsistent delivery times while sending towards the specified network. Our dedicated team is working with the MNO to resolve the situation at hand, no estimated time of resolution can be provided yet. Start: 2026-09-18 04:30 CEST End: Ongoing Thank you for understanding.

2. resolved Sep 29, 2026, 09:13 AM UTC

   This degradation has been resolved. We will continue to monitor the traffic with the operator to ensure no further issues are observed. Start: 2026-09-18 04:30 CEST End: 2026-09-29 10:30 CEST Thank you for understanding.

Read the full incident report →

Started Aug 15, 2026, 04:02 AM UTC· resolved Aug 24, 2026, 07:08 AM UTC

1. investigating Aug 15, 2026, 04:10 AM UTC

   Service Impact: *Outage ongoing in Data Center*. Start: 2026-08-15 05:40 0:00 CEST End: Ongoing Description: We are currently experiencing a critical outage affecting services hosted in our primary data center. Our engineering and infrastructure teams are actively investigating the root cause and working to restore full operational status as quickly as possible. Customer impact: Customers may experience service degradation, intermittent connectivity, or a complete inability to access hosted services and applications. Updates will be provided as soon as further information becomes available. Thank you for understanding.

2. identified Aug 15, 2026, 06:25 AM UTC

   Service Restoration Update - 2026-08-15 07:57 CEST Mitigation & Planned Actions • Issue investigation — Completed • Leak closure — Completed • Chiller water refilling — In Progress • Additional hose installation to accelerate refilling process — In Progress • Mobile dehumidifiers deployment — Completed • Water clearing from affected areas — In Progress • Vendor engagement — Enroute to the site (ETA 20 minutes) • Fire protection vendor activation — Enroute to the site

3. identified Aug 15, 2026, 06:34 AM UTC

   Service Restoration Update - 2026-08-15 06:32 CEST Mitigation & Planned Actions • Issue investigation — Completed • Leak closure — Completed • Chiller water refilling — In Progress • Mobile dehumidifier deployment — Completed • Water clearing from affected areas — In Progress • Vendor engagement — In Progress (ETA one hour)

4. identified Aug 15, 2026, 06:35 AM UTC

   Service Restoration Update - 2026-08-15 06:58 CEST Mitigation & Planned Actions • Issue investigation — Completed • Leak closure — Completed • Chiller water refilling — In Progress • Additional hose installation to accelerate refilling process — In Progress • Mobile dehumidifier deployment — Completed • Water clearing from affected areas — In Progress • Vendor engagement — In Progress (ETA one hour)

5. identified Aug 15, 2026, 06:36 AM UTC

   Service Restoration Update - 2026-08-15 07:29 CEST Mitigation & Planned Actions • Issue investigation — Completed • Leak closure — Completed • Chiller water refilling — In Progress • Additional hose installation to accelerate refilling process — In Progress • Mobile dehumidifiers deployment — Completed • Water clearing from affected areas — In Progress • Vendor engagement — In Progress (ETA 20 minutes) • Fire protection vendor activation — Enroute to the site

6. identified Aug 15, 2026, 06:37 AM UTC

   Service Restoration Update - 2026-08-15 07:57 CEST Mitigation & Planned Actions • Issue investigation — Completed • Leak closure — Completed • Chiller water refilling — In Progress • Additional hose installation to accelerate refilling process — In Progress • Mobile dehumidifiers deployment — Completed • Water clearing from affected areas — In Progress • Vendor engagement — Enroute to the site (ETA 20 minutes) • Fire protection vendor activation — Enroute to the site

7. identified Aug 15, 2026, 06:39 AM UTC

   Service Restoration Update - 2026-08-15 08:31 CEST Mitigation & Planned Actions • Issue investigation — Completed • Leak closure — Completed • Chiller water refilling — In Progress • Mobile dehumidifiers deployment — Completed • Water clearing from affected areas — In Progress • Vendor engagement — Enroute to the site (ETA 20 minutes) • Fire system vendor to restore fire system — In Progress • Elevator unavailable— In Progress We are invoking our Disaster Recovery (DR) environment due to the ongoing datacentre incident. The primary site has been impacted for approximately three hours, and no confirmed restoration time is currently available. We will continue to provide updates as recovery progresses.

8. identified Aug 15, 2026, 07:06 AM UTC

   Service Restoration Update - 2026-08-15 08:58 CEST Mitigation & Planned Actions • Issue investigation — Completed • Leak closure — Completed • Chiller water refilling — In Progress • Mobile dehumidifiers deployment — Completed • Water clearing from affected areas — In Progress • Chiller vendor engagement — Enroute to the site (ETA 09:30 Site Local Time) • Fire system vendor to restore fire system — Enroute to the site (ETA 09:30 Site Local Time) • Elevator restoration — Completed

9. identified Aug 15, 2026, 07:47 AM UTC

   Service Restoration Update - 2026-08-15 09:33 CEST Mitigation & Planned Actions • Issue investigation — Completed • Leak closure — Completed • Chiller water refilling — In Progress (nearly complete) • Mobile dehumidifiers deployment — Completed • Water clearing from affected areas — In Progress • Chiller vendor engagement — Enroute to the site (ETA 09:30 Site Local Time) • Fire system vendor to restore fire system — Enroute to the site (ETA 09:30 Site Local Time) • Elevator restoration — Completed • Pump operation to purge air from system — Planned • Chiller test run (one chiller at a time) — Planned We are invoking our Disaster Recovery (DR) environment due to the ongoing datacentre incident. The primary site has been impacted for approximately three hours, and no confirmed restoration time is currently available. We will continue to provide updates as recovery progresses. We appreciate your patience and understanding while we work to fully restore the affected services.

10. identified Aug 15, 2026, 08:04 AM UTC

    Service Restoration Update - 2026-08-15 10:01 Mitigation & Planned Actions (Mitto DR Activation in progress) • Issue investigation — Completed • Leak closure — Completed • Chiller water refilling — In Progress (nearly complete) • Mobile dehumidifiers deployment — Completed • Water clearing from affected areas — In Progress (nearly complete) • Chiller vendor engagement — Enroute to the site • Fire system vendor to restore fire system — Arrived on-site, Restoration In Progress • Elevator restoration — Completed • Chiller test run (one chiller at a time) — In Progress We are invoking our Disaster Recovery (DR) environment due to the ongoing datacentre incident. The primary site has been impacted for approximately three hours, and no confirmed restoration time is currently available. We will continue to provide updates as recovery progresses. We appreciate your patience and understanding while we work to fully restore the affected services.

11. identified Aug 15, 2026, 08:31 AM UTC

    Service Restoration Update - 2026-08-15 10:30 Mitigation & Planned Actions • Issue investigation — Completed • Leak closure — Verifying • Chiller water refilling — In Progress (nearly complete) • Mobile dehumidifiers deployment — Completed • Water clearing from affected areas — In Progress • Chiller vendor engagement — Onsite, Restoration In Progress • Fire system vendor to restore fire system — Onsite, Restoration In Progress • Elevator restoration — Completed • Chiller test run (one chiller at a time) — In Progress We are invoking our Disaster Recovery (DR) environment due to the ongoing datacentre incident. The primary site has been impacted and no confirmed restoration time is currently available. We will continue to provide updates as recovery progresses. We appreciate your patience and understanding while we work to fully restore the affected services.

12. identified Aug 15, 2026, 09:03 AM UTC

    Service Restoration Update - 2026-08-15 11:02 Mitigation & Planned Actions • Leak closure — Completed • Second leak closure — Isolated and Investigation In Progress • Chiller water refilling — In Progress • Second chiller water refilling — In Progress • Mobile dehumidifiers deployment — Completed • Water clearing from affected areas — In Progress • Chiller vendor engagement — Restoration work In Progress • Fire system vendor to restore fire system — Restoration work In Progress • Elevator restoration — Completed • Chiller test run (one chiller at a time) — Planned We are invoking our Disaster Recovery (DR) environment due to the ongoing datacentre incident. The primary site has been impacted for approximately three hours, and no confirmed restoration time is currently available. We will continue to provide updates as recovery progresses. We appreciate your patience and understanding while we work to fully restore the affected services.

13. identified Aug 15, 2026, 09:29 AM UTC

    Service Restoration Update - 2026-08-15 11:28 Mitigation & Planned Actions • Leak closure — Completed • Second leak closure — Isolated and Investigation In Progress • Chiller water refilling — In Progress • Second chiller water refilling — In Progress • Mobile dehumidifiers deployment — Completed • Water clearing from affected areas — In Progress • Chiller vendor engagement — Restoration work In Progress • Fire system vendor to restore fire system — Restoration work In Progress • Elevator restoration — Completed • Chiller test run (one chiller at a time) — Planned We are invoking our Disaster Recovery (DR) environment due to the ongoing datacentre incident. The primary site has been impacted for approximately three hours, and no confirmed restoration time is currently available. We will continue to provide updates as recovery progresses. We appreciate your patience and understanding while we work to fully restore the affected services.

14. identified Aug 15, 2026, 09:56 AM UTC

    Service Restoration Update - 2026-08-15 11:55 Mitigation & Planned Actions • Leak closure — Completed • Second leak closure — Isolated and Investigation In Progress • Chiller water refilling — In Progress • Second chiller water refilling — In Progress • Mobile dehumidifiers deployment — Completed • Water clearing from affected areas — In Progress • Chiller vendor engagement — Restoration work In Progress • Fire system vendor to restore fire system — Restoration work In Progress • Elevator restoration — Completed • Chiller test run (one chiller at a time) — Planned We are invoking our Disaster Recovery (DR) environment due to the ongoing datacentre incident. The primary site has been impacted for approximately three hours, and no confirmed restoration time is currently available. We will continue to provide updates as recovery progresses. We appreciate your patience and understanding while we work to fully restore the affected services.

15. identified Aug 15, 2026, 10:25 AM UTC

    Service Restoration Update - 2026-08-15 12:26 Mitigation & Planned Actions • Leak closure — Completed • Second leak closure — Isolated and Investigation In Progress • Chiller water refilling — In Progress • Second chiller water refilling — In Progress • Mobile dehumidifiers deployment — Completed • Water clearing from affected areas — In Progress • Chiller vendor engagement — Restoration work In Progress • Fire system vendor to restore fire system — Restoration work In Progress • Elevator restoration — Completed • Chiller test run (one chiller at a time) — Planned Suspected Initial Cause The suspected initial cause is a cooling system failure due to a leak in the chilled water system. We are invoking our Disaster Recovery (DR) environment due to the ongoing datacentre incident. The primary site has been impacted and no confirmed restoration time is currently available. We will continue to provide updates as recovery progresses. We appreciate your patience and understanding while we work to fully restore the affected services.

16. identified Aug 15, 2026, 10:56 AM UTC

    Service Restoration Update - 2026-08-15 12:57 Mitigation & Planned Actions • Leak closure — Completed • Second leak closure — Isolated and Investigation In Progress • Chiller water refilling — In Progress • Second chiller water refilling — In Progress • Mobile dehumidifiers deployment — Completed • Water clearing from affected areas — In Progress • Chiller vendor engagement — Restoration work In Progress • Fire system vendor to restore fire system — Restoration work In Progress • Elevator restoration — Completed • Buffer tanks refill — In Progress • Chiller test run (one chiller at a time) — Planned Suspected Initial Cause The suspected initial cause is a cooling system failure due to a leak in the chilled water system. We are invoking our Disaster Recovery (DR) environment due to the ongoing datacentre incident. The primary site has been impacted and no confirmed restoration time is currently available. We will continue to provide updates as recovery progresses. We appreciate your patience and understanding while we work to fully restore the affected services.

17. identified Aug 15, 2026, 11:24 AM UTC

    Service Restoration Update - 2026-08-15 1:24 Mitigation & Planned Actions • Leak closure — Completed • Second leak closure — Isolated and Investigation In Progress • Chilled water refilling — Completed • Second chilled water refilling — In Progress • Mobile dehumidifiers deployment — Completed • Water clearing from affected areas — In Progress • Chiller vendor engagement — Restoration work In Progress • Fire system vendor to restore fire system — Restoration work In Progress • Elevator restoration — Completed • Buffer tanks refill — Completed • Chiller test run (one chiller at a time) — Planned Suspected Initial Cause The suspected initial cause is a cooling system failure due to a leak in the chilled water system. We are invoking our Disaster Recovery (DR) environment due to the ongoing datacentre incident. The primary site has been impacted and no confirmed restoration time is currently available. We will continue to provide updates as recovery progresses. We appreciate your patience and understanding while we work to fully restore the affected services.

18. identified Aug 15, 2026, 11:53 AM UTC

    Service Restoration Update - 2026-08-15 1:53 Mitigation & Planned Actions • Leak closure — Completed • Second leak closure — Isolated and Investigation In Progress • Chilled water refilling — Completed • Second chilled water refilling — In Progress • Mobile dehumidifiers deployment — Completed • Water clearing from affected areas — In Progress • Chiller vendor engagement — Restoration work In Progress • Fire system vendor to restore fire system — Restoration work In Progress • Elevator restoration — Completed • Buffer tanks refill — Completed • Chiller test run (one chiller at a time) — In Progress Suspected Initial Cause The suspected initial cause is a cooling system failure due to a leak in the chilled water system. We are invoking our Disaster Recovery (DR) environment due to the ongoing datacentre incident. The primary site has been impacted and no confirmed restoration time is currently available. We will continue to provide updates as recovery progresses. We appreciate your patience and understanding while we work to fully restore the affected services.

19. identified Aug 15, 2026, 12:20 PM UTC

    Service Restoration Update - 2026-08-15 2:20 Mitigation & Planned Actions • Leak closure — Completed • Second leak closure — Isolated and Investigation In Progress • Chilled water refilling — Completed • Second chilled water refilling — In Progress • Mobile dehumidifiers deployment — Completed • Water clearing from affected areas — In Progress • Chiller vendor engagement — Restoration work In Progress • Fire system vendor to restore fire system — Restoration work In Progress • Elevator restoration — Completed • Buffer tanks refill — Completed • Chiller test run (one chiller at a time) — In Progress Suspected Initial Cause The suspected initial cause is a cooling system failure due to a leak in the chilled water system. We are invoking our Disaster Recovery (DR) environment due to the ongoing datacentre incident. The primary site has been impacted and no confirmed restoration time is currently available. We will continue to provide updates as recovery progresses. We appreciate your patience and understanding while we work to fully restore the affected services.

20. identified Aug 15, 2026, 12:54 PM UTC

    Service Restoration Update - 2026-08-15 2:53 Mitigation & Planned Actions • Leak closure — Completed • Second leak closure — Isolated and Investigation In Progress • Chilled water refilling — Completed • Second chilled water refilling — In Progress • Mobile dehumidifiers deployment — Completed • Water clearing from affected areas — In Progress • Chiller vendor engagement — Restoration work In Progress • Fire system vendor to restore fire system — Restoration work In Progress • Elevator restoration — Completed • Buffer tanks refill — Completed • Chiller test run (one chiller at a time) — In Progress Suspected Initial Cause The suspected initial cause is a cooling system failure due to a leak in the chilled water system. We are invoking our Disaster Recovery (DR) environment due to the ongoing datacentre incident. The primary site has been impacted and no confirmed restoration time is currently available. We will continue to provide updates as recovery progresses. We appreciate your patience and understanding while we work to fully restore the affected services.

21. identified Aug 15, 2026, 01:17 PM UTC

    Service Restoration Update - 2026-08-15 3:17 Mitigation & Planned Actions • First leak closure — Isolated • Second leak closure — Isolated and Investigation In Progress • Chilled water refilling — Completed • Second chilled water refilling — In Progress • Mobile dehumidifiers deployment — Completed • Water clearing from affected areas — In Progress • Chiller vendor engagement — Restoration work In Progress • Fire system vendor to restore fire system — Restoration work In Progress • Elevator restoration — Completed • Buffer tanks refill — Completed • Chiller test run (one chiller at a time) — In Progress Suspected Initial Cause The suspected initial cause is a cooling system failure due to a leak in the chilled water system. We are invoking our Disaster Recovery (DR) environment due to the ongoing datacentre incident. The primary site has been impacted and no confirmed restoration time is currently available. We will continue to provide updates as recovery progresses. We appreciate your patience and understanding while we work to fully restore the affected services.

22. identified Aug 15, 2026, 01:41 PM UTC

    Service Restoration Update - 2026-08-15 3:42 Mitigation & Planned Actions • First leak isolation — Completed • Second leak isolation — Completed and Investigation In Progress • Chilled water refilling — Completed • Second chilled water refilling — In Progress • Mobile dehumidifiers deployment — Completed • Water clearing from affected areas — In Progress • Chiller vendor engagement — Restoration work In Progress • Fire system vendor to restore fire system — Restoration work In Progress • Elevator restoration — Completed • Buffer tanks refill — Completed • Chiller test run (one chiller at a time) — In Progress Suspected Initial Cause The suspected initial cause is a cooling system failure due to a leak in the chilled water system. We are invoking our Disaster Recovery (DR) environment due to the ongoing datacentre incident. The primary site has been impacted and no confirmed restoration time is currently available. We will continue to provide updates as recovery progresses. We appreciate your patience and understanding while we work to fully restore the affected services.

23. identified Aug 15, 2026, 02:44 PM UTC

    Service Restoration Update - 15 Aug 2026 - 4:04 Mitigation & Planned Actions • First leak isolation — Completed • Second leak isolation — Completed and Investigation In Progress • Chilled water refilling — Completed • Second chilled water refilling — In Progress • Mobile dehumidifiers deployment — Completed • Water clearing from affected areas — In Progress • Chiller vendor engagement — Restoration work In Progress • Fire system vendor to restore fire system — Restoration work In Progress • Elevator restoration — Completed • Buffer tanks refill — Completed • Chiller test run (one chiller at a time) — In Progress The suspected initial cause is a cooling system failure due to a leak in the chilled water system. We are invoking our Disaster Recovery (DR) environment due to the ongoing datacentre incident. The primary site has been impacted and no confirmed restoration time is currently available. We will continue to provide updates as recovery progresses. We appreciate your patience and understanding while we work to fully restore the affected services.

24. identified Aug 15, 2026, 02:46 PM UTC

    Service Restoration Update - 15 Aug 2026 - 4:31 Mitigation & Planned Actions • First leak isolation — Completed • Second leak isolation — Completed and Investigation In Progress • Chilled water refilling — Completed • Second chilled water refilling — In Progress • Mobile dehumidifiers deployment — Completed • Water clearing from affected areas — In Progress • Chiller vendor engagement — Restoration work In Progress • Fire system vendor to restore fire system — Restoration work In Progress • Elevator restoration — Completed • Buffer tanks refill — Completed • Chiller test run (one chiller at a time) — In Progress • Additional chiller vendors en route - In Progress The suspected initial cause is a cooling system failure due to a leak in the chilled water system. We are invoking our Disaster Recovery (DR) environment due to the ongoing datacentre incident. The primary site has been impacted and no confirmed restoration time is currently available. We will continue to provide updates as recovery progresses. We appreciate your patience and understanding while we work to fully restore the affected services.

25. identified Aug 15, 2026, 03:11 PM UTC

    Service Restoration Update - 15 Aug 2026 – 5:09 Mitigation & Planned Actions • First leak isolation — Completed • Second leak isolation — Completed and Investigation In Progress • Chilled water refilling — Completed • Second chilled water refilling — In Progress • Mobile dehumidifiers deployment — Completed • Water clearing from affected areas — In Progress • Chiller vendor engagement — Restoration work In Progress • Fire system vendor to restore fire system — Restoration work In Progress • Elevator restoration — Completed • Buffer tanks refill — Completed • Chiller test run (one chiller at a time) — In Progress • Additional chiller vendors en route - In Progress The suspected initial cause is a cooling system failure due to a leak in the chilled water system. We are invoking our Disaster Recovery (DR) environment due to the ongoing datacentre incident. The primary site has been impacted and no confirmed restoration time is currently available. We will continue to provide updates as recovery progresses. We appreciate your patience and understanding while we work to fully restore the affected services.

26. identified Aug 15, 2026, 03:40 PM UTC

    Service Restoration Update - 15 Aug 2026 – 5:39 Mitigation & Planned Actions • First leak isolation — Completed • Second leak isolation — Completed and Investigation In Progress • Chilled water refilling — Completed • Second chilled water refilling — In Progress • Mobile dehumidifiers deployment — Completed • Water clearing from affected areas — In Progress • Chiller vendor engagement — Restoration work In Progress • Fire system vendor to restore fire system — Restoration work In Progress • Elevator restoration — Completed • Buffer tanks refill — Completed • Chiller test run (one chiller at a time) — In Progress • Additional chiller vendors en route - Completed The suspected initial cause is a cooling system failure due to a leak in the chilled water system. We are invoking our Disaster Recovery (DR) environment due to the ongoing datacentre incident. The primary site has been impacted and no confirmed restoration time is currently available. We will continue to provide updates as recovery progresses. We appreciate your patience and understanding while we work to fully restore the affected services.

27. identified Aug 15, 2026, 04:09 PM UTC

    Service Restoration Update - 15 Aug 2026 – 6:06 Mitigation & Planned Actions • First leak isolation — Completed • Second leak isolation — Completed and Investigation In Progress • Chilled water refilling — Completed • Second chilled water refilling — In Progress • Mobile dehumidifiers deployment — Completed • Water clearing from affected areas — In Progress • Chiller vendor engagement — Restoration work In Progress • Fire system vendor to restore fire system — Restoration work In Progress • Elevator restoration — Completed • Buffer tanks refill — Completed • Chiller test run (one chiller at a time) — In Progress • Additional chiller vendors en route - Completed The suspected initial cause is a cooling system failure due to a leak in the chilled water system. We are invoking our Disaster Recovery (DR) environment due to the ongoing datacentre incident. The primary site has been impacted and no confirmed restoration time is currently available. We will continue to provide updates as recovery progresses. We appreciate your patience and understanding while we work to fully restore the affected services.

28. identified Aug 15, 2026, 04:48 PM UTC

    Service Restoration Update - 15 Aug 2026 – 6:39 Mitigation & Planned Actions • First leak isolation — Completed • Second leak isolation — Completed and Investigation In Progress • Chilled water refilling — Completed • Second chilled water refilling — Completed • Mobile dehumidifiers deployment — Completed • Water clearing from affected areas — In Progress • Chiller vendor engagement — Restoration work In Progress • Fire system vendor to restore fire system — Restoration work In Progress • Elevator restoration — Completed • Buffer tanks refill — Completed • Chillers 7, 8, and 9 Restoration — Completed • Additional chiller vendors en route — Completed • Restoration of cooling to the affected areas of second floor (Module 215) — In Progress Suspected Initial Cause The suspected initial cause is a cooling system failure due to a leak in the chilled water system. We are invoking our Disaster Recovery (DR) environment due to the ongoing datacentre incident. The primary site has been impacted and no confirmed restoration time is currently available. We will continue to provide updates as recovery progresses. We appreciate your patience and understanding while we work to fully restore the affected services.

29. identified Aug 15, 2026, 05:11 PM UTC

    Service Restoration Update - 15 Aug 2026 – 7:05 Mitigation & Planned Actions • First leak isolation — Completed • Second leak isolation — Completed and Investigation In Progress • Chilled water refilling — Completed • Second chilled water refilling — Completed • Mobile dehumidifiers deployment — Completed • Water clearing from affected areas — In Progress • Chiller vendor engagement — Restoration work In Progress • Fire system vendor to restore fire system — Restoration work In Progress • Elevator restoration — Completed • Buffer tanks refill — Completed • Chillers 7, 8, and 9 Restoration — Completed • Additional chiller vendors en route — Completed • Restoration of cooling to the affected areas of second floor (Module 215) — In Progress Suspected Initial Cause The suspected initial cause is a cooling system failure due to a leak in the chilled water system. We are invoking our Disaster Recovery (DR) environment due to the ongoing datacentre incident. The primary site has been impacted and no confirmed restoration time is currently available. We will continue to provide updates as recovery progresses. We appreciate your patience and understanding while we work to fully restore the affected services.

30. identified Aug 15, 2026, 05:59 PM UTC

    Service Restoration Update - 15 Aug 2026 – 7:35 Mitigation & Planned Actions • First leak isolation — Completed • Second leak isolation — Completed and Investigation In Progress • Chilled water refilling — Completed • Second chilled water refilling — Completed • Mobile dehumidifiers deployment — Completed • Water clearing from affected areas — In Progress • Chiller vendor engagement — Restoration work In Progress • Fire system vendor to restore fire system — Restoration work In Progress • Elevator restoration — Completed • Buffer tanks refill — Completed • Chillers 7, 8, and 9 Restoration — Completed • Additional chiller vendors en route — Completed • Restoration of cooling to the affected areas of second floor (Module 215) — In Progress Suspected Initial Cause The suspected initial cause is a cooling system failure due to a leak in the chilled water system. We are invoking our Disaster Recovery (DR) environment due to the ongoing datacentre incident. The primary site has been impacted and no confirmed restoration time is currently available. We will continue to provide updates as recovery progresses. We appreciate your patience and understanding while we work to fully restore the affected services.

31. identified Aug 15, 2026, 06:09 PM UTC

    Service Restoration Update - 15 Aug 2026 – 8:02 Mitigation & Planned Actions • First leak isolation — Completed • Second leak isolation — Completed and Investigation In Progress • Chilled water refilling — Completed • Second chilled water refilling — Completed • Mobile dehumidifiers deployment — Completed • Water clearing from affected areas — In Progress • Chiller vendor engagement — Restoration work In Progress • Fire system vendor to restore fire system — Restoration work In Progress • Elevator restoration — Completed • Buffer tanks refill — Completed • Chillers 7, 8, and 9 Restoration — Completed • Additional chiller vendors en route — Completed • Restoration of cooling to the affected areas of second floor (Module 215) — In Progress Suspected Initial Cause The suspected initial cause is a cooling system failure due to a leak in the chilled water system. We are invoking our Disaster Recovery (DR) environment due to the ongoing datacentre incident. The primary site has been impacted and no confirmed restoration time is currently available. We will continue to provide updates as recovery progresses. We appreciate your patience and understanding while we work to fully restore the affected services.

32. identified Aug 15, 2026, 06:34 PM UTC

    Service Restoration Update - 15 Aug 2026 – 8:29 Mitigation & Planned Actions • First leak isolation — Completed • Second leak isolation — Completed and Investigation In Progress • Chilled water refilling — Completed • Second chilled water refilling — Completed • Mobile dehumidifiers deployment — Completed • Water clearing from affected areas — In Progress • Chiller vendor engagement — Restoration work In Progress • Fire system vendor to restore fire system — Restoration work In Progress • Elevator restoration — Completed • Buffer tanks refill — Completed • Chillers 7, 8, and 9 Restoration — Completed • Additional chiller vendors en route — Completed • Restoration of cooling to the affected areas of second floor (Module 215) — In Progress Suspected Initial Cause The suspected initial cause is a cooling system failure due to a leak in the chilled water system. We are invoking our Disaster Recovery (DR) environment due to the ongoing datacentre incident. The primary site has been impacted and no confirmed restoration time is currently available. We will continue to provide updates as recovery progresses. We appreciate your patience and understanding while we work to fully restore the affected services.

33. monitoring Aug 15, 2026, 07:19 PM UTC

    Service Restoration Update - 15 Aug 2026 – 9:11 Service has been tentatively restored at our Equinix datacentre, and message delivery is now resuming. Our teams continue to monitor the environment closely and are working through the remaining message backlog. We will provide further updates as stability is confirmed. We appreciate your patience and understanding while we work to fully restore the affected services.

34. monitoring Aug 16, 2026, 07:05 AM UTC

    We are continuing to monitor for any further issues.

35. monitoring Aug 16, 2026, 08:09 AM UTC

    We have not seen any active issues up to this point, all systems are fully operational. Our team will continue to monitor all services closely.

36. resolved Aug 24, 2026, 07:08 AM UTC

    Service Impact: *Outage ongoing in Data Center*. Start: 2026-08-15 05:10 CEST End: 2026-08-15 23:38 CEST After a period of close monitoring, we are pleased to confirm that all services have been fully restored as of 2026-08-15 23:38 CEST. All systems are fully operational, and the services are operating optimally. We apologize for any inconvenience caused and appreciate your patience during this incident.

Read the full incident report →

Started Jul 28, 2026, 01:01 AM UTC· resolved Jul 28, 2026, 04:01 AM UTC

1. investigating Jul 28, 2026, 01:01 AM UTC

   Please be advised that currently there is a degradation in delivery towards Israel, Partner(425-01) You may experience irregular delivery with inconsistent delivery times while sending towards the specified network. Our dedicated team is working with the MNO to resolve the situation at hand, no estimated time of resolution can be provided yet. Start: 2026-07-27 22:00 CEST End: Ongoing Thank you for understanding.

2. resolved Jul 28, 2026, 04:01 AM UTC

   This degradation has been resolved. We will continue to monitor the traffic with the operator to ensure no further issues are observed. Start: 2026-07-27 22:00 CEST End: 2026-07-28 05:15 CEST Thank you for understanding.

Read the full incident report →

Started Jul 21, 2026, 02:48 PM UTC· resolved Jul 22, 2026, 07:53 PM UTC

1. investigating Jul 21, 2026, 02:48 PM UTC

   Please be advised that currently there is a degradation in delivery towards Israel, Partner (425-01) You may experience irregular delivery with inconsistent delivery times while sending towards the specified network. Our dedicated team is working with the MNO to resolve the situation at hand, no estimated time of resolution can be provided yet. Start: 2026-07-21 15:50 CEST End: Ongoing Thank you for understanding.

2. resolved Jul 22, 2026, 07:53 PM UTC

   This degradation has been resolved. We will continue to monitor the traffic with the operator to ensure no further issues are observed. Start: 2026-07-21 15:50 CEST End: 2026-07-22 19:35CEST Thank you for understanding.

Read the full incident report →

Started Jun 16, 2026, 05:44 AM UTC· resolved Jun 16, 2026, 08:49 AM UTC

1. investigating Jun 16, 2026, 05:44 AM UTC

   Please be advised that currently there is a degradation in delivery towards Iran, RighTel (432-20) You may experience irregular delivery with inconsistent delivery times while sending towards the specified network. Our dedicated team is working with the MNO to resolve the situation at hand, no estimated time of resolution can be provided yet. Start: 2026-06-16 07:00 CEST End: Ongoing Thank you for understanding.

2. resolved Jun 16, 2026, 08:49 AM UTC

   Hi Team, This degradation has been resolved. We will continue to monitor the traffic with the operator to ensure no further issues are observed. Start: 2026-06-16 07:00 CEST End: 2026-06-16 10:15 CEST Thank you for understanding.

Read the full incident report →

Started May 16, 2026, 02:01 PM UTC· resolved May 16, 2026, 09:55 PM UTC

1. investigating May 16, 2026, 02:01 PM UTC

   Please be advised that currently there is a degradation in delivery towards Iran, RighTel (432-20) You may experience irregular delivery with inconsistent delivery times while sending towards the specified network. Our dedicated team is working with the MNO to resolve the situation at hand, no estimated time of resolution can be provided yet. Start: 2026-05-16 15:30 CEST End: Ongoing Thank you for understanding.

2. resolved May 16, 2026, 09:55 PM UTC

   This degradation has been resolved. We will continue to monitor the traffic with the operator to ensure no further issues are observed. Start: 2026-05-16 15:30 CEST End: 2026-05-16 23:15 CEST Thank you for understanding.

Read the full incident report →

Started May 07, 2026, 12:05 PM UTC· resolved May 07, 2026, 12:27 PM UTC

1. investigating May 07, 2026, 12:05 PM UTC

   Please be advised that currently there is a degradation in delivery towards Afghanistan, Roshan (412-20) You may experience irregular delivery with inconsistent delivery times while sending towards the specified network. Our dedicated team is working with the MNO to resolve the situation at hand, no estimated time of resolution can be provided yet. Start: 2026-05-07 13:26 CET End: Ongoing Thank you for understanding.

2. resolved May 07, 2026, 12:27 PM UTC

   This degradation has been resolved. We will continue to monitor the traffic with the operator to ensure no further issues are observed. Start: 2026-05-07 13:26 CET End: 2026-05-07 14:18 CET Thank you for understanding.

Read the full incident report →

Started Mar 16, 2026, 10:18 AM UTC· resolved Mar 16, 2026, 12:23 PM UTC

1. investigating Mar 16, 2026, 10:18 AM UTC

   Please be advised that currently there is a degradation in delivery towards Tajikistan, Babilon-Mobile (436-04). You may experience irregular delivery with inconsistent delivery times while sending towards the specified network. Our dedicated team is working with the MNO to resolve the situation at hand, no estimated time of resolution can be provided yet. Start: 2026-03-16 10:15 CET End: Ongoing Thank you for understanding.

2. resolved Mar 16, 2026, 12:23 PM UTC

   This degradation has been resolved. We will continue to monitor the traffic with the operator to ensure no further issues are observed. Start: 2026-03-16 10:15 CET End: 2026-03-16 12:55 CET Thank you for understanding.

Read the full incident report →

Started Mar 06, 2026, 08:55 PM UTC· resolved Apr 14, 2026, 11:50 AM UTC

1. investigating Mar 06, 2026, 08:55 PM UTC

   Please be advised that currently there is a degradation in delivery towards Iran, MCI, (432-11) You may experience irregular delivery with inconsistent delivery times while sending towards the specified network. Our dedicated team is working with the MNO to resolve the situation at hand, no estimated time of resolution can be provided yet. Start: 2026-03-06 20:00 CET End: Ongoing Thank you for understanding.

2. resolved Apr 14, 2026, 11:50 AM UTC

   This degradation has been resolved. We will continue to monitor the traffic with the operator to ensure no further issues are observed. Start: 2026-03-06 20:00 CET End: 2026-04-14 11:30 CET Thank you for understanding.

Read the full incident report →

Started Mar 04, 2026, 01:04 PM UTC· resolved Mar 06, 2026, 06:57 AM UTC

1. investigating Mar 04, 2026, 01:04 PM UTC

   Please be advised that currently there is a degradation in delivery towards Tajikistan, Megafon (436-03) You may experience irregular delivery with inconsistent delivery times while sending towards the specified network. Our dedicated team is working with the MNO to resolve the situation at hand, no estimated time of resolution can be provided yet. Start: 2026-03-04 13:17 CET End: Ongoing Thank you for understanding.

2. resolved Mar 06, 2026, 06:57 AM UTC

   This degradation has been resolved. We will continue to monitor the traffic with the operator to ensure no further issues are observed. Start: 2026-03-04 13:17 CET End: 2026-03-06 07:50 CET Thank you for understanding.

Read the full incident report →

Started Jan 08, 2026, 11:20 PM UTC· resolved Jan 31, 2026, 11:24 AM UTC

1. investigating Jan 08, 2026, 11:20 PM UTC

   Please be advised that currently there is a degradation in delivery towards Iran, Irancell (432-35), RighTel (432-20) and MCI (432-11). You may experience irregular delivery with inconsistent delivery times when sending to the specified networks. Our dedicated team is working with the MNOs to resolve the situation at hand, no estimated time of resolution can be provided yet. Start: 2025-01-08 21:30 CET End: Ongoing Thank you for understanding.

2. monitoring Jan 29, 2026, 02:39 AM UTC

   Please be advised that the degradation towards Iran, Irancell (432-35) and MCI (432-11) has been resolved. We will continue to monitor the traffic with the operator to ensure no further issues are observed. Start: 2025-01-08 21:30 CET End: 2025-01-28 15:30 CET Thank you for understanding.

3. resolved Jan 31, 2026, 11:24 AM UTC

   Please be advised that the degradation towards Iran, Rightel (432-20) has been resolved. We will continue to monitor the traffic with the operator to ensure no further issues are observed. Start: 2025-01-08 21:30 CET End: 2025-01-31 10:30 CET Thank you for understanding.

Read the full incident report →

Started Dec 28, 2025, 01:42 PM UTC· resolved Dec 29, 2025, 09:15 AM UTC

1. investigating Dec 28, 2025, 01:42 PM UTC

   Please be advised that currently there is a degradation in delivery towards Iran, Rightel (432-20) You may experience irregular delivery with inconsistent delivery times while sending towards the specified network. Our dedicated team is working with the MNO to resolve the situation at hand, no estimated time of resolution can be provided yet. Start: 2025-12-28 14:10 CET End: Ongoing Thank you for understanding.

2. investigating Dec 28, 2025, 07:25 PM UTC

   This degradation has been resolved. We will continue to monitor the traffic with the operator to ensure no further issues are observed. Start: 2024-12-28 14:10 CET End: 2024-12-28 20:25 CET Thank you for understanding.

3. resolved Dec 29, 2025, 09:15 AM UTC

   This degradation has been resolved. We will continue to monitor the traffic with the operator to ensure no further issues are observed. Start: 2024-12-28 14:10 CET End: 2024-12-28 20:25 CET Thank you for understanding.

Read the full incident report →

Started Dec 24, 2025, 10:15 AM UTC· resolved Dec 24, 2025, 10:15 AM UTC

1. resolved Dec 24, 2025, 10:15 AM UTC

   NEW NUMBER RANGES Destination: Iran, Rightel MCC: 432 MNC: 20 Please be advised that Iran, Rightel (432-20) added new subscriber number ranges. New number ranges: Country Code (CC) National Destination Code (NDC) 98 99950 98 99951 Would you please implement new number ranges in your system? Thank you in advance.

Read the full incident report →

Started Dec 11, 2025, 11:06 PM UTC· resolved Dec 12, 2025, 06:20 AM UTC

1. investigating Dec 11, 2025, 11:06 PM UTC

   Please be advised that currently, there is a degradation in delivery towards Israel, Partner (425-01). You may experience irregular delivery with inconsistent delivery times while sending towards the specified network. Our dedicated team is working with the MNO to resolve the situation at hand, no estimated time of resolution can be provided yet. Start: 2025-12-11 23:00CET End: Ongoing Thank you for understanding.

2. resolved Dec 12, 2025, 06:20 AM UTC

   This degradation has been resolved. We will continue to monitor the traffic with the operator to ensure no further issues are observed. Start: 2025-12-11 23:00 CET End: 2025-12-12 05:00 CET Thank you for understanding.

Read the full incident report →

Started Nov 25, 2025, 11:54 PM UTC· resolved Nov 26, 2025, 03:22 AM UTC

1. investigating Nov 25, 2025, 11:54 PM UTC

   Please be advised that currently there is a degradation in delivery towards Iran, RighTel, (432-20). You may experience irregular delivery with inconsistent delivery times while sending towards the specified network. Our dedicated team is working with the MNO to resolve the situation at hand, no estimated time of resolution can be provided yet. Start: 2025-11-26 00:20 CET End: Ongoing Thank you for understanding.

2. resolved Nov 26, 2025, 03:22 AM UTC

   This degradation has been resolved. We will continue to monitor the traffic with the operator to ensure no further issues are observed. Start: 2025-11-26 00:20 CET End: 2025-11-26 04:15 CET Thank you for understanding.

Read the full incident report →

Started Nov 07, 2025, 12:11 AM UTC· resolved Nov 07, 2025, 01:03 AM UTC

1. investigating Nov 07, 2025, 12:11 AM UTC

   Please be advised that currently there is a degradation in delivery towards Israel, Partner, (425-01) You may experience irregular delivery with inconsistent delivery times while sending towards the specified network. Our dedicated team is working with the MNO to resolve the situation at hand, no estimated time of resolution can be provided yet. Start: 2025-11-07 00:01 CET End: Ongoing Thank you for understanding.

2. resolved Nov 07, 2025, 01:03 AM UTC

   This degradation has been resolved. We will continue to monitor the traffic with the operator to ensure no further issues are observed. Start: 2025-11-07 00:01 CET End: 2025-11-07 01:55 CET Thank you for understanding.

Read the full incident report →

Started Oct 29, 2025, 04:14 PM UTC· resolved Oct 29, 2025, 06:05 PM UTC

1. investigating Oct 29, 2025, 04:14 PM UTC

   Hi Team, We are currently having issue with CDN serving HTTP API traffic. Start time: 16:48 CET We will keep you posted with changes.

2. resolved Oct 29, 2025, 06:05 PM UTC

   Hi Team, Kindly note that we mitigated the issue and we are operative since 18:05 CET We apologize for any inconvenience this might have caused.

Read the full incident report →

Started Oct 28, 2025, 10:46 AM UTC· resolved Oct 28, 2025, 10:46 AM UTC

1. resolved Oct 28, 2025, 10:46 AM UTC

   We have experienced intermittent issues with our Chat apps service. Occasional disruptions when using the HTTP API were observed. After continuous monitoring of latency improvement, we declared the issue as mitigated after receiving confirmation of recovery. Start: 2025-10-28 10:35:00 CET End: 2025-10-28 11:25:00 CET

Read the full incident report →

Started Oct 27, 2025, 08:30 AM UTC· resolved Oct 27, 2025, 11:15 AM UTC

1. resolved Oct 27, 2025, 12:59 PM UTC

   We identified intermittent network performance issues that may have caused occasional service disruptions. Mitigation measures were applied, and performance has since returned to normal. We will continue to monitor the situation closely and provide updates should the issue reoccur. Impact Period: Start: 2025-10-27 10:30 CEST End: 2025-10-27 13:15 CEST

Read the full incident report →

Started Oct 09, 2025, 01:34 PM UTC· resolved Oct 09, 2025, 06:36 PM UTC

1. investigating Oct 09, 2025, 01:34 PM UTC

   Service Impact: HTTP API. Start: 2025-10-09 10:20:00 CET End: Ongoing Description: Our API Gateway vendor is currently experiencing intermittent issues and is working to resolve the issue. Occasional disruptions when using the HTTP API can be observed. Thank you for understanding.

2. resolved Oct 09, 2025, 06:36 PM UTC

   After continuous monitoring of latency improvement, we declared the issue as mitigated after receiving confirmation of recovery. Start: 2025-10-09 10:20:00 CET End: 2025-10-09 18:00:00 CET

Read the full incident report →