Is Mintlify Down?

No — Mintlify is up

Mintlify's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 503 ms

Right now

The verdict is the worse of these two. How we decide

Mintlify's status page

status.mintlify.com · read 3 minutes ago · checked every 3 minutes

Operational

Mintlify's components, as its status page reports them
Component	Status
Display	Operational
Search	Operational
Updates	Operational
Dashboard	Operational

Open their status page

FlareWarden checks

mintlify.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 503 ms
Checked: 1 hour ago

By region

Ashburn reachable, 364 ms
Frankfurt reachable, 284 ms
Johannesburg reachable, 1191 ms
London reachable, 306 ms
Los Angeles reachable, 492 ms
Newark reachable, 247 ms
São Paulo reachable, 589 ms
Tokyo reachable, 551 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Ashburn	227 ms	1 ms	10 ms	342 ms
Frankfurt	40 ms	3 ms	8 ms	275 ms
Johannesburg	415 ms	1 ms	60 ms	1136 ms
London	62 ms	3 ms	9 ms	295 ms
Los Angeles	101 ms	1 ms	26 ms	470 ms
Newark	49 ms	8 ms	11 ms	214 ms
São Paulo	245 ms	1 ms	6 ms	582 ms
Tokyo	174 ms	2 ms	6 ms	539 ms

We check that mintlify.com loads, not every feature behind it. Test it yourself

History

Incidents Mintlify reported

Since Oct 22, 15 days · from status.mintlify.com

Incidents: 2
Major or critical: 1
Median to resolve: 37m

Unable to access preview deployments
major · Nov 4
lasted 27m
Delayed deployments from GitHub
minor · Oct 21
lasted 48m

Mintlify website availability

Measured by FlareWarden · mintlify.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 570ms

Last 30 days

65-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of mintlify.com from multiple regions every 6 hours. Mintlify's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 65 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

What Mintlify does

Mintlify hosts developer documentation. Teams write content in Markdown, keep it in a repository, and Mintlify builds and serves the public documentation site, including search, API playgrounds and a dashboard for editing and analytics. For software companies it is the public reference customers reach for during their own integration work and incidents.

What an outage looks like

The published documentation site fails to load or returns errors for readers while the team editing it sees nothing wrong. Mintlify reports Documentation separately from the Dashboard, so hosted docs can be unavailable while the editor works normally. Deploys of new content can also stall, leaving the live site on an older version with no visible error.

What to do about it

Read status.mintlify.com and check the Documentation row rather than the Dashboard, since the hosted sites your readers reach are reported separately from the editor your team uses. If Documentation is affected, tell support and sales, because customers hitting your docs during their own integration will see the failure before you do. Avoid repeated redeploys during an incident.

Is it down for everyone, or just you?

If this page says Mintlify is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Mintlify outage FAQ

My Mintlify dashboard works but customers say the docs are down. Is that possible?

Yes, and it is the split the status page is built around. Mintlify reports Documentation, the hosted sites readers reach, separately from the Dashboard your team edits in. A working editor is not evidence that the public site is serving. Check the Documentation row on status.mintlify.com rather than judging from your own view.

Does a Mintlify outage affect my main product?

Not directly, since documentation is hosted separately from your application. The cost is that customers cannot reach your reference material, which matters most when they are debugging an integration or working through their own incident. Support volume usually rises during a documentation outage because people ask questions they would otherwise answer themselves.

My documentation is showing an old version. Is that an outage?

It can be. Mintlify reports Updates as a component separate from Documentation, so the site can serve normally while new content fails to publish. The live site stays on the previous build with no error shown to readers. Check the Updates row before assuming a problem with your repository or your build configuration.

How long do Mintlify incidents usually last?

Mintlify publishes 90 days of per-component uptime on status.mintlify.com, which is a better guide than any general figure, and the Documentation and Dashboard rows differ. Read the current incident's own updates for the expected duration rather than an average, since a publish failure and a hosting failure are not comparable events.

How we measure this

We request Mintlify's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Mintlify publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of Mintlify itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Mintlify goes down

We check Mintlify every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required