Docs search unavailable
Mintlify reported that search on its documentation site did not work. The issue later included some documentation pages that did not load and navigation items that were not clickable. Mintlify deployed a fix, and the incident is resolved. It lasted 17 minutes.
State
Resolved
Started
Lasted
17 min
Worst impact
Major outage
Timeline
3 updatesIdentified
17 min 100%
Updates
Times in UTCAs posted by Mintlify
The fix has been deployed and the documentation sites are fully restored. All pages are loading, and search and navigation are working normally again. Thanks for your patience.
The issue is broader than first reported. Beyond search, some documentation pages aren’t loading, and on other pages many navigation items aren’t clickable. Our team has a fix ready and is deploying it now. We’ll post another update once the docs site is fully restored.
We’ve identified the cause of an issue affecting search on our documentation site. Docs search is currently unavailable. All documentation pages remain accessible and can be browsed through the navigation.
Mintlify in the last 90 days
Full historyIncidents in 90 days
16
Days with an incident
16
Median duration
32 min
This incident
45% shorter than the median
Other Mintlify incidents
All incidentsMintlify·Unable to access preview deployments
Mintlify could not log in some users to preview deployments and to sites protected by Mintlify authentication. Production documentation sites and preview builds were not affected. Mintlify identified the cause, deployed a fix, and confirmed normal logins. Mintlify resolved the incident after 28 minutes.
Mintlify·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
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.live/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.live/feed.xml?providers=mintlify/feed subscribe https://outages.live/feed.xml?providers=mintlifyFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane