Some Mintlify Agent and Autopilot runs failing to start
Some Mintlify Agent and Autopilot runs fail to start. Mintlify reports that this issue affects runs started from the dashboard, Slack, or scheduled workflows. Mintlify is monitoring the recovery of an infrastructure provider.
State
Monitoring
Started
Ongoing for
14 min
Worst impact
Notice
Timeline
1 updateMonitoring
14 min 100%
Updates
Times in UTCAs posted by Mintlify
Since 6:05 PM PT (02:05 UTC), some Autopilot and agent runs are failing to start. An infrastructure provider we depend on is having an incident, and the environments our agents run in can't be created. Runs started from the dashboard, Slack or scheduled workflows may fail before they begin. We're monitoring the provider's recovery.
Mintlify in the last 90 days
Full historyIncidents in 90 days
17
Days with an incident
16
Median duration
37 min
This incident
63% shorter than the median
Other Mintlify incidents
All incidentsMintlify·Inflated agent views in docs analytics
Mintlify reported inflated agent views in the Analytics dashboard for documentation sites served from a subpath. Mintlify resolved the issue and removed the miscounted views. The outage lasted about 3 hours and 34 minutes.
Mintlify·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.
Mintlify·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.
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