Simbase Outage History

Started May 22, 2026, 03:21 AM UTC· resolved May 22, 2026, 04:21 AM UTC

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 →

Started May 17, 2026, 04:21 PM UTC· resolved May 17, 2026, 04:41 PM UTC

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 →

Started May 14, 2026, 06:20 PM UTC· resolved May 14, 2026, 09:20 PM UTC

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 →

Started May 12, 2026, 02:43 PM UTC· resolved May 12, 2026, 04:00 PM UTC

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 →

Started May 12, 2026, 02:41 PM UTC· resolved May 12, 2026, 02:55 PM UTC

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 →

Started May 11, 2026, 12:52 PM UTC· resolved May 11, 2026, 03:40 PM UTC

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 →

Started May 06, 2026, 06:38 PM UTC· resolved May 06, 2026, 06:54 PM UTC

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 →

Started May 06, 2026, 11:41 AM UTC· resolved May 06, 2026, 04:41 PM UTC

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 →

Started May 04, 2026, 11:00 PM UTC· resolved May 06, 2026, 02:00 AM UTC

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 →

Started Apr 22, 2026, 11:30 PM UTC· resolved Apr 23, 2026, 01:30 AM UTC

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 →

Started Apr 13, 2026, 04:39 PM UTC· resolved Apr 13, 2026, 05:46 PM UTC

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 →

Started Apr 07, 2026, 08:41 AM UTC· resolved Apr 09, 2026, 01:38 PM UTC

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 →

Started Mar 31, 2026, 09:41 AM UTC· resolved Mar 31, 2026, 10:41 AM UTC

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 →

Started Mar 25, 2026, 09:44 AM UTC· resolved Mar 25, 2026, 10:52 AM UTC

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 →

Started Mar 16, 2026, 01:21 PM UTC· resolved Mar 16, 2026, 03:00 PM UTC

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 →

Started Mar 15, 2026, 02:01 PM UTC· resolved Mar 15, 2026, 02:13 PM UTC

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 →

Started Mar 09, 2026, 11:40 AM UTC· resolved Mar 12, 2026, 03:13 PM UTC

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 →

Started Feb 20, 2026, 12:20 PM UTC· resolved Feb 20, 2026, 02:00 PM UTC

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 →

Started Feb 06, 2026, 05:36 PM UTC· resolved Feb 11, 2026, 09:40 AM UTC

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 →

Started Feb 03, 2026, 10:40 PM UTC· resolved Feb 03, 2026, 11:20 PM UTC

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 →

Started Jan 03, 2026, 04:00 PM UTC· resolved Jan 03, 2026, 05:40 PM UTC

1. investigating Jan 03, 2026, 04:00 PM UTC

   Data traffic disruption affecting IoT connectivity due to network fault Affected countries: NL

2. investigating Jan 03, 2026, 04:00 PM UTC

   [2026-01-03 15:44:37] - Incident status was updated. Summary: An unexpected fault during an emergency change is causing decreased successful data traffic for some IoT customers. Engineers are actively working to resolve the issue with next update expected by 18:00 CET.

3. resolved Jan 03, 2026, 05:40 PM UTC

   [2026-01-03 17:33:50] - Incident status was updated. Summary: The incident has been fully mitigated and is now closed.

Read the full incident report →

Started Dec 29, 2025, 07:49 PM UTC· resolved Dec 29, 2025, 07:49 PM UTC

1. resolved Dec 29, 2025, 07:49 PM UTC

   A subset of our RADIUS infrastructure experienced temporary degraded performance due to an internal network routing issue. The issue has been resolved and all services are operating normally. Preventive measures have been implemented.

2. postmortem Dec 29, 2025, 07:50 PM UTC

   ## **Post-Mortem: RADIUS Service Degradation** ‌ **Date:** 29 December 2025 **Incident window:** 16:00 – 20:00 UTC **Severity:** Partial service disruption **Status:** Resolved ‌ ### **Summary** A subset of the RADIUS infrastructure experienced degraded availability due to an internal network routing disruption. This prevented affected RADIUS servers from forwarding accounting and diagnostic logs, which eventually led to service degradation. ### **Impact** * Intermittent RADIUS authentication and/or accounting issues for a subset of customers * No data loss or configuration changes * Impact limited to specific RADIUS instances ### **Root Cause** The incident was caused by a **temporary routing disruption within the private network**, introduced during a scheduled update of underlying connectivity components. As a result, outbound traffic from certain RADIUS servers was blocked. ### **Resolution** The routing issue was identified and corrected, restoring normal outbound connectivity. Affected RADIUS servers were recovered and resumed normal operation. ### **Preventive Actions** * Added safeguards around network changes that affect routing and egress * Introduced additional validation checks before similar updates * Improved monitoring to detect outbound connectivity issues earlier ### **Lessons Learned** Network routing changes can have indirect effects on dependent services. Additional pre-deployment checks and monitoring are required for changes affecting shared infrastructure components.

Read the full incident report →

Started Dec 15, 2025, 04:00 PM UTC· resolved Dec 16, 2025, 04:05 PM UTC

1. investigating Dec 15, 2025, 04:00 PM UTC

   New APN connection requests are being rejected, potentially affecting mobile data connectivity for IoT devices. Existing connections remain unaffected. Technical teams are investigating and working on resolving the issue. Affected countries: NL

2. investigating Dec 15, 2025, 04:00 PM UTC

   [2025-12-15 15:52:09] - Incident status was updated to "investigating". Summary: An issue affecting new APN connection requests is under investigation. Existing connections are not impacted. Technical teams are working to determine the root cause and full extent of the problem. Measures have been implemented to reduce the impact. Further updates will be provided.

3. monitoring Dec 15, 2025, 04:20 PM UTC

   [2025-12-15 16:14:18] - Incident status was updated to "monitoring". Summary: The reported issue has been resolved as of 17:00. Monitoring continues to ensure stability. The immediate cause has been identified, but further investigation into the root cause is ongoing.

4. resolved Dec 16, 2025, 04:05 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 11, 2025, 02:00 PM UTC· resolved Dec 11, 2025, 02:11 PM UTC

1. investigating Dec 11, 2025, 02:00 PM UTC

   A 3G signaling outage is currently under investigation, potentially affecting mobile connectivity services. Affected countries: XX

2. investigating Dec 11, 2025, 02:00 PM UTC

   [2025-12-11 13:46:03] - Incident status was updated to "investigating". Summary: An investigation is currently underway regarding a reported issue affecting mobile network services.

3. resolved Dec 11, 2025, 02:11 PM UTC

   We concluded that this issue does not affect any of our SIM profiles.

Read the full incident report →

Started Dec 10, 2025, 10:00 AM UTC· resolved Dec 10, 2025, 12:40 PM UTC

1. identified Dec 10, 2025, 10:00 AM UTC

   An upstream internet feed problem is causing data session failures and poor device performance. The issue is being investigated. Affected countries: XX

2. identified Dec 10, 2025, 10:00 AM UTC

   [2025-12-10 09:41:55] - Incident status was updated to "identified". Summary: An upstream internet feed issue has been detected, potentially causing data session failures or poor device performance. The provider is investigating a firewall problem.

3. monitoring Dec 10, 2025, 10:20 AM UTC

   [2025-12-10 10:05:13] - Incident status was updated to "monitoring". Summary: The provider reports that sessions are stabilizing and their internet provider has confirmed firewall stabilization. They will continue monitoring for any issues.

4. resolved Dec 10, 2025, 12:40 PM UTC

   [2025-12-10 12:24:13] - Incident status was updated to "resolved". Summary: Firewalls are now stable. Awaiting post-incident review from upstream provider.

Read the full incident report →