- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 18of 100
What to do
Check whether your product depends on Mintlify. 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 1h 12m it lasted.
Anything that failed between 2026-07-01 21:10 UTC and 2026-07-01 22:22 UTC may need a replay.Subscribe to Mintlify's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=mintlify works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Mintlify 3
- investigating
We're investigating elevated latency and intermittent errors (including 500s) affecting docs pages and related services. The cause has been traced to a traffic spike on our primary database cluster, which is degrading performance across the platform. Our team is working to stabilize the cluster and restore normal service. We'll post another update shortly.
provider
- investigating
The earlier latency and errors affecting docs pages have been resolved, and all services are back to normal. Thanks for your patience.
provider
- resolved
After a period of monitoring, we have confirmed a full return to healthy services.
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-1bce6048d9
Is Mintlify still down?
No, this incident was resolved 2026-07-01 22:22 UTC. For Mintlify's live state, see https://down.guide/mintlify.
How long did it last?
1h 12m, from 2026-07-01 21:10 UTC to 2026-07-01 22:22 UTC, by the times Mintlify posted.
What caused it?
Mintlify hasn't published a root cause. If it does, it shows here.
Where does this come from?
Mintlify's official status page, https://status.mintlify.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.