InternetComputer Outage History

21 incidents recorded over the last 365 days, 11 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 InternetComputer status100.00% uptime history

Every Recorded InternetComputer Incident

InternetComputer incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 29, 2026Application Subnet is StalledThis incident has been resolved.1h 7mResolved
Oct 23, 2026Switching dashboard.internetcomputer.org to new on-chain dashboardThe scheduled maintenance has been completed.30 minScheduled
Oct 19, 2026Key resharing maintenance on subnet uzr34 (II subnet)The scheduled maintenance has been completed.30 minScheduled
Sep 1, 2026ckBTC ledger temporarily unavailableThis incident has been resolved.21h 50mResolved
Jul 25, 2026Application Subnet is stalledThe incident has been resolved.3h 59mResolved
Jul 15, 2026Dashboard metrics maintenanceThe scheduled maintenance has been completed.30 minScheduled
May 2, 2026Public dashboard API impairedThis incident has been resolved.2h 36mResolved
Apr 1, 2026Updating ICRC API Token DataThe scheduled maintenance has been completed.2h 0mScheduled
Mar 26, 2026Tuning resource requests and limitsThe scheduled maintenance has been completed.1h 0mScheduled
Mar 16, 2026Switching dashboard-ui over to new prod clusterThe scheduled maintenance has been completed.1h 0mScheduled
Mar 12, 2026ledger-api updateThe scheduled maintenance has been completed.1h 0mScheduled
Mar 9, 2026Switching ic-api over to a new clusterThe scheduled maintenance has been completed.1h 0mScheduled
Feb 28, 2026Application Subnet is stalledThis incident has been resolved.9h 22mResolved
Feb 23, 2026Switch ledger-api, sns-api, and icrc-api over to the new prod clusterThe scheduled maintenance has been completed.2h 0mScheduled
Feb 19, 2026Switchover metrics-api to new prod clusterThe scheduled maintenance has been completed.1h 0mScheduled
Jan 28, 2026icrc-api outageicrc-api was down due to a migration taking an exclusive lock on the database. The migration took 3.5 hours...-1965 minResolved
Jan 13, 2026Subnet pjljw stalledThis incident has been resolved.28 minResolved
Dec 11, 2025Subnet `mpubz` stalledThis incident has been resolved.2h 21mResolved
Dec 3, 2025Issue with the BNs/HTTP gatewaysThis incident has been resolved.24 minResolved
Nov 18, 2025Cloudflare outage induced dashboard errorsThis incident has been resolved.14h 14mResolved
Nov 18, 2025Dashboard errorsThis incident has been resolved.6 minResolved

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 InternetComputer 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 InternetComputer 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 InternetComputer 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 InternetComputer outage in this window ran 21h 50m, against a mean recovery of 3h 21m. If you depend on InternetComputer 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.