- Level
- confirmed
- Worst impact
- Degraded
- Components
- Superhuman
- Down Index
- 24of 100
What to do
Check whether you use Superhuman Superhuman. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 2h 32m it lasted.
Anything that failed between 2026-02-12 15:33 UTC and 2026-02-12 18:05 UTC may need a replay.Subscribe to Superhuman's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=superhuman works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Superhuman 3
- investigating
We're seeing elevated error rates when indexing new content for AI features. Already indexed content is not affected. We've identified the source as coming from a third-party provider. We're monitoring the situation and looking for alternatives.
provider
- monitoring
Error rates have decreased, and our system and the third-party provider seem stable. We're continuing to monitor the situation.
provider
- resolved
All systems are back to normal. All pending queues have been processed and cleared.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-8ab8fc447b
Is Superhuman still down?
No, this incident was resolved 2026-02-12 18:05 UTC. For Superhuman's live state, see https://down.guide/superhuman.
How long did it last?
2h 32m, from 2026-02-12 15:33 UTC to 2026-02-12 18:05 UTC, by the times Superhuman posted.
What was affected?
Superhuman named Superhuman.
What caused it?
Superhuman hasn't published a root cause. If it does, it shows here.
Where does this come from?
Superhuman's official status page, https://status.superhuman.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.