Tezos Outage History

13 incidents recorded over the last 365 days, 13 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.

Live Tezos status100.00% uptime history

Every Recorded Tezos Incident

Tezos incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Nov 4, 2026TzKT Explorer is down15h 8mResolved
Nov 2, 2026Scheduled maintenance - Octez.Connect nodes 1, 3, 5 and 730 minResolved
Oct 30, 2026Scheduled maintenance - Octez.Connect nodes 2, 4, 6 and 88 minResolved
Oct 8, 2026Scheduled hardware maintenance — Octez.Connect Node 12h 2mResolved
Sep 16, 2026FINN is down1203h 11mResolved
Sep 15, 2026FINN is down1215h 35mResolved
Sep 10, 2026FINN is down1341h 11mResolved
Aug 20, 2026FINN is down1740h 8mResolved
Jul 28, 2026Octez.Connect Node 1, Octez.Connect Node 3, and 2 other services are down1543h 47mResolved
Jul 20, 2026Octez.Connect Node 2, Octez.Connect Node 4, and 2 other services are down1742h 20mResolved
Jul 12, 2026FINN is down1933h 32mResolved
Jul 3, 2026FINN is down2150h 16mResolved
Jun 4, 2026Octez.Connect Node 1 and Octez.Connect Node 3 are down2127h 25mResolved

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 Tezos 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 Tezos 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 Tezos 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 Tezos outage in this window ran 89d 14h, against a mean recovery of 48d 3h. If you depend on Tezos 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.