Chord Outage History

Chord is up right now

Chord had 13 outages in the last 2 years totaling 79h 50m of downtime — averaging 0.5 incidents per month.

There were 13 Chord outages since February 10, 2025 totaling 79h 50m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.chord.co

Notice July 7, 2026

Infrastructure issue

Detected by Pingoru
Jul 07, 2026, 04:22 AM UTC
Resolved
Jul 07, 2026, 06:48 AM UTC
Duration
2h 26m
Affected: Hub
Timeline · 4 updates
  1. investigating Jul 07, 2026, 04:22 AM UTC

    We are investigating an infrastructure issue impacting Chord AI

  2. investigating Jul 07, 2026, 04:23 AM UTC

    We are continuing to investigate this issue.

  3. investigating Jul 07, 2026, 06:45 AM UTC

    This incident has been resolved. Chord Hub is fully operational again. We apologize for the disruption. If you continue to experience issues, please contact support.

  4. resolved Jul 07, 2026, 06:48 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 11, 2026

Investigating — Chord Hub unavailable

Detected by Pingoru
Jun 11, 2026, 03:25 PM UTC
Resolved
Jun 11, 2026, 04:01 PM UTC
Duration
36m
Affected: Hub
Timeline · 2 updates
  1. investigating Jun 11, 2026, 03:25 PM UTC

    We are currently investigating an issue causing the Chord Hub to be unavailable. Our team is actively working to identify the cause. We will provide another update as soon as we have more information. We apologize for the disruption.

  2. resolved Jun 11, 2026, 04:01 PM UTC

    This incident has been resolved. Chord Hub is fully operational again. We apologize for the disruption. If you continue to experience issues, please contact support.

Read the full incident report →

Notice May 22, 2026

Chord Copilot Outage

Detected by Pingoru
May 22, 2026, 01:56 PM UTC
Resolved
May 22, 2026, 02:08 PM UTC
Duration
12m
Affected: Hub
Timeline · 3 updates
  1. investigating May 22, 2026, 01:56 PM UTC

    Our engineering team is actively investigating the issue, and we will provide updates as soon as possible.

  2. monitoring May 22, 2026, 02:06 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved May 22, 2026, 02:08 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 20, 2026

Degraded performance - Chord Copilot

Detected by Pingoru
May 20, 2026, 02:50 PM UTC
Resolved
May 20, 2026, 04:28 PM UTC
Duration
1h 37m
Affected: Hub
Timeline · 2 updates
  1. identified May 20, 2026, 02:50 PM UTC

    We have identified an issue causing degraded performance with Chord Copilot. We are monitoring and will provide updates as soon as possible.

  2. resolved May 20, 2026, 04:28 PM UTC

    This incident with our third-party provider has been resolved.

Read the full incident report →

Notice May 18, 2026

Chord Copilot Service Disruptions

Detected by Pingoru
May 18, 2026, 02:35 PM UTC
Resolved
May 18, 2026, 03:30 PM UTC
Duration
54m
Affected: Hub
Timeline · 2 updates
  1. investigating May 18, 2026, 02:35 PM UTC

    We are currently investigating an issue affecting Chord Copilot. Some users may experience errors. Our team is actively working to identify the cause. We will provide updates as more information becomes available.

  2. resolved May 18, 2026, 03:30 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice November 18, 2025

Chord CDP - Degraded Performance

Detected by Pingoru
Nov 18, 2025, 02:00 PM UTC
Resolved
Nov 18, 2025, 09:29 PM UTC
Duration
7h 28m
Affected: Chord CDP
Timeline · 3 updates
  1. investigating Nov 18, 2025, 02:00 PM UTC

    Chord CDP is experiencing degraded performance. This is an identified issue with a third-party service provider and is currently being resolved.

  2. monitoring Nov 18, 2025, 02:01 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Nov 18, 2025, 09:29 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice November 18, 2025

Chord OMS - Partial Degradation

Detected by Pingoru
Nov 18, 2025, 01:51 PM UTC
Resolved
Nov 18, 2025, 09:30 PM UTC
Duration
7h 39m
Affected: OMS
Timeline · 2 updates
  1. monitoring Nov 18, 2025, 01:51 PM UTC

    Brand customers may experience issues when checking out on storefronts. This is an identified issue with a third-party service provider and is currently being resolved.

  2. resolved Nov 18, 2025, 09:30 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice November 18, 2025

Chord Platform - Degraded Service

Detected by Pingoru
Nov 18, 2025, 01:31 PM UTC
Resolved
Nov 18, 2025, 09:30 PM UTC
Duration
7h 59m
Affected: Hub
Timeline · 3 updates
  1. monitoring Nov 18, 2025, 01:31 PM UTC

    Customers may experience issues when trying to access the Chord platform. This is an identified issue with a third-party service provider and is currently being resolved.

  2. monitoring Nov 18, 2025, 09:30 PM UTC

    This incident has been resolved.

  3. resolved Nov 18, 2025, 09:30 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice November 18, 2025

Chord Documentation Outage

Detected by Pingoru
Nov 18, 2025, 01:19 PM UTC
Resolved
Nov 18, 2025, 09:30 PM UTC
Duration
8h 11m
Affected: Documentation
Timeline · 3 updates
  1. monitoring Nov 18, 2025, 01:19 PM UTC

    Chord's documentation site is currently experiencing an outage. Documentation may not be accessible during this time. The incident has been recorded and is being investigated.

  2. monitoring Nov 18, 2025, 01:20 PM UTC

    We are continuing to monitor for any further issues.

  3. resolved Nov 18, 2025, 09:30 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 5, 2025

Chord Docs Platform Disruption: Partial Outage and Performance Degradation

Detected by Pingoru
Aug 05, 2025, 05:14 PM UTC
Resolved
Aug 06, 2025, 01:43 PM UTC
Duration
20h 29m
Affected: Documentation
Timeline · 2 updates
  1. monitoring Aug 05, 2025, 05:14 PM UTC

    We’ve identified a partial outage affecting our documents site—some users may experience slow performance. We are monitoring the system continuously to ensure full functionality as quickly as possible.

  2. resolved Aug 06, 2025, 01:43 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 4, 2025

Chord Docs Platform Disruption: Partial Outage and Performance Degradation Resolved

Detected by Pingoru
Aug 04, 2025, 07:18 PM UTC
Resolved
Aug 05, 2025, 12:31 PM UTC
Duration
17h 13m
Affected: Documentation
Timeline · 2 updates
  1. monitoring Aug 04, 2025, 07:18 PM UTC

    We’ve identified a partial outage affecting our documents site—some users may experience slow performance. We are monitoring the system continuously to ensure full functionality as quickly as possible.

  2. resolved Aug 05, 2025, 12:31 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 19, 2025

Chord Activations are currently unavailable on the platform.

Detected by Pingoru
Mar 19, 2025, 10:10 PM UTC
Resolved
Mar 20, 2025, 01:26 AM UTC
Duration
3h 15m
Affected: Hub
Timeline · 2 updates
  1. investigating Mar 19, 2025, 10:10 PM UTC

    We are currently investigating this issue and will provide an update once the issue is identified and fixed.

  2. resolved Mar 20, 2025, 01:26 AM UTC

    This incident has been resolved. Chord Activations functionality has been restored on our platform.

Read the full incident report →

Critical February 10, 2025

Systemwide Outage

Detected by Pingoru
Feb 10, 2025, 05:38 PM UTC
Resolved
Feb 10, 2025, 07:26 PM UTC
Duration
1h 47m
Affected: HubOMSAPI
Timeline · 4 updates
  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.

Read the full incident report →