Delayed documentation updates from GitHub
The backlog of documentation updates from GitHub has been fully processed, and updates are publishing within the usual timeframe.
The latest update from Mintlify.
State
Resolved
Started
Lasted
4 h 42 min
Worst impact
Partial outage
Timeline
3 updatesInvestigating
2 h 32 min 54%
Monitoring
2 h 9 min 46%
Updates
Times in UTCAs posted by Mintlify
The backlog of documentation updates from GitHub has been fully processed, and updates are publishing within the usual timeframe.
New documentation updates from GitHub are now processing normally, and changes pushed from this point on should go live within the usual timeframe. We are continuing to work through a backlog of earlier updates, so changes pushed during the incident window may still take some time to appear. Triggering a manual update from your dashboard will publish them immediately.
Some customers are experiencing delays between pushing changes to GitHub and those changes appearing on their documentation site. Updates are being processed and no data is lost, but they may take significantly longer than usual to go live. If you have a pressing change, you can trigger a manual update from your dashboard to publish it immediately.
Mintlify in the last 90 days
Full historyIncidents in 90 days
14
Days with an incident
14
Median duration
37 min
This incident
7.6× 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