Zenhub Outage History

11 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 Zenhub status100.00% uptime history

Every Recorded Zenhub Incident

Zenhub incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 24, 2026Infrastructure upgradeMaintenance is still ongoing. The Zenhub app continues to be operational but may experience temporary delays and brief outages until the upgrades are completed.59 minResolved
Aug 21, 2026Zenhub is seeing elevated error rates; performance may be degradedThe incident has been resolved.1172h 30mResolved
Aug 19, 2026Zenhub is seeing elevated error rates; performance may be degradedThe incident has been resolved.1224h 31mResolved
Aug 17, 2026Zenhub is seeing elevated error rates; performance may be degradedThe incident has been resolved.1270h 24mResolved
Aug 17, 2026Zenhub is seeing elevated error rates; performance may be degradedThe incident has been resolved.10h 32mResolved
Jun 10, 2026Zenhub is seeing elevated error rates; performance may be degradedGitHub has fixed the incident on their end.1h 1mResolved
Feb 9, 2026GitHub OutageThe incident has been resolved.1h 50mResolved
Dec 12, 2025Zenhub is seeing elevated error rates; performance may be degradedThe incident has been resolved.17 minResolved
Dec 12, 2025Zenhub is seeing elevated error rates; performance may be degradedThe incident has been resolved.44 minResolved
Dec 10, 2025Zenhub is seeing elevated error rates; performance may be degradedThe incident has been resolved.28 minResolved
Dec 9, 2025Zenhub is seeing elevated error rates; performance may be degradedThe incident has been resolved.0 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 Zenhub 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 Zenhub 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 Zenhub 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 Zenhub outage in this window ran 52d 22h, against a mean recovery of 13d 22h. If you depend on Zenhub 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.