Currents incident

Issues with slow processing of results

Minor Resolved View vendor source →
Started
Feb 11, 2026, 05:11 PM UTC
Resolved
Feb 11, 2026, 05:11 PM UTC
Duration
Detected by Pingoru
Feb 11, 2026, 05:11 PM UTC

Update timeline

  1. resolved Feb 11, 2026, 05:11 PM UTC

    Type: Incident Duration: 5 hours and 11 minutes Affected Components: Data Pipeline, API - HTTP REST API, Scheduler, Data Injestion, API - Dashboard Browsing, 3rd Party Integrations Feb 11, 19:41:12 GMT+0 - Identified - We are continuing work on full recovery. Initial results processing and notifications are back to normal, but some data queues that populate the dashboard charts and explorers are still delayed. Feb 11, 22:22:54 GMT+0 - Resolved - This incident has been resolved. All queues are caught up. Feb 11, 22:15:58 GMT+0 - Monitoring - We are almost fully recovered, though are still seeing a 10 minute delay on our analytics queues, that power some of the reports in the dashboard. These should finish catching up over the next half hour, with the delay improving steadily. Feb 11, 17:11:35 GMT+0 - Investigating - We are currently investigating this incident. But processing results has gotten significantly behind. We are also seeing an increase of errors in the endpoints that receive client requests from the reports. Feb 11, 17:38:30 GMT+0 - Identified - We are continuing to work on recovery. The endpoint errors have been resolved. But our queues are backed up, so results are taking a while to show in the dashboard.

Looking to track Currents downtime and outages?

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

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

5 free monitors · No credit card required