Pyth Network incident

Pyth Pro API and WebSocket Incident

Minor Resolved View vendor source →

Pyth Network experienced a minor incident on August 12, 2026 affecting Historical Data and Live Data, lasting —. The incident has been resolved; the full update timeline is below.

Started
Aug 12, 2026, 04:24 AM UTC
Resolved
Aug 12, 2026, 04:24 AM UTC
Duration
Detected by Pingoru
Aug 12, 2026, 04:24 AM UTC

Affected components

Historical DataLive Data

Update timeline

  1. investigating Aug 12, 2026, 03:49 AM UTC

    Status: Investigating We’re currently investigating an incident affecting Pyth Pro API and WebSocket streaming endpoints. Current impact: Data is not currently available. We’ll share more updates as soon as we have them. Affected components Live Data (Full outage) Historical Data (Full outage)

  2. resolved Aug 12, 2026, 04:24 AM UTC

    Status: Resolved The issue with Pyth Pro API and WebSocket streaming endpoints have been resolved. All systems are now operating normally. The incident was caused by a major outage: https://www.teraswitchstatus.com/incidents/kwg2ffkjg5q1 at TeraSwitch, a data center provider hosting part of our infrastructure. At the time, two of four NATS nodes were hosted in TeraSwitch facilities. When those nodes became unreachable, NATS lost quorum and dependent Router services became unavailable. We had already been working to improve infrastructure redundancy and reduce provider concentration. This work is now being accelerated, including onboarding an additional infrastructure provider and distributing critical services across independent failure domains. The goal is to ensure that a future outage affecting any single infrastructure provider does not result in a broader service disruption. Affected components Live Data (Operational) Historical Data (Operational)