Pyth Network Outage History
19 incidents recorded over the last 365 days, 19 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Pyth Network Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 2, 2026 | Service Degradation for Pyth Pro Historical Data and HermesThe issue with Pyth Pro Historical Data and Hermes endpoints has been resolved. All systems are now operating normally. | -150 min | Resolved |
| Aug 12, 2026 | Pyth Pro API and WebSocket IncidentAll 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… | -495 min | Resolved |
| Aug 4, 2026 | Pyth Pro Service Degradation 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… | -8426 min | Resolved |
| Jul 6, 2026 | Delayed Price Data 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… | -4224 min | Resolved |
| Jun 16, 2026 | Pyth Pro HTTP Endpoints DowntimeThe issue with **Pyth Pro HTTP Endpoints** has been resolved. All systems are now operating normally. | -7986 min | Resolved |
| Jun 2, 2026 | Pyth Pro Database Write FailurePyth Pro historical database is now operating as expected again. These issues stemmed from underlying Clickhouse issues. All missed data has already been backfilled. | -231 min | Resolved |
| Jun 2, 2026 | Pyth Pro Database Write FailurePyth Pro historical database is now operating as expected again. These issues stemmed from underlying Clickhouse issues. All missed data has already been backfilled. | -520 min | Resolved |
| May 22, 2026 | URGENT - Pythnet/Hermes Downtime 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… | 6h 5m | Resolved |
| Dec 24, 2025 | Pyth Pro Service Degradation The issue with **Pyth Pro** has been resolved. All systems are now operating normally. | -1057 min | Resolved |
| Dec 24, 2025 | Pyth Pro Service Degradation The issue with **Pyth Pro** has been resolved. All systems are now operating normally. | -1074 min | Resolved |
| Dec 24, 2025 | Pyth Pro Service DegradationThe issue with **Pyth Pro** has been resolved. All systems are now operating normally. _Postmortem summary coming soon._ | -1101 min | Resolved |
| Dec 15, 2025 | Delayed Pushed Feeds on SuiThe issue with the **Push Feeds on Sui** have now been resolved. All systems are now operating normally. Issues arose as Sui released fixes locked accounts that the Push Feeds were using. Other users were still able… | -565 min | Resolved |
| Dec 14, 2025 | Pyth Pro (Lazer) Service InterruptionThe issue with **Pyth Lazer** has been resolved. All systems have now been operating normally for quite some time. | 24h 36m | Resolved |
| Dec 4, 2025 | Pyth Pro (Lazer) Service InterruptionAll systems have been restored and are operating normally. Our team is conducting a thorough investigation to determine the root cause. We will provide a detailed post-mortem analysis once the investigation is… | 4 min | Resolved |
| Nov 21, 2025 | Pyth Lazer Sequencer IssuesThe issue with **Pyth Lazer** has been resolved. All systems are now operating normally. For about 10 seconds, no prices were produced. | -46 min | Resolved |
| Nov 21, 2025 | Pyth Lazer Sequencer IssuesThe issue with **Pyth Lazer** has been resolved. All systems are now operating normally. For about 10 seconds, no prices were produced. | -209 min | Resolved |
| Nov 18, 2025 | Public Hermes Downtime due to Cloudflare Global OutageThe issue with **the public Hermes endpoint and Benchmarks** have been resolved. All systems are now operating normally. _Reminder that end users should get dedicated / private endpoints from providers to maximize… | -93 min | Resolved |
| Nov 18, 2025 | Public Hermes UnavailableThe issue with **Hermes** has been resolved. All systems are now operating normally. | 1h 39m | Resolved |
| Nov 15, 2025 | Missing Historical Data The issue with **Benchmarks** has been resolved. All systems are now operating normally. Root cause stem from ongoing Teraswitch issues which caused the public historical database to fail storing data. | -118 min | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Pyth Network incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Pyth Network Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Pyth Network acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Pyth Network outage in this window ran 1d, against a mean recovery of 8h 6m. If you depend on Pyth Network in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.