Is Pyth Network down?
Last checked 3m agoNo incidents right now.
Pyth Network is operational right now. Last checked 3m ago; the most recent incident resolved 80d ago.
Real-time Pyth Network status, recent outages, and incident history: pulled directly from Pyth Network's official status page at status.pyth.network every 5 minutes. Pingoru tracks 20 Pyth Network services and has captured 2 incidents in the last 90 days (99.78% uptime). Get email, Slack, Discord, or webhook alerts the moment Pyth Network reports a new incident, free for 3 monitors, no credit card.
Recent outages & incidents
Past 90 days-
Timeline · 1 update
- investigating · Aug 12, 2026, 04:54 PM UTC
Status: Investigating This is a temporary public test incident for incident workflow verification. No customer impact.
Latest: Status: Investigating This is a temporary public test incident for incident workflow verification. No customer impact.
-
- Historical DataLive Data
Timeline · 3 updates
- 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)
- 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)
- resolved · Aug 14, 2026, 11:16 AM UTC
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.
Latest: 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 cand…
-
Incident record
Since April 2026 · incident.io · 20 components checked every 5 minutesThe longest incident in the last year, Pyth Pro API and WebSocket Incident on August 12, 2026, ran for 2 days.
Most affected components, last 12 months
- Aptos6
- Arbitrum6
- Avalanche6
- Base Mainnet6
- Benchmarks6
Latest incidents
- [TEST] Dummy incident — Apollo verification
Status: Investigating This is a temporary public test incident for incident workflow verification. No customer impact.
- Pyth Pro API and WebSocket Incident
Status: Investigating We’re currently investigating an incident affecting Pyth Pro API and WebSocket streaming endpoints. Current impact: Data is not currently…
- Pyth Pro Service Degradation
Status: Investigating We’re currently investigating an incident affecting Pyth Pro. We’ll share more updates as soon as we have them. Affected components…
- Started Aug 12, 2026, 04:54 PM UTC · Resolved Aug 12, 2026, 05:18 PM UTC · 23m
- Pyth Pro API and WebSocket Incident ResolvedStarted Aug 12, 2026, 03:49 AM UTC · Resolved Aug 14, 2026, 11:16 AM UTC · 2d 7h