Simbase incident

[External] - Provisioning System Performance Degradation

Notice Resolved View vendor source →

Simbase experienced a notice incident on May 6, 2026, lasting 5h. The incident has been resolved; the full update timeline is below.

Started
May 06, 2026, 11:41 AM UTC
Resolved
May 06, 2026, 04:41 PM UTC
Duration
5h
Detected by Pingoru
May 06, 2026, 11:41 AM UTC

Update timeline

  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.

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