Pyth Network Outage History

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)

Status: Resolved All systems are currently operating normally. However, no prices were produced by Pyth during the incident window. As a result, historical price data and OHLC candlesticks for that period are unavailable and will not be backfilled.

Status: Resolved Pyth Pro experienced a service degradation due to network issues at one of our infrastructure providers. The affected period was 19:09:34 - 19:48:00 UTC and during this time users may have seen delayed price updates, HTTP requests failures and websocket disconnections. Affected components Kraken Mainnet (Operational) HyperEVM Mainnet (Operational) Sonic Mainnet (Operational) Aptos (Operational) Sui (Operational) Fortuna (Operational) Hermes beta (Operational) Base Mainnet (Operational) Hermes (Operational) Berachain Mainnet (Operational) Ethereum Mainnet (Operational) Unichain Mainnet (Operational) Benchmarks beta (Operational) Benchmarks (Operational) Pythnet (Operational) Movement (Operational) Fortuna staging (Operational) Live Data (Operational) Linea Mainnet (Operational) Solana (Operational) Pythtest (Operational) Historical Data (Operational) Avalanche (Operational) Arbitrum (Operational)

Status: Resolved Pyth Pro experienced a service degradation due to network issues at one of our infrastructure providers. The affected period was 14:10:39 - 14:11:09 UTC and during this time users may have seen delayed price updates on some feeds Affected components Sonic Mainnet (Operational) Historical Data (Operational) Arbitrum (Operational) Unichain Mainnet (Operational) Fortuna (Operational) Benchmarks beta (Operational) Live Data (Operational) Avalanche (Operational) Linea Mainnet (Operational) HyperEVM Mainnet (Operational) Solana (Operational) Movement (Operational) Sui (Operational) Fortuna staging (Operational) Hermes beta (Operational) Pythtest (Operational) Benchmarks (Operational) Base Mainnet (Operational) Pythnet (Operational) Kraken Mainnet (Operational) Hermes (Operational) Berachain Mainnet (Operational) Ethereum Mainnet (Operational) Aptos (Operational)

Status: Resolved Pyth Pro historical database is now operating as expected again. These issues stemmed from underlying Clickhouse issues. All missed data has already been backfilled. Affected components Kraken Mainnet (Operational) Sonic Mainnet (Operational) Aptos (Operational) Movement (Operational) Fortuna staging (Operational) HyperEVM Mainnet (Operational) Hermes (Operational) Ethereum Mainnet (Operational) Unichain Mainnet (Operational) Fortuna (Operational) Live Data (Operational) Historical Data (Operational) Pythnet (Operational) Solana (Operational) Hermes beta (Operational) Pythtest (Operational) Avalanche (Operational) Benchmarks (Operational) Berachain Mainnet (Operational) Sui (Operational) Benchmarks beta (Operational) Arbitrum (Operational) Linea Mainnet (Operational) Base Mainnet (Operational)