Chord incident

Systemwide Outage

Critical Resolved View vendor source →

Chord experienced a critical incident on February 10, 2025 affecting Hub and OMS and 1 more component, lasting 1h 47m. The incident has been resolved; the full update timeline is below.

Started
Feb 10, 2025, 05:38 PM UTC
Resolved
Feb 10, 2025, 07:26 PM UTC
Duration
1h 47m
Detected by Pingoru
Feb 10, 2025, 05:38 PM UTC

Affected components

HubOMSAPI

Update timeline

  1. investigating Feb 10, 2025, 05:38 PM UTC

    Chord is currently experiencing an unexpected service outage. Our technical teams are actively investigating the issue and working to restore full functionality as quickly as possible. Users may experience login failures in the Chord data platform and legacy services.

  2. investigating Feb 10, 2025, 05:40 PM UTC

    We are continuing to investigate this issue.

  3. identified Feb 10, 2025, 07:15 PM UTC

    We are continuing to investigate this issue.

  4. resolved Feb 10, 2025, 07:26 PM UTC

    The incident has been resolved. The Chord data platform and legacy services are now fully operational.