Currents Outage History

Currents is up right now

Currents had 7 outages in the last 2 years totaling 1h 18m of downtime — averaging 0.3 incidents per month.

There were 7 Currents outages since October 20, 2025 totaling 1h 18m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://currents.instatus.com

Major October 1, 2026

Notifications and analytics data delayed

Detected by Pingoru
Oct 01, 2026, 05:59 PM UTC
Resolved
Oct 01, 2026, 07:18 PM UTC
Duration
1h 18m
Affected: Data IngestionIntegrations
Timeline · 5 updates
  1. investigating Oct 01, 2026, 05:59 PM UTC

    We are observing a delay in delivering notifications to 3rd parties and updating analytics events.

  2. identified Oct 01, 2026, 06:01 PM UTC

    The issue is related to an outage in upstream service outage. We are monitoring the systems and working on a workaround.

  3. identified Oct 01, 2026, 06:34 PM UTC

    Implemented a workaround to unblock and process notifications to 3rd party integrations

  4. monitoring Oct 01, 2026, 06:53 PM UTC

    We implemented a workaround and currently are processing the backlog of events and data sync requests.

  5. resolved Oct 01, 2026, 07:18 PM UTC

    This incident has been resolved, our workarounds are keeping everything in sync. We are monitoring the upstream dependency outage.

Read the full incident report →

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 →