Simbase Outage History

Simbase is up right now

There were 12 Simbase outages since February 3, 2026 totaling 250h 4m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.simbase.com

Notice April 27, 2026

[External] - Data session establishment issues

Detected by Pingoru
Apr 27, 2026, 07:01 AM UTC
Resolved
Apr 27, 2026, 09:21 AM UTC
Duration
2h 19m
Timeline · 5 updates
  1. identified Apr 27, 2026, 07:01 AM UTC

    Supplier is investigating data session establishment problems that may affect connectivity Affected countries: XX

  2. investigating Apr 27, 2026, 07:21 AM UTC

    [2026-04-27 06:48:51] - Incident status was updated. Summary: Investigation is currently underway to determine the cause and scope of the incident.

  3. identified Apr 27, 2026, 07:21 AM UTC

    [2026-04-27 06:57:49] - Incident status was updated. Summary: Investigation is ongoing to resolve the connectivity issue.

  4. monitoring Apr 27, 2026, 07:21 AM UTC

    [2026-04-27 07:10:24] - Incident status was updated. Summary: A fix has been implemented and is currently being monitored for effectiveness.

  5. resolved Apr 27, 2026, 09:21 AM UTC

    [2026-04-27 09:18:53] - Incident status was updated. Summary: Monitoring has remained stable. The system causing the problem has been isolated and investigation into the root cause is ongoing.

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 →

Major February 6, 2026

Provisioning issue affecting BLUE and YELLOW profile SIM cards

Detected by Pingoru
Feb 06, 2026, 05:36 PM UTC
Resolved
Feb 11, 2026, 09:40 AM UTC
Duration
4d 16h
Affected: Data ConnectivityData ConnectivityCarrier ProvisioningCarrier Provisioning
Timeline · 4 updates
  1. investigating Feb 06, 2026, 05:36 PM UTC

    An upstream partner is investigating an issue affecting connectivity and provisioning of 🔵BLUE and 🟡YELLOW profile SIM cards. We are monitoring the situation closely, and will provide updates as soon as they are available. Enabling and disabling those SIM cards might fail at this time. If you are experiencing data connectivity issues, such as frequent disconnections, you may try using APN "mobiledata" instead of "simbase" as a workaround.

  2. identified Feb 09, 2026, 05:16 PM UTC

    Our partner has identified multiple issues and are working towards a permanent fix; they expect most provisioning errors to be resolved soon. We will continue monitoring the progress and will provide more updates as soon as they are available to us.

  3. monitoring Feb 10, 2026, 10:50 AM UTC

    A fix has been deployed to address the provisioning issues, and we are actively monitoring the results. If an affected SIM is enabled but unable to attach to the network, please try disabling and re-enabling it via the dashboard or API. We are continuing to investigate the degraded performance of the "simbase" APN in collaboration with our partner. As a precaution, we continue to recommend switching to the "mobiledata" APN for any SIM experiencing connectivity issues, including frequent disconnections or reduced data rates.

  4. resolved Feb 11, 2026, 09:40 AM UTC

    This incident has been resolved. The "simbase" APN is now operating as expected. If you previously switched to "mobiledata", you may revert back to "simbase" at your convenience. We welcome your feedback and encourage you to reach out if you notice anything unusual. Following further analysis, we determined that the provisioning issue affected a smaller subset of SIM cards than initially estimated. As a result, the provisioning impact has been reclassified as "partial outage".

Read the full incident report →

Notice February 3, 2026

[External] - Data Session Issues

Detected by Pingoru
Feb 03, 2026, 10:40 PM UTC
Resolved
Feb 03, 2026, 11:20 PM UTC
Duration
39m
Timeline · 4 updates
  1. investigating Feb 03, 2026, 10:40 PM UTC

    Investigating increased rate of data sessions unable to pass traffic Affected countries: XX

  2. investigating Feb 03, 2026, 10:40 PM UTC

    [2026-02-03 22:35:44] - Incident status was updated Summary: An increased rate of data sessions are failing to pass traffic. Investigation is underway.

  3. identified Feb 03, 2026, 11:00 PM UTC

    [2026-02-03 22:47:43] - Incident status was updated Summary: Data sessions are recovering and connectivity is being restored. Root cause investigation is ongoing.

  4. resolved Feb 03, 2026, 11:20 PM UTC

    [2026-02-03 23:00:23] - Incident status was updated Summary: Service has been restored to normal operations. Investigation into the root cause is ongoing.

Read the full incident report →

Looking to track Simbase downtime and outages?

Pingoru polls Simbase's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Simbase reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Simbase alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Simbase for free

5 free monitors · No credit card required