Mitto Outage History

Mitto degraded · 3 active incidents View live status →

Mitto had 22 outages in the last 2 years totaling 1702h 31m of downtime — averaging 0.9 incidents per month.

There were 22 Mitto outages since June 16, 2025 totaling 1702h 31m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.mitto.ch

Minor June 17, 2026

[RESOLVED] DELIVERY DEGRADATION Iran, Irancell (432-35)

Detected by Pingoru
Jun 17, 2026, 04:41 PM UTC
Resolved
Jun 17, 2026, 05:46 PM UTC
Duration
1h 5m
Affected: Local Degradation
Timeline · 2 updates
  1. investigating Jun 17, 2026, 04:41 PM 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-06-17 18:00 CEST End: Ongoing Thank you for understanding.

  2. resolved Jun 17, 2026, 05:46 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-06-17 18:00 CEST End: 2026-06-17 19:30 CEST Thank you for understanding.

Read the full incident report →

Minor June 16, 2026

[RESOLVED] DELIVERY DEGRADATION Iran, Rightel (432-20)

Detected by Pingoru
Jun 16, 2026, 05:44 AM UTC
Resolved
Jun 16, 2026, 08:49 AM UTC
Duration
3h 4m
Affected: Local Degradation
Timeline · 2 updates
  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 →

Minor May 16, 2026

[RESOLVED] DELIVERY DEGRADATION Iran, RighTel (432-20)

Detected by Pingoru
May 16, 2026, 02:01 PM UTC
Resolved
May 16, 2026, 09:55 PM UTC
Duration
7h 53m
Affected: Local Degradation
Timeline · 2 updates
  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 →

Minor May 15, 2026

[RESOLVED] DELIVERY DEGRADATION Iran, RighTel (432-20)

Detected by Pingoru
May 15, 2026, 06:14 PM UTC
Resolved
May 16, 2026, 06:44 AM UTC
Duration
12h 29m
Affected: Local Degradation
Timeline · 2 updates
  1. investigating May 15, 2026, 06:14 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-15 19:30 CEST End: Ongoing Thank you for understanding.

  2. resolved May 16, 2026, 06:44 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-05-15 19:30 CEST End: 2026-05-16 07:40 CEST Thank you for understanding.

Read the full incident report →

Minor May 7, 2026

[RESOLVED] DELIVERY DEGRADATION Afghanistan, Roshan (412-20)

Detected by Pingoru
May 07, 2026, 12:05 PM UTC
Resolved
May 07, 2026, 12:27 PM UTC
Duration
21m
Affected: Local Degradation
Timeline · 2 updates
  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 →

Minor March 16, 2026

[RESOLVED] DELIVERY DEGRADATION Tajikistan, Babilon-Mobile (436-04)

Detected by Pingoru
Mar 16, 2026, 10:18 AM UTC
Resolved
Mar 16, 2026, 12:23 PM UTC
Duration
2h 5m
Affected: Local Degradation
Timeline · 2 updates
  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 →

Minor March 6, 2026

[RESOLVED] DELIVERY DEGRADATION Iran, MCI, (432-11)

Detected by Pingoru
Mar 06, 2026, 08:55 PM UTC
Resolved
Apr 14, 2026, 11:50 AM UTC
Duration
38d 14h
Affected: Local Degradation
Timeline · 2 updates
  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 →

Minor March 4, 2026

[RESOLVED] DELIVERY DEGRADATION Tajikistan, Megafon (436-03)

Detected by Pingoru
Mar 04, 2026, 01:04 PM UTC
Resolved
Mar 06, 2026, 06:57 AM UTC
Duration
1d 17h
Affected: Local Degradation
Timeline · 2 updates
  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 →

Minor January 8, 2026

[RESOLVED] DELIVERY DEGRADATION Iran, Irancell (432-35), RighTel (432-20) and MCI (432-11)

Detected by Pingoru
Jan 08, 2026, 11:20 PM UTC
Resolved
Jan 31, 2026, 11:24 AM UTC
Duration
22d 12h
Affected: Local Degradation
Timeline · 3 updates
  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 →

Minor December 28, 2025

[RESOLVED]DELIVERY DEGRADATION Iran, Rightel (432-20)

Detected by Pingoru
Dec 28, 2025, 01:42 PM UTC
Resolved
Dec 29, 2025, 09:15 AM UTC
Duration
19h 33m
Affected: Local Degradation
Timeline · 3 updates
  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 →

Notice December 24, 2025

NOTIFICATION - NEW NUMBER RANGES - Iran RighTel

Detected by Pingoru
Dec 24, 2025, 10:15 AM UTC
Resolved
Dec 24, 2025, 10:15 AM UTC
Duration
Affected: Customer Portal/Dashboard
Timeline · 1 update
  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 →

Minor December 11, 2025

[RESOLVED] DELIVERY DEGRADATION Israel, Partner (425-01)

Detected by Pingoru
Dec 11, 2025, 11:06 PM UTC
Resolved
Dec 12, 2025, 06:20 AM UTC
Duration
7h 14m
Affected: Local Degradation
Timeline · 2 updates
  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 →

Minor November 25, 2025

[RESOLVED] DELIVERY DEGRADATION Iran, RighTel, (432-20)

Detected by Pingoru
Nov 25, 2025, 11:54 PM UTC
Resolved
Nov 26, 2025, 03:22 AM UTC
Duration
3h 28m
Affected: Local Degradation
Timeline · 2 updates
  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 →

Minor November 7, 2025

[RESOLVED] DELIVERY DEGRADATION Israel, Partner, (425-01)

Detected by Pingoru
Nov 07, 2025, 12:11 AM UTC
Resolved
Nov 07, 2025, 01:03 AM UTC
Duration
52m
Affected: Local Degradation
Timeline · 2 updates
  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 →

Minor October 29, 2025

[RESOLVED] ISSUE WITH HTTP API

Detected by Pingoru
Oct 29, 2025, 04:14 PM UTC
Resolved
Oct 29, 2025, 06:05 PM UTC
Duration
1h 51m
Affected: HTTP API
Timeline · 2 updates
  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 →

Notice October 28, 2025

[RESOLVED] Chat apps issue

Detected by Pingoru
Oct 28, 2025, 10:46 AM UTC
Resolved
Oct 28, 2025, 10:46 AM UTC
Duration
Affected: HTTP API
Timeline · 1 update
  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 →

Notice October 27, 2025

[RESOLVED] Performance Degradation

Detected by Pingoru
Oct 27, 2025, 12:59 PM UTC
Resolved
Oct 27, 2025, 12:59 PM UTC
Duration
Affected: HTTP APISMPP smpp1.mitto.chSMPP smpp2.mitto.ch
Timeline · 1 update
  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 →

Minor October 9, 2025

[RESOLVED] HTTP API

Detected by Pingoru
Oct 09, 2025, 01:34 PM UTC
Resolved
Oct 09, 2025, 06:36 PM UTC
Duration
5h 2m
Affected: HTTP API
Timeline · 2 updates
  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 →

Minor September 29, 2025

[RESOLVED] DELIVERY DEGRADATION Afghanistan, Roshan, (412-20)

Detected by Pingoru
Sep 29, 2025, 01:19 PM UTC
Resolved
Oct 01, 2025, 01:32 PM UTC
Duration
2d
Affected: Local Degradation
Timeline · 3 updates
  1. investigating Sep 29, 2025, 01:19 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: 2025-09-29 14:45 CEST End: Ongoing Thank you for understanding.

  2. investigating Sep 30, 2025, 01:02 PM UTC

    Please be advised that there is currently a country-level outage in Afghanistan due to a government-ordered internet blackout, which may cause issues with traffic delivery. Start: 2025-09-29 14:45 CEST End: Ongoing, no ETR Thank you for understanding.

  3. resolved Oct 01, 2025, 01:32 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: 2025-09-29 14:45 CEST End: 2025-10-01 15:00 CEST Thank you for understanding.

Read the full incident report →

Minor September 24, 2025

[RESOLVED] DELIVERY DEGRADATION Iran, Irancell, (432-35)

Detected by Pingoru
Sep 24, 2025, 11:32 AM UTC
Resolved
Sep 27, 2025, 03:28 PM UTC
Duration
3d 3h
Affected: Local Degradation
Timeline · 2 updates
  1. investigating Sep 24, 2025, 11:32 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: 2025-09-24 09:45CEST End: Ongoing Thank you for understanding.

  2. resolved Sep 27, 2025, 03:28 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: 2025-09-24 09:45CEST End: 2025-09-27 17:25 CEST Thank you for understanding.

Read the full incident report →

Notice September 23, 2025

Notice — Roshan (Afghanistan, 412-20) Sender ID Policy Change

Detected by Pingoru
Sep 23, 2025, 09:55 AM UTC
Resolved
Sep 23, 2025, 09:55 AM UTC
Duration
Affected: Local Degradation
Timeline · 1 update
  1. resolved Sep 23, 2025, 09:55 AM UTC

    Notice — Roshan (Afghanistan, 412-20) Sender ID Policy Change Date: (effective immediately) What happened: Roshan (MNO, Afghanistan — MCC/MNC 412-20) has implemented new Sender ID regulations. Impact: - All long codes, short codes, and generic alphanumeric Sender IDs will be blocked. - Only branded alphanumeric (alpha) Sender IDs are permitted. Action required: Please update your configurations to use branded alpha Sender IDs immediately to avoid traffic being blocked.

Read the full incident report →

Minor August 8, 2025

[RESOLVED] DELIVERY DEGRADATION Tajikistan, Megafon, (436-03)

Detected by Pingoru
Aug 08, 2025, 11:48 AM UTC
Resolved
Aug 08, 2025, 04:18 PM UTC
Duration
4h 29m
Affected: Local Degradation
Timeline · 2 updates
  1. investigating Aug 08, 2025, 11:48 AM 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: 2025-08-08 13:00 CEST End: Ongoing Thank you for understanding.

  2. resolved Aug 08, 2025, 04:18 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: 2025-08-08 13:00 CEST End: 2025-08-08 17:55 CES Thank you for understanding.

Read the full incident report →