- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 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 0m it lasted.
Anything that failed between 2026-07-14 23:49 UTC and 2026-07-13 20:00 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 1
- resolved
The web editor was unintentionally auto making commits directly to the main branch on user typing edits. This impacted any customer who did not have GitHub branch protections enabled between approximately 07/13/2026 13:00 PST and 07/14/2026 15:44 PT when we deployed a fix
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-ef21c4bc25
Is Mintlify still down?
No, this incident was resolved 2026-07-13 20:00 UTC. For Mintlify's live state, see https://down.guide/mintlify.
How long did it last?
0m, from 2026-07-14 23:49 UTC to 2026-07-13 20:00 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.