Hex Outage History
2 incidents recorded over the last 365 days, 1 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 Hex Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Aug 30, 2026 | Database upgradeThe scheduled maintenance has been completed. The database upgrade is complete. hex.pm is running on PostgreSQL 18. Requests paused for 21 seconds during the switch; no requests failed. | 1h 0m | Scheduled |
| Jul 29, 2026 | Outagehex.pm and the API have been stable since 19:11 UTC, and package file preview pages have been serving normally since 19:36 UTC. The cause was a sustained flood of automated traffic against package file preview pages… | 1h 12m | 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 Hex 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 Hex 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 Hex 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 Hex outage in this window ran 1h 12m, against a mean recovery of 1h 6m. If you depend on Hex 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.