Currents Outage History

Currents is up right now

Currents had 8 outages in the last 2 years — averaging 0.3 incidents per month.

There were 8 Currents outages since August 18, 2025. Each is summarised below — incident details, duration, and resolution information.

Source: https://currents.instatus.com

Minor May 4, 2026

Increased number of API response errors

Detected by Pingoru
May 04, 2026, 12:30 PM UTC
Resolved
May 04, 2026, 12:30 PM UTC
Duration
Timeline · 1 update
  1. resolved May 04, 2026, 12:30 PM UTC

    Type: Incident Duration: 2 hours and 20 minutes Affected Components: API - HTTP REST API, API - Dashboard Browsing May 4, 12:30:00 GMT+0 - Investigating - We are currently investigating this incident. May 4, 14:04:43 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. May 4, 14:49:30 GMT+0 - Resolved - This incident has been resolved.

Read the full incident report →

Minor December 15, 2025

Slow reported run completions

Detected by Pingoru
Dec 15, 2025, 04:42 PM UTC
Resolved
Dec 15, 2025, 04:42 PM UTC
Duration
Timeline · 1 update
  1. resolved Dec 15, 2025, 04:42 PM UTC

    Type: Incident Duration: 1 hour and 17 minutes Affected Components: Data Pipeline Dec 15, 17:23:24 GMT+0 - Monitoring - The queue has now recovered, we will monitor the change as the extra processes we launched ramp back down to normal levels. Dec 15, 18:00:16 GMT+0 - Resolved - This incident has been resolved. Dec 15, 16:42:53 GMT+0 - Identified - Our background tasks queues have gotten behind and as a result run status in the dashboard and event notifications are currently delayed. This was due to a low auto-scaling cap put in place during our last incident (to limit database connections). This scaling issue has now been resolved but we will expect it to take some time for the system to catch up. And result notifications will likely continue to be delayed for the next hour or two.

Read the full incident report →

Minor December 13, 2025

Slowness in test results ingestion rate, runs timing out

Detected by Pingoru
Dec 13, 2025, 02:30 AM UTC
Resolved
Dec 13, 2025, 02:30 AM UTC
Duration
Timeline · 1 update
  1. resolved Dec 13, 2025, 02:30 AM UTC

    Type: Incident Duration: 2 hours and 50 minutes Affected Components: Data Pipeline, Data Injestion Dec 13, 02:30:00 GMT+0 - Investigating - We are currently investigating this incident. Dec 13, 05:20:09 GMT+0 - Resolved - This incident has been resolved. The preliminary root cause is a sudden spike in concurrent executions, which affected the DB capacity. After increasing the capacity and processing the backlog the system is back to normal. A more thorough investigation and mitigation are to follow to improve system stability due to surge in concurrent requests.

Read the full incident report →

Minor August 21, 2025

Performance issues for Cypress uploads and users on the us east coast.

Detected by Pingoru
Aug 21, 2025, 06:23 PM UTC
Resolved
Aug 21, 2025, 06:23 PM UTC
Duration
Timeline · 1 update
  1. resolved Aug 21, 2025, 06:23 PM UTC

    Type: Incident Duration: 2 hours and 1 minute Affected Components: Data Injestion Aug 21, 18:23:28 GMT+0 - Identified - Due to a network issue, uploads may be slow. Cypress uploads of logs in all regions are impacted (because our ingest server for these is in the impacted area), and playwright artifact uploads from the us east coast. Aug 21, 19:06:36 GMT+0 - Monitoring - The issue looks to have been resolved. We are continuing to monitor and confirm. Aug 21, 20:24:18 GMT+0 - Resolved - This incident has been resolved.

Read the full incident report →

Minor August 18, 2025

Increased errors and timeouts for reporting runs and uploading artifacts

Detected by Pingoru
Aug 18, 2025, 03:33 PM UTC
Resolved
Aug 18, 2025, 03:33 PM UTC
Duration
Timeline · 1 update
  1. resolved Aug 18, 2025, 03:33 PM UTC

    Type: Incident Duration: 2 hours and 43 minutes Affected Components: Data Injestion Aug 18, 15:33:32 GMT+0 - Investigating - We are currently investigating this incident. Aug 18, 16:46:15 GMT+0 - Monitoring - We are no longer experiencing the issue, but are still investigating the cause. Aug 18, 18:17:00 GMT+0 - Resolved - Incident resolved. We had a partial outage with our object storage provider that resulting in some uploads and requests timing out. We also had issues with our retry logic triggering access limit. We will look into improving this area.

Read the full incident report →