Live

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").

The latest update from Mintlify.

State

Resolved

Started

Lasted

40 min

Worst impact

Notice

Timeline

2 updates
23:4223:5200:0200:1200:22
NoticeUpdate postedTimes in UTC

Identified

40 min 100%

Updates

Times in UTC

As posted by Mintlify

Resolved

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").

Identified

We identified an issue preventing some users from installing or updating the Mintlify CLI. A fix is being deployed. Existing documentation sites remain unaffected.

Mintlify in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

14

Days with an incident

14

Median duration

37 min

This incident

About the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

18 h 17 min
median 37 min
90 days agoToday

Other Mintlify incidents

All incidents

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.

Resolved

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.

Resolved

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").

Resolved

Mintlify·Search and other services impacted

Services were impacted and slowed from 10:42-10:49 PST, and we have fully recovered

Resolved

Mintlify·Images on Authed Sites are not rendering

Resolved, we restored the storage access policy affecting images on authenticated documentation sites. Images are loading normally, and the service has remained stable following the fix. If you continue to run into any issues please reach out to [support@mintlify.com](mailto:support@mintlify.com "support@mintlify.com").

Resolved

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.

Prompt
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.

RSS
https://outages.live/feed.xml?providers=mintlify
Slack
/feed subscribe https://outages.live/feed.xml?providers=mintlify

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane