Documentation pages down
ResolvedOfficial update
Issue upstream appears to be fixed.
The latest update from Hume AI.
State
Resolved
Started
20 d ago
2026-10-12 17:30 UTC
Lasted
29 min
until 2026-10-12 18:00 UTC
Worst impact
Major outage
Timeline
2 updates17:3017:3817:4517:5218:00
Major outageUpdate postedTimes in UTC
Identified
29 min 100%
Updates
Times in UTCAs posted by Hume AI
Resolved2026-10-12 18:00 UTC
Issue upstream appears to be fixed.
Identified2026-10-12 17:16 UTC
Our documentation pages are down because one of our providers, Fern, is having an outage.
Hume AI in the last 90 days
Full history90 days agoToday
Incidents in 90 days
2
Days with an incident
2
Median duration
18 min
This incident
1.6× the median
Other Hume AI incidents
All incidentsFollow Hume AI
Your coding agent knows when Hume AI is down, and tells you when a failure is theirs, not yours. You can also get Hume AI incidents in a feed reader or in Slack.
Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "hume" and tell me if Hume AI has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
RSS
https://outages.cc/feed.xml?providers=humeSlack
/feed subscribe https://outages.cc/feed.xml?providers=humeFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane