Hex logo

Is Hex Down?

SaaSLive status, outages, and incident history

No. Hex is up right now.

Every monitored Hex system is operational as of September 25, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 5m agoLive · 60s while moving

Know the moment Hex breaks

Hex is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

Free, no password, no card. Unsubscribe in one click.

Official Hex status page
How we know: the official Hex status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

Hex Component Status

The main Hex systems on this page. All 6 are operational right now.

6operational
Billing
Operational
Hex.pm Website & API
Operational
HexDocs
Operational

3 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Private HexDocs, Private repository, Repository.

See all of them free

Component statuses may change independently during partial outages.

Recent Hex Outages & Incidents

Incident history from the official Hex status page, including resolution updates.

Database upgradeScheduled for Aug 30, 2026 · 1h 0mScheduled

The 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. --- [2026-08-30T12:00:07.428Z] (in_progress) Scheduled maintenance is currently in progress. We will provide updates as necessary. --- [2026-08-30T11:10:16.892Z] (scheduled) hex.pm is upgrading its database to PostgreSQL 18. Expected impact: during a window of under a minute, requests to hex.pm and the hex.pm API will pause for up to ~30 seconds and then complete; no requests are expected to fail. This includes package publishing, private package downloads, and access to private documentation, all of which authenticate against hex.pm. Background jobs (emails, builds) pause for a few minutes. Public package downloads via repo.hex.pm and public documentation on hexdocs.pm are not affected.

OutageResolved Jul 29, 2026 · 1h 12mResolved

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. --- [2026-07-29T19:20:31.899Z] (monitoring) We are continuing to monitor for any further issues. --- [2026-07-29T19:12:47.201Z] (monitoring) 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. --- [2026-07-29T18:58:21.805Z] (identified) 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. --- [2026-07-29T18:45:02.367Z] (investigating) We are currently investigating this issue.

Hex Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Hex incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history49 days observed
Aug 8100.00% average · 1 day with incidentsSep 25

Live Hex Outage Reports

Problems reported by engineers using Hex. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Hex problems reported yet.

Something wrong with Hex on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Hex

Is Hex down? Hex reports live availability for 6 components at status.hex.pm, among them Hex.pm Website & API, Repository and HexDocs. Track Hex outages, degradations and past incidents here, with uptime history and alerts across your SaaS stack.

Over the past 30 days, PulsAPI has measured Hex uptime at 100.00%. Response times, incident history, and SLA tracking for Hex are available on the PulsAPI dashboard.

Hex Status FAQ

Is Hex down right now?

The verdict at the top of this page comes from the latest poll of the official Hex status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

What should I do if Hex is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Hex recovers.

How do I check Hex uptime history?

PulsAPI tracks Hex uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Hex changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Hex outages?

PulsAPI reads the official Hex status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual Hex components?

Yes. PulsAPI monitors 6 individual Hex components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Hex goes down?

Yes. Create a free account and subscribe to Hex: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Hex to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Hex problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Hex?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Hex plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Hex with the rest of your stack

2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services