Live

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 updates
19:0420:2721:5123:1400:37
Major outageUpdate postedTimes in UTC

Investigating

47 min 14%

Identified

1 h 9 min 21%

Monitoring

3 h 38 min 65%

Updates

Times in UTC

As posted by Mintlify

Resolved

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

Monitoring

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.

Monitoring

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.

Identified

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.

Investigating

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

Investigating

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

Investigating

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 history
90 days agoToday

Incidents in 90 days

14

Days with an incident

14

Median duration

37 min

This incident

9.0× 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

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

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

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane