Pyth Network Outage History

Pyth Network is up right now

Pingoru has recorded 21 incidents for Pyth Network: 19 in the last 12 months and 3 in the last 90 days.

Source: status.pyth.network

21incidents recorded
19last 12 months
3last 90 days
5 hourstypical duration
Incidents per month
024AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Pyth Network in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202616 of 744 (1%)
June 202631 of 720 (0%)
July 202621 of 744 (0%)
August 2026256 of 744 (7%)
September 202600 of 720 (0%)
October 202600 of 554 (0%)

Incidents, newest first

Major August 12, 2026 [TEST] Dummy incident — Apollo verification 23m

Started Aug 12, 2026, 04:54 PM UTC· resolved Aug 12, 2026, 05:18 PM UTC

  1. investigating Aug 12, 2026, 04:54 PM UTC

    This is a temporary public test incident for incident workflow verification. No customer impact.

Read the full incident report →

Minor August 12, 2026 Pyth Pro API and WebSocket Incident 2d 7h Historical Data, Live Data

Started Aug 12, 2026, 03:49 AM UTC· resolved Aug 14, 2026, 11:16 AM UTC

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

    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.

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

    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.

  3. resolved Aug 14, 2026, 11:16 AM UTC

    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.

Read the full incident report →

Minor July 29, 2026 Pyth Pro Service Degradation 39m Historical Data, Hermes, HyperEVM Mainnet, Monad and 20 more

Started Jul 29, 2026, 07:09 PM UTC· resolved Jul 29, 2026, 07:48 PM UTC

  1. investigating Jul 29, 2026, 11:09 PM UTC

    We’re currently investigating an incident affecting Pyth Pro. We’ll share more updates as soon as we have them.

  2. resolved Jul 29, 2026, 11:48 PM UTC

    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.

Read the full incident report →

Minor July 3, 2026 Delayed Price Data 1m Historical Data, Hermes, HyperEVM Mainnet, Monad and 20 more

Started Jul 03, 2026, 12:10 PM UTC· resolved Jul 03, 2026, 12:11 PM UTC

  1. investigating Jul 03, 2026, 12:10 PM UTC

    Pyth Pro is experiencing a service degradation due to network issues at one of our infrastructure providers. Users may experience delayed price updates on some feeds.

  2. resolved Jul 03, 2026, 12:11 PM UTC

    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

Read the full incident report →

Minor June 10, 2026 Pyth Pro HTTP Endpoints Downtime 15m Historical Data, Hermes, HyperEVM Mainnet, Monad and 20 more

Started Jun 10, 2026, 06:38 PM UTC· resolved Jun 10, 2026, 06:53 PM UTC

  1. investigating Jun 10, 2026, 06:38 PM UTC

    We’re currently investigating an incident affecting Pyth Pro HTTP Endpoints. Current impact: Any client performing standard TLS validation (browsers, SDKs, most WebSocket/HTTP libraries) would reject the certificate during the TLS handshake, so all new HTTPS/WSS connections to pyth-lazer-{0,1,2}.dourolabs.app are failing. Already-established WebSocket streams are not unaffected, because the certificate is only validated at handshake time. We’ll share more updates as soon as we have them.

  2. resolved Jun 10, 2026, 06:53 PM UTC

    The issue with Pyth Pro HTTP Endpoints has been resolved. All systems are now operating normally.

Read the full incident report →

Minor June 2, 2026 Pyth Pro Database Write Failure 16m Historical Data, Hermes, HyperEVM Mainnet, Monad and 20 more

Started Jun 02, 2026, 04:34 PM UTC· resolved Jun 02, 2026, 04:50 PM UTC

  1. investigating Jun 02, 2026, 04:34 PM UTC

    Pyth Pro historical database is currently facing issues coming from Clickhouse cloud issues. Some historical data is not being successfully stored in the public historical database accessible via API.

  2. resolved Jun 02, 2026, 04:50 PM UTC

    Pyth Pro historical database is now operating as expected again. These issues stemmed from underlying Clickhouse issues. All missed data has already been backfilled.

Read the full incident report →

Minor May 22, 2026 URGENT - Pythnet/Hermes Downtime 6h 5m Hermes, HyperEVM Mainnet, Monad, Sui and 13 more

Started May 22, 2026, 06:58 AM UTC· resolved May 22, 2026, 01:04 PM UTC

  1. identified May 22, 2026, 06:58 AM UTC

    The Wormhole Guardians stopped observing prices on Pythnet and since no proofs have been created. We are working to resolve this ASAP with Pythnet validators. Apologies for the inconvenience caused. Any questions please let us know. Please note that Pyth Pro (Lazer) is operating as expected. If you wish to move onto Pyth Pro infrastructure, please create an account on the terminal: https://app.pyth.com/explore And follow the documentation here: https://docs.pyth.network/price-feeds/pro

  2. identified May 22, 2026, 10:34 AM UTC

    We’ve identified the root cause of the issue affecting Pythnet (Pyth Core/Hermes). The validators are coordinating a restart currently which hopefully should have the Pyth Core Feeds and Sponsored Feeds resume by 12.30 PM UTC. We'll keep you updated as things evolve.

  3. monitoring May 22, 2026, 12:26 PM UTC

    The issue with Pythnet/Pyth Core Feeds has been resolved. However, the Hermes endpoints are still not exposing prices. We are actively working on this. Please note that Pyth Pro/Lazer continued operating as expected. You can start your migration here: https://docs.pyth.network/price-feeds/pro/getting-started Postmortem summary coming soon.

  4. resolved May 22, 2026, 01:04 PM UTC

    The issue with Hermes endpoints and Sponsored Feeds have now been resolved. All systems are now operating normally. Please note that Pyth Pro / Lazer continued operating normally throughout. To migrate, please see: https://docs.pyth.network/price-feeds/pro/getting-started Postmortem summary coming soon.

Read the full incident report →

Minor December 23, 2025 Pyth Pro Service Degradation –

Started Dec 23, 2025, 02:23 PM UTC· resolved Dec 23, 2025, 02:23 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Critical December 15, 2025 Delayed Pushed Feeds on Sui –

Started Dec 15, 2025, 06:30 AM UTC· resolved Dec 15, 2025, 06:30 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Critical December 14, 2025 Pyth Pro (Lazer) Service Interruption 1d

Started Dec 14, 2025, 03:10 PM UTC· resolved Dec 15, 2025, 03:47 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Critical December 4, 2025 Pyth Pro (Lazer) Service Interruption 4m

Started Dec 04, 2025, 08:35 AM UTC· resolved Dec 04, 2025, 08:40 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Critical November 21, 2025 Pyth Lazer Sequencer Issues –

Started Nov 21, 2025, 12:26 PM UTC· resolved Nov 21, 2025, 12:26 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Critical November 18, 2025 Public Hermes Downtime due to Cloudflare Global Outage –

Started Nov 18, 2025, 02:20 PM UTC· resolved Nov 18, 2025, 02:20 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Critical November 18, 2025 Public Hermes Unavailable 1h 39m

Started Nov 18, 2025, 01:50 PM UTC· resolved Nov 18, 2025, 03:30 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Critical November 15, 2025 Missing Historical Data –

Started Nov 15, 2025, 01:38 PM UTC· resolved Nov 15, 2025, 01:38 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Major October 14, 2025 Delayed Historical Data for Lazer –

Started Oct 14, 2025, 01:18 PM UTC· resolved Oct 14, 2025, 01:18 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Critical October 13, 2025 Delayed Push Feeds on Sonic –

Started Oct 13, 2025, 07:37 AM UTC· resolved Oct 13, 2025, 07:37 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →