Simbase Outage History

Simbase degraded · 1 active incident View live status →

Simbase had 61 outages in the last 2 years totaling 352h 10m of downtime — averaging 2.5 incidents per month.

There were 61 Simbase outages since August 22, 2025 totaling 352h 10m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.simbase.com

Minor June 11, 2026

[External] - Data service degradation

Detected by Pingoru
Jun 11, 2026, 10:21 AM UTC
Resolved
Jun 11, 2026, 03:21 PM UTC
Duration
4h 59m
Affected: Data Connectivity
Timeline · 5 updates
  1. investigating Jun 11, 2026, 10:21 AM UTC

    Data service degradation affecting Green SIM profile. Devices may have difficulty establishing new data sessions. Existing sessions remain unaffected. Affected countries: XX

  2. investigating Jun 11, 2026, 10:41 AM UTC

    [2026-06-11 10:06:45] - Incident status was updated. Summary: Investigating degradation in data service performance. Devices may have difficulty establishing new data sessions. Existing sessions remain unaffected. Actively monitoring the situation.

  3. identified Jun 11, 2026, 12:00 PM UTC

    [2026-06-11 11:48:59] - Incident status was updated. Summary: Performance degradation affecting data services for devices on a specific IMSI range has been identified. Devices may experience difficulties establishing new data sessions, while existing active sessions remain unaffected. Engineering teams are actively working to resolve the issue and the situation is being continuously monitored.

  4. identified Jun 11, 2026, 02:01 PM UTC

    [2026-06-11 13:53:36] - Incident status was updated. Summary: Gradual recovery observed for performance degradation affecting data services. Some devices may still experience intermittent difficulties establishing new data sessions while recovery continues. Existing active sessions remain unaffected. Engineering teams remain actively engaged working toward full resolution.

  5. resolved Jun 11, 2026, 03:21 PM UTC

    [2026-06-11 15:09:31] - Incident status was updated. Summary: The incident has been resolved and service is being closely monitored.

Read the full incident report →

Notice June 10, 2026

[External] - Data session establishment issues on Blue SIM profile

Detected by Pingoru
Jun 10, 2026, 09:21 AM UTC
Resolved
Jun 10, 2026, 05:21 PM UTC
Duration
8h
Timeline · 4 updates
  1. investigating Jun 10, 2026, 09:21 AM UTC

    Devices are experiencing failures when establishing data sessions on 4G networks using the Blue SIM profile. The issue is affecting a limited number of devices and is being investigated with the network operator. Affected countries: XX

  2. investigating Jun 10, 2026, 09:41 AM UTC

    [2026-06-10 09:10:19] - Incident status was updated. Summary: Investigating data session establishment failures on 4G network affecting a limited number of devices. Issue appears related to a previous fix and work is ongoing to identify and resolve the problem.

  3. monitoring Jun 10, 2026, 03:41 PM UTC

    [2026-06-10 15:23:10] - Incident status was updated. Summary: A fix has been applied to address the connectivity issue. Session counts are recovering and the situation continues to be monitored.

  4. resolved Jun 10, 2026, 05:21 PM UTC

    [2026-06-10 17:18:52] - Incident status was updated. Summary: The issue has been resolved with devices continuing to recover. A formal root cause analysis is pending and will be shared once available.

Read the full incident report →

Minor June 5, 2026

O2 UK Network - Temporary Access Restriction

Detected by Pingoru
Jun 05, 2026, 01:08 PM UTC
Resolved
Jun 08, 2026, 09:51 AM UTC
Duration
2d 20h
Affected: Data Connectivity
Timeline · 2 updates
  1. investigating Jun 05, 2026, 03:08 PM UTC

    We are currently experiencing issues with the O2 network in the UK. As a precautionary measure, we have temporarily restricted access to O2 while we work with our roaming partner to investigate the root cause. Affected devices may show as connected to O2 but will not have active data. We recommend ensuring your device is configured to automatically select a network, as alternative supported networks : EE, Three, and Vodafone remain fully operational. We will provide further updates as our investigation progresses. We apologise for any inconvenience caused. Please note: this issue affects Black Profile SIMs used in the UK only.

  2. resolved Jun 08, 2026, 09:51 AM UTC

    The issue affecting O2 connectivity in the UK has now been resolved. The root cause was identified as a firewall configuration issue within the VPLMN side , and service on O2 UK should now be fully restored.

Read the full incident report →

Minor June 4, 2026

[External] - Mobile network connectivity issues in Guinea

Detected by Pingoru
Jun 04, 2026, 02:20 PM UTC
Resolved
Jun 08, 2026, 01:40 PM UTC
Duration
3d 23h
Timeline · 4 updates
  1. identified Jun 04, 2026, 02:20 PM UTC

    Connectivity issues and service degradation reported on mobile network in Guinea. Network provider is investigating the incident affecting service availability. Affected countries: GN

  2. investigating Jun 04, 2026, 02:20 PM UTC

    [2026-06-04 13:48:25] - Incident status was updated. Summary: Investigating connectivity issue affecting devices in Guinea network. Customers may experience intermittent connectivity and service degradation. Team is actively working to identify root cause and restore normal service.

  3. identified Jun 04, 2026, 02:21 PM UTC

    [2026-06-04 13:58:57] - Incident status was updated. Summary: Network operator has confirmed an ongoing incident within their infrastructure that may be impacting service availability. The situation is being actively monitored and coordinated with the operator's team, with further updates to follow as more information becomes available.

  4. resolved Jun 08, 2026, 01:40 PM UTC

    [2026-06-08 13:30:41] - Incident status was updated. Summary: Connectivity in Guinea has been confirmed as fully operational. Services have recovered and traffic is processing normally.

Read the full incident report →

Major May 28, 2026

Provisioning Issues Impacting Blue and Yellow Profile SIM

Detected by Pingoru
May 28, 2026, 01:28 PM UTC
Resolved
May 28, 2026, 02:05 PM UTC
Duration
36m
Affected: Carrier ProvisioningCarrier Provisioning
Timeline · 3 updates
  1. investigating May 28, 2026, 01:28 PM UTC

    We have identified an increase in provisioning errors affecting Blue and Yellow Profile SIMs. As a result, some SIMs may fail to Enable and remain stuck in the “Enabling” state. As a precaution, we recommend that customers avoid disabling Blue/Yellow Profile SIMs until further notice. SIMs that are already enabled and in session are not affected.

  2. monitoring May 28, 2026, 01:38 PM UTC

    Provisioning rates for Blue and Yellow Profile SIMs have returned to normal, and we are seeing stable performance across the platform. We will continue monitoring the situation closely.

  3. resolved May 28, 2026, 02:05 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 26, 2026

Data service degradation

Detected by Pingoru
May 26, 2026, 04:53 PM UTC
Resolved
May 26, 2026, 05:50 PM UTC
Duration
56m
Affected: Data ConnectivityData Connectivity
Timeline · 4 updates
  1. investigating May 26, 2026, 04:53 PM UTC

    Our systems have identified a potential issue for Blue and Yellow Profile SIMs. Our engineers are actively investigating the situation to resolve it as quickly as possible.

  2. identified May 26, 2026, 05:18 PM UTC

    The issue has been identified and a fix is being implemented.

  3. identified May 26, 2026, 05:50 PM UTC

    We are continuing to work on a fix for this issue.

  4. resolved May 26, 2026, 05:50 PM UTC

    The service is now fully recovered.

Read the full incident report →

Notice May 26, 2026

[External] - API Service Disruption

Detected by Pingoru
May 26, 2026, 08:21 AM UTC
Resolved
May 27, 2026, 08:58 AM UTC
Duration
1d
Timeline · 5 updates
  1. investigating May 26, 2026, 08:21 AM UTC

    Supplier experiencing API service disruption under investigation. Affected countries: None

  2. investigating May 26, 2026, 08:41 AM UTC

    [2026-05-26 08:16:35] - Incident status was updated. Summary: Investigation is currently underway to determine the cause and scope of the incident.

  3. identified May 26, 2026, 09:41 AM UTC

    [2026-05-26 09:37:00] - Incident status was updated. Summary: The provider is working with their cloud infrastructure supplier to resolve an issue affecting their platform. Further updates are expected.

  4. monitoring May 26, 2026, 11:21 AM UTC

    [2026-05-26 11:16:14] - Incident status was updated. Summary: A fix has been implemented and is currently being monitored for effectiveness.

  5. resolved May 27, 2026, 08:58 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 22, 2026

[External] - Service congestion causing performance issues

Detected by Pingoru
May 22, 2026, 03:21 AM UTC
Resolved
May 22, 2026, 04:21 AM UTC
Duration
59m
Timeline · 4 updates
  1. monitoring May 22, 2026, 03:21 AM UTC

    Supplier experiencing service congestion leading to performance degradation and failures. Service is recovering and being monitored. Affected countries: XX

  2. investigating May 22, 2026, 03:41 AM UTC

    [2026-05-22 03:01:12] - Incident status was updated. Summary: Investigation is underway for service congestion causing performance issues. Further updates to follow.

  3. monitoring May 22, 2026, 03:41 AM UTC

    [2026-05-22 03:06:32] - Incident status was updated. Summary: Service is recovering and continues to be monitored.

  4. resolved May 22, 2026, 04:21 AM UTC

    [2026-05-22 04:05:53] - Incident status was updated. Summary: Service has been fully restored and is now operating normally.

Read the full incident report →

Notice May 17, 2026

[External] - Data session establishment issues

Detected by Pingoru
May 17, 2026, 04:21 PM UTC
Resolved
May 17, 2026, 04:41 PM UTC
Duration
20m
Timeline · 4 updates
  1. monitoring May 17, 2026, 04:21 PM UTC

    Data session establishment degraded, fix implemented and being monitored Affected countries: XX

  2. investigating May 17, 2026, 04:41 PM UTC

    [2026-05-17 15:30:00] - Incident status was updated. Summary: Data session establishment has been degraded and is currently under investigation.

  3. monitoring May 17, 2026, 04:41 PM UTC

    [2026-05-17 15:54:00] - Incident status was updated. Summary: A fix has been implemented and is currently being monitored for effectiveness.

  4. resolved May 17, 2026, 04:41 PM UTC

    [2026-05-17 16:40:16] - Incident status was updated. Summary: The incident has been resolved and services have returned to normal operations.

Read the full incident report →

Minor May 14, 2026

[External] - Mobile network connectivity issues in Poland

Detected by Pingoru
May 14, 2026, 06:20 PM UTC
Resolved
May 14, 2026, 09:20 PM UTC
Duration
2h 59m
Timeline · 5 updates
  1. identified May 14, 2026, 06:20 PM UTC

    Connectivity issues detected on a mobile network operator in Poland. Service temporarily restricted on affected network, alternative networks available. Affected countries: PL

  2. investigating May 14, 2026, 06:21 PM UTC

    [2026-05-14 18:02:13] - Incident status was updated. Summary: Connectivity issues are being investigated affecting devices on the mobile network in Poland. Customers may experience intermittent connectivity or service degradation. The team is actively working to identify the root cause and restore normal service.

  3. identified May 14, 2026, 06:21 PM UTC

    [2026-05-14 18:10:46] - Incident status was updated. Summary: The issue affecting connectivity in Poland has been identified and contact has been established with the operator to restore service. As a temporary measure, connectivity through the affected network has been restricted. Customers can continue using alternative networks in the country which are operating normally. Further updates will be provided as information becomes available.

  4. monitoring May 14, 2026, 08:40 PM UTC

    [2026-05-14 20:29:24] - Incident status was updated. Summary: Connectivity has been restored on the mobile network in Poland and services are operating normally. The situation continues to be monitored to ensure service stability.

  5. resolved May 14, 2026, 09:20 PM UTC

    [2026-05-14 21:16:25] - Incident status was updated. Summary: The incident has been resolved.

Read the full incident report →

Major May 12, 2026

Intermittment Service Issue

Detected by Pingoru
May 12, 2026, 02:43 PM UTC
Resolved
May 12, 2026, 04:00 PM UTC
Duration
1h 17m
Affected: Data ConnectivityData Connectivity
Timeline · 4 updates
  1. investigating May 12, 2026, 02:43 PM UTC

    We are currently seeing intermittent service issues affecting Blue and Yellow Profile SIMs. We are actively working with our upstream providers to deploy additional measures and restore the stability of our service.

  2. investigating May 12, 2026, 02:45 PM UTC

    We are continuing to investigate this issue.

  3. monitoring May 12, 2026, 03:34 PM UTC

    A fix has been implemented. Traffic levels are under control and service has fully recovered. We will continue to monitor.

  4. resolved May 12, 2026, 04:00 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 12, 2026

[External] - Intermittent Service Issue

Detected by Pingoru
May 12, 2026, 02:41 PM UTC
Resolved
May 12, 2026, 02:55 PM UTC
Duration
14m
Timeline · 1 update
  1. investigating May 12, 2026, 02:41 PM UTC

    Supplier experiencing intermittent service issues due to increased load on their infrastructure. Affected countries: XX

Read the full incident report →

Major May 11, 2026

Intermittent connectivity issues detected

Detected by Pingoru
May 11, 2026, 12:52 PM UTC
Resolved
May 11, 2026, 03:40 PM UTC
Duration
2h 48m
Affected: Data ConnectivityData ConnectivityData Connectivity
Timeline · 4 updates
  1. investigating May 11, 2026, 12:52 PM UTC

    Our systems have identified a potential issue for Black, Green and Red Profile SIM cards. Our engineers are actively investigating the situation to resolve it quickly.

  2. identified May 11, 2026, 01:21 PM UTC

    We are observing recovery across impacted Black, Green and Red Profile SIM cards. Our teams remain engaged and are continuing to monitor systems to ensure services return to normal as quickly as possible. Thank you for your continued patience.

  3. monitoring May 11, 2026, 02:10 PM UTC

    We have implemented a fix and are observing continued recovery of services impacting Black, Green and Red Profile SIM cards. Monitoring remains ongoing as we work to ensure full stability across all systems. We appreciate your continued patience.

  4. resolved May 11, 2026, 03:40 PM UTC

    Earlier today, during a scheduled maintenance performed by one of our upstream providers , intermittent connectivity issues have been observed in the USA. Service Impact: Some API calls may have experienced elevated response times, and limited connectivity inconsistencies may have been intermittently observed. Normal performance has been restored, and we continue to monitor closely to ensure ongoing stability.

Read the full incident report →

Minor May 6, 2026

Accounting system migration issues

Detected by Pingoru
May 06, 2026, 06:38 PM UTC
Resolved
May 06, 2026, 06:54 PM UTC
Duration
15m
Affected: DashboardStore
Timeline · 2 updates
  1. identified May 06, 2026, 06:38 PM UTC

    We are extending the maintenance window for the migration of our accounting and billing system to a new provider. We are working through a technical issue and will provide an update shortly. SIM connectivity is not affected.

  2. resolved May 06, 2026, 06:54 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 6, 2026

[External] - Provisioning System Performance Degradation

Detected by Pingoru
May 06, 2026, 11:41 AM UTC
Resolved
May 06, 2026, 04:41 PM UTC
Duration
5h
Timeline · 4 updates
  1. investigating May 06, 2026, 11:41 AM UTC

    Supplier experiencing elevated system load causing rate limiting in provisioning operations. No failed jobs reported. Affected countries: XX

  2. investigating May 06, 2026, 11:41 AM UTC

    [2026-05-06 11:30:13] - Incident status was updated. Summary: Elevated system load has triggered automatic rate limiting at provisioning job start time. No jobs are stuck or failed. An unresolved underlying factor contributing to the slowdown is currently under investigation.

  3. monitoring May 06, 2026, 02:41 PM UTC

    [2026-05-06 14:16:04] - Incident status was updated. Summary: A fix has been implemented and is currently being monitored for effectiveness.

  4. resolved May 06, 2026, 04:41 PM UTC

    [2026-05-06 16:14:55] - Incident status was updated. Summary: The incident has been resolved.

Read the full incident report →

Major May 5, 2026

Connectivity issues due to Scheduled GRX Security Maintenance

Detected by Pingoru
May 05, 2026, 08:23 AM UTC
Resolved
May 04, 2026, 11:00 PM UTC
Duration
Timeline · 1 update
  1. resolved May 05, 2026, 08:23 AM UTC

    During the scheduled GRX security maintenance performed by the external provider, Blue & Yellow Profile SIM devices experienced temporary roaming connectivity interruptions and failed network attachments. The impact occurred during the maintenance window while security enhancements were being applied to specific roaming partners, causing intermittent session terminations. Most devices reconnected automatically after the disruption, although some required a manual reboot to restore connectivity. The maintenance activities are scheduled to continue across May 5th, 6th, and 7th between 20:00–03:00 CET.

Read the full incident report →

Minor April 23, 2026

Connectivity Disruption Due to Signalling Storm

Detected by Pingoru
Apr 23, 2026, 01:30 AM UTC
Resolved
Apr 23, 2026, 01:30 AM UTC
Duration
Timeline · 1 update
  1. resolved Apr 23, 2026, 10:20 AM UTC

    We experienced a connectivity disruption impacting Blue and Yellow Profile SIMs due to an unexpected signaling storm. Immediate mitigation measures were implemented, and core connectivity was restored within approximately one hour. Please note that due to the nature of network propagation, some SIMs may have taken additional time—up to a few hours—to fully reconnect. We continue to monitor the network to ensure stability and prevent recurrence but at this point, we observe full service recovery.

Read the full incident report →

Major April 13, 2026

Mobile Data issues

Detected by Pingoru
Apr 13, 2026, 04:54 PM UTC
Resolved
Apr 13, 2026, 05:46 PM UTC
Duration
52m
Affected: Data ConnectivityData Connectivity
Timeline · 4 updates
  1. investigating Apr 13, 2026, 04:39 PM UTC

    Investigation underway for a drop in data sessions. Further updates to follow.

  2. investigating Apr 13, 2026, 04:54 PM UTC

    The issue has been identified, and our team is actively working to restore full service. Customers should begin to observe service recovery as we continue to implement a fix.

  3. monitoring Apr 13, 2026, 05:22 PM UTC

    Connectivity has been restored to all affected SIM cards. We continue to monitor the situation closely.

  4. resolved Apr 13, 2026, 05:46 PM UTC

    This incident is resolved. If Blue or Yellow SIM profiles still show issues, force a location update via the diagnostics tool or by SMS (if supported by the device).

Read the full incident report →

Notice April 7, 2026

[External] - Data session ingest and notification delivery

Detected by Pingoru
Apr 07, 2026, 08:41 AM UTC
Resolved
Apr 09, 2026, 01:38 PM UTC
Duration
2d 4h
Timeline · 3 updates
  1. monitoring Apr 07, 2026, 08:41 AM UTC

    Issue with core message queuing platform causing delays to data session notifications Affected countries: XX

  2. monitoring Apr 07, 2026, 09:01 AM UTC

    [2026-04-07 08:38:21] - Incident status was updated. Summary: An issue in the core message queuing platform caused delays to data session and other notifications. A fix has been implemented and processing is recovering. The situation continues to be monitored as the backlog clears.

  3. resolved Apr 09, 2026, 01:38 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 31, 2026

[External] - Data Instability

Detected by Pingoru
Mar 31, 2026, 09:41 AM UTC
Resolved
Mar 31, 2026, 10:41 AM UTC
Duration
59m
Timeline · 4 updates
  1. monitoring Mar 31, 2026, 09:41 AM UTC

    Supplier investigating data service instability, service has been restored and is being monitored. Affected countries: None

  2. investigating Mar 31, 2026, 10:01 AM UTC

    [2026-03-31 09:35:19] - Incident status was updated. Summary: Investigation is currently underway to determine the cause and scope of the incident.

  3. monitoring Mar 31, 2026, 10:01 AM UTC

    [2026-03-31 09:38:22] - Incident status was updated. Summary: Service has been restored and monitoring is ongoing.

  4. resolved Mar 31, 2026, 10:41 AM UTC

    [2026-03-31 10:27:53] - Incident status was updated. Summary: No further issues have been observed with the service.

Read the full incident report →

Minor March 25, 2026

[External] - Network signaling issues affecting device connectivity

Detected by Pingoru
Mar 25, 2026, 09:44 AM UTC
Resolved
Mar 25, 2026, 10:52 AM UTC
Duration
1h 7m
Timeline · 5 updates
  1. identified Mar 25, 2026, 09:44 AM UTC

    Signaling degradation is causing devices to require multiple connection attempts to the network. Issue identified and fix is being applied. Affected countries: XX

  2. investigating Mar 25, 2026, 09:45 AM UTC

    [2026-03-25 09:35:11] - Incident status was updated. Summary: Investigation ongoing for signalling degradation issue causing some devices to require multiple connection attempts. Team working to identify root cause and mitigate impact.

  3. identified Mar 25, 2026, 09:45 AM UTC

    [2026-03-25 09:39:33] - Incident status was updated. Summary: The issue has been identified with onset at approximately 09:05 UTC. A fix is currently being applied to resolve the signalling degradation. Mitigation efforts are actively underway with ongoing progress updates to follow.

  4. monitoring Mar 25, 2026, 09:51 AM UTC

    [2026-03-25 09:47:10] - Incident status was updated. Summary: The fix has been successfully applied and service is now restored and operating normally. Engineering teams continue to monitor the situation closely to ensure stability. Further updates will be provided if any additional issues are observed.

  5. resolved Mar 25, 2026, 10:52 AM UTC

    [2026-03-25 10:51:39] - Incident status was updated. Summary: The issue has been fully resolved and all services are operating normally.

Read the full incident report →

Notice March 16, 2026

[External] - Data service degradation in Belgium

Detected by Pingoru
Mar 16, 2026, 01:21 PM UTC
Resolved
Mar 16, 2026, 03:00 PM UTC
Duration
1h 39m
Timeline · 3 updates
  1. investigating Mar 16, 2026, 01:21 PM UTC

    Severe data service degradation detected in Belgium on local network. Issue is limited to Belgium only and does not affect international roaming. Affected countries: BE

  2. investigating Mar 16, 2026, 01:21 PM UTC

    [2026-03-16 13:10:35] - Incident status was updated. Summary: Severe data service degradation observed in Belgium on a local network. The operator is aware and actively working on resolution. Impact is limited to Belgium only and does not affect international roaming.

  3. resolved Mar 16, 2026, 03:00 PM UTC

    [2026-03-16 14:50:23] - Incident status was updated. Summary: The issue has been resolved and services have returned to normal operation.

Read the full incident report →

Notice March 15, 2026

[External] - Roaming Connectivity Degradation

Detected by Pingoru
Mar 15, 2026, 02:01 PM UTC
Resolved
Mar 15, 2026, 02:13 PM UTC
Duration
12m
Timeline · 4 updates
  1. investigating Mar 15, 2026, 02:01 PM UTC

    Investigating roaming connectivity degradation affecting diameter signaling Affected countries: XX

  2. investigating Mar 15, 2026, 02:01 PM UTC

    [2026-03-15 14:00:52] - Incident status was updated. Summary: An incident is currently under investigation.

  3. investigating Mar 15, 2026, 02:13 PM UTC

    This incident was automatically opened by one of our monitoring systems as a precautionary measure. After a thorough investigation, we have confirmed that all roaming connectivity and diameter signaling are operating normally. No customer impact was identified. We are closing this incident as resolved.

  4. resolved Mar 15, 2026, 02:13 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 9, 2026

[External] - Data roaming services disruption

Detected by Pingoru
Mar 09, 2026, 11:40 AM UTC
Resolved
Mar 12, 2026, 03:13 PM UTC
Duration
3d 3h
Timeline · 4 updates
  1. investigating Mar 09, 2026, 11:40 AM UTC

    Data roaming services blocked for all inbound roamers due to regulatory instruction from local authorities. Affected countries: KW

  2. investigating Mar 09, 2026, 11:40 AM UTC

    [2026-03-09 11:33:06] - Incident status was updated. Summary: Data roaming services for inbound roamers in Kuwait have been blocked by local authorities with immediate effect. The situation is being monitored and updates will be provided once services are restored.

  3. identified Mar 12, 2026, 03:09 PM UTC

    Kindly note that data traffic in Kuwait is still blocked until further notice. We will notify you once we receive any further updates.

  4. resolved Mar 12, 2026, 03:13 PM UTC

    Data roaming services in Kuwait remain blocked by local authorities due to regulatory restrictions. This is not a network fault on our side. We will open a new incident if the situation changes. For questions, contact support.

Read the full incident report →

Notice February 20, 2026

[External] - Mobile Data issues

Detected by Pingoru
Feb 20, 2026, 12:20 PM UTC
Resolved
Feb 20, 2026, 02:00 PM UTC
Duration
1h 40m
Timeline · 4 updates
  1. identified Feb 20, 2026, 12:20 PM UTC

    Drop in data sessions detected. Service is recovering and being monitored. Affected countries: XX

  2. investigating Feb 20, 2026, 12:20 PM UTC

    [2026-02-20 12:01:02] - Incident status was updated Summary: Investigation underway for a drop in data sessions. Further updates to follow.

  3. identified Feb 20, 2026, 12:20 PM UTC

    [2026-02-20 12:12:49] - Incident status was updated Summary: Service is recovering and continues to be monitored.

  4. resolved Feb 20, 2026, 02:00 PM UTC

    [2026-02-20 13:51:52] - Incident status was updated Summary: Traffic levels have returned to normal after monitoring over the last hour. Root cause investigation is in progress.

Read the full incident report →