Investigating - Outage across Dashboard, Search, Authenticated Docs, MCP and Assistant
**Documentation updates restored** We have worked through the documentation update backlog and re-run all updates that were dropped during the disruption. New deploys and content updates are processing normally. We are continuing to monitor recovery before resolving the incident.
The latest update from Mintlify.
State
Resolved
Started
Lasted
5 h 33 min
Worst impact
Major outage
Timeline
7 updatesInvestigating
47 min 14%
Identified
1 h 9 min 21%
Monitoring
3 h 38 min 65%
Updates
Times in UTCAs posted by Mintlify
**Documentation updates restored** We have worked through the documentation update backlog and re-run all updates that were dropped during the disruption. New deploys and content updates are processing normally. We are continuing to monitor recovery before resolving the incident.
Core platform services are operational, but documentation updates, deploys, and commit checks remain delayed due to processing queue backlogs. We are actively draining the backlogs and restoring normal processing capacity. New updates may continue to experience delays during recovery. We’ll provide another update as processing returns to normal.
Database availability has been restored and all replica members are healthy. We are progressively scaling impacted services back up. Dashboard, documentation updates, search, MCP, and Assistant are recovering but may experience intermittent errors or elevated latency. Some authenticated sites remain affected by a separate DNS issue. We’re monitoring stability and continuing restoration.
We've identified the underlying database issue and database availability has been restored. We are now scaling impacted services back up in a controlled sequence while monitoring stability. Dashboard, documentation updates and deploys, search, MCP, GitHub Actions, Assistant, and authenticated documentation sites remain intermittently unavailable. We’ll provide another update as recovery progresses.
The services that were previously restored are experiencing issues again. The following are currently unavailable: • Dashboard • Documentation updates - deploys and content updates are not going through • Doc search • MCP • Assistant • Authenticated documentation sites • GitHub Actions
The following services have been restored and are operating normally: • Dashboard • Doc search • Assistant • Authenticated documentation sites We're continuing to work on restoring the remaining affected services: • Documentation updates - deploys and content updates are not going through • MCP - unavailable
We're currently investigating an issue affecting the hot path for database requests. This is impacting the following services: • Authenticated documentation sites - unavailable • Dashboard - unavailable • Documentation updates - deploys and content updates are not going through • Doc search - unavailable • Assistant - unavailable • MCP - unavailable Unauthenticated (public) documentation sites remain fully available and are not affected by this incident
Mintlify in the last 90 days
Full historyIncidents in 90 days
14
Days with an incident
14
Median duration
37 min
This incident
9.0× the median
Other Mintlify incidents
All incidentsMintlify·Delayed deployments from GitHub
GitHub has resolved the webhook delivery issue, and deployments from GitHub are back to normal. Delayed pushes should now be deployed. If a recent change still isn't on your docs, trigger a manual update from the dashboard or push a new commit.
Mintlify·Elevated search latency on documentation sites
Search latency has returned to normal levels across documentation sites. We’re continuing to look into the cause and will keep monitoring to make sure performance stays stable.
Mintlify·Delayed Github webhook processing
Deployments triggered by GitHub pushes are back to normal, and all delayed updates have now been processed. We're sorry for the delay, and we're putting safeguards in place to stop this from happening again. If you are still experiencing any issues please contact [support@mintlify.com](mailto:support@mintlify.com "support@mintlify.com").
Mintlify·Search and other services impacted
Services were impacted and slowed from 10:42-10:49 PST, and we have fully recovered
Mintlify·Mintlify CLI installation failures
We’ve deployed a fix, and users should now be able to install and update the Mintlify CLI normally. We’re monitoring recovery. If you continue to run into issues please contact [support@mintlify.com](mailto:support@mintlify.com "support@mintlify.com").
Follow Mintlify
Your coding agent knows when Mintlify is down, and tells you when a failure is theirs, not yours. You can also get Mintlify incidents in a feed reader or in Slack.
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 "mintlify" and tell me if Mintlify 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.
https://outages.cc/feed.xml?providers=mintlify/feed subscribe https://outages.cc/feed.xml?providers=mintlifyFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane