Avalanche Outage History
4 incidents recorded over the last 365 days, 4 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 Avalanche Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Sep 19, 2026 | Mainnet API degradedThis incident has been resolved. | 1h 1m | Resolved |
| Sep 8, 2026 | ICM Relayer and C-Chain RPC outage on AvaCloudContinued monitoring showed no further issues. All services are back to regular operation in all supported regions. | 31h 8m | Resolved |
| Jul 28, 2026 | Fuji(Testnet) C-Chain Helicon Block IndexingThis incident has been resolved. | 2h 4m | Resolved |
| Nov 22, 2025 | AvaCloud new L1 creation issueThis incident has been resolved. | 68h 9m | 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 Avalanche 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 Avalanche 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 Avalanche 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 Avalanche outage in this window ran 2d 20h, against a mean recovery of 1d 1h. If you depend on Avalanche 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.