Live

Mintlify

Mintlify is operational

Checked Operational

User reports

What people told outages.live in the last 24 hours, reviewed before it shows. Not from the Mintlify status page.

No reviewed reports in the last 24 hours.

History

90 days agoToday

outages.live tracks Mintlify since . The days before that show only what Mintlify published.

Incidents in 90 days

14

Days with an incident

14

Median duration

37 min

Longest incident

18 h 17 min

Components

4
Display Operational
90 days agoNo incidentsToday
Search Operational
90 days agoNo incidentsToday
Updates Operational
90 days agoNo incidentsToday
Dashboard Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

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

Go from tracking outages to fixing production issues with Polylane.

Try Polylane