Hume API Outage History

16 incidents recorded over the last 365 days, 16 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 Hume API Incident

Hume API incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 12, 2026Documentation pages downIssue upstream appears to be fixed.29 minResolved
Sep 19, 2026TTS is downThe issue has been resolved.6 minResolved
Jul 24, 2026EVI IssueIssue was resolved.80h 25mResolved
Jul 14, 2026EVI and TTS outageIssue seems to be resolved. We mitigated the issue by increasing capacity and adjusting timeout/retry handling to improve reliability under load. Service health was confirmed once automated checks and live sessions were…-4406 minResolved
Jun 9, 2026APIs unavailableWe worked with the third-party provider to resolve the integration issue, restoring API availability.-1017 minResolved
Jun 8, 2026API unavailableIntegration issue has been fixed.28 minResolved
Feb 15, 2026High Error Rates on EVI and TTSIssue was resolved29 minResolved
Feb 11, 2026EVI timeouts and disconnectsEverything is operating normally again. Monitoring will continue throughout the day.24h 26mResolved
Feb 9, 2026EVI Multilingual Transcription downMultilingual transcription has been re-enabled. Service fully restored.17h 3mResolved
Feb 8, 2026Experiencing EVI timeoutsAn API key had expired and has been rotated. EVI appears functional again.1h 28mResolved
Jan 28, 2026EVI and TTS API IssuesIssue was resolved.7 minResolved
Nov 25, 2025Degraded performance for TTS-related products on the websiteIssue was resolved-131 minResolved
Nov 18, 2025Service outage for web applicationsIssue was resolved-131 minResolved
Nov 18, 2025Hume AI platform and APIs down due to Cloudflare OutageServices back up with cloudflare outage resolution.10 minResolved
Nov 8, 2025TTS service downInternal issue was fixed.-3 minResolved
Nov 6, 2025Timeout issue affecting EVI and OctaveIssue has been resolved.58 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 Hume API 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 Hume API 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 Hume API 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 Hume API outage in this window ran 3d 8h, against a mean recovery of 11h 28m. If you depend on Hume API 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.