Hex PM Outage History
Hex PM is up right nowPingoru has recorded 3 incidents for Hex PM: 1 in the last 12 months and 1 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| July 2026 | 1 | 1 of 744 (0%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 512 (0%) |
Incidents, newest first
Major July 29, 2026 Outage 1h 12m Hex.pm Website & API, Private repository (organizations), Private HexDocs (organizations)
Started Jul 29, 2026, 06:45 PM UTC· resolved Jul 29, 2026, 07:57 PM UTC
- investigating Jul 29, 2026, 06:45 PM UTC
We are currently investigating this issue.
- identified Jul 29, 2026, 06:58 PM UTC
The hex.pm website and API are unavailable. The cause is a surge of automated traffic against package file preview pages, which exhausted memory on the web servers and took them out of rotation. We are applying mitigations now. Public package downloads and hexdocs.pm are not affected. Private package downloads and private documentation that triggers reauthentication will currently fail due to the website and API outage.
- monitoring Jul 29, 2026, 07:12 PM UTC
hex.pm and the API are responding normally again as of 19:11 UTC. The cause was a surge of automated traffic against package file preview pages, which exhausted memory on the web servers. We have blocked that traffic at the edge and raised capacity limits. Package file preview pages are temporarily returning errors while the block is in place.
- monitoring Jul 29, 2026, 07:20 PM UTC
We are continuing to monitor for any further issues.
- resolved Jul 29, 2026, 07:57 PM UTC
hex.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. Because each of those requests unpacks a package archive, the volume exhausted memory on the web servers and took them out of rotation, which is why the site returned errors. We have put rate limiting in place at the edge and raised capacity limits. The traffic is still arriving and is being rate limited. We are continuing to monitor.