Mintlify Outage History

Mintlify is up right now

Mintlify had 51 outages in the last 2 years totaling 1h 8m of downtime — averaging 2.1 incidents per month.

There were 51 Mintlify outages since February 3, 2026 totaling 1h 8m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.mintlify.com

Minor July 27, 2026

Delayed documentation updates due to GitHub API degradation

Detected by Pingoru
Jul 27, 2026, 07:37 AM UTC
Resolved
Jul 27, 2026, 07:37 AM UTC
Duration
—
Affected: Updates
Timeline · 3 updates
  1. identified Jul 27, 2026, 04:21 AM UTC

    Status: Identified We are investigating delays in documentation deployments triggered by GitHub pushes. Changes pushed to your docs repository may take longer than usual to appear, or may not deploy until this is resolved. Docs sites remain fully available, this only affects new updates. We are working to identify the cause and will post updates here. Affected components Updates (Partial outage)

  2. monitoring Jul 27, 2026, 04:30 AM UTC

    Status: Monitoring New documentation updates are processing normally again. We are continuing to monitor. If a push made during the incident window hasn't appeared, you can immediately rectify by re-triggering the deployment from the dashboard or push a new commit. Affected components Updates (Partial outage)

  3. resolved Jul 27, 2026, 07:37 AM UTC

    Status: Resolved Root cause was identified to be the github outage: https://www.githubstatus.com/incidents/fmmsrcg5x638 Documentation updates are prorcessing normally between the times of 03:53 UTC and 04:09 UTC updates to GitHub failed to process to fix this manually run a manual update in the dashboard Affected components Updates (Operational)

Read the full incident report →

Minor July 21, 2026

Search requests failing for some customers

Detected by Pingoru
Jul 21, 2026, 10:49 PM UTC
Resolved
Jul 21, 2026, 10:49 PM UTC
Duration
—
Timeline · 3 updates
  1. investigating Jul 21, 2026, 10:32 PM UTC

    Status: Investigating We’re investigating an issue causing search requests to fail for some customers following a recent deployment. We’ve identified the change and are working to restore service. We’ll share another update shortly.

  2. identified Jul 21, 2026, 10:33 PM UTC

    Status: Identified We’ve identified the issue and merged a fix. We’re deploying it now and will confirm once search is fully restored.

  3. resolved Jul 21, 2026, 10:49 PM UTC

    Status: Resolved The fix has been deployed, and search functionality has been restored

Read the full incident report →

Minor July 21, 2026

Updates and preview deployments being delayed

Detected by Pingoru
Jul 21, 2026, 06:44 PM UTC
Resolved
Jul 21, 2026, 06:44 PM UTC
Duration
—
Affected: Updates
Timeline · 2 updates
  1. investigating Jul 21, 2026, 05:14 PM UTC

    Status: Investigating We're investigating delays or stalls in documentation updates Affected components Updates (Degraded performance)

  2. resolved Jul 21, 2026, 06:44 PM UTC

    Status: Resolved Impact: Customers were not able to update their docs Root Cause: Updates failed due to a hitting a rate limit on Github Time Range: 4:40 AM - 8:00 AM PST Affected components Updates (Operational)

Read the full incident report →

Minor July 20, 2026

GitHub API degradation causing update failures

Detected by Pingoru
Jul 20, 2026, 01:57 AM UTC
Resolved
Jul 20, 2026, 01:57 AM UTC
Duration
—
Affected: DashboardUpdates
Timeline · 4 updates
  1. identified Jul 20, 2026, 12:46 AM UTC

    Status: Identified We are seeing some documentation updates fail due to ongoing issues with GitHub’s API. We are monitoring GitHub’s recovery and will provide further updates as service is restored. Affected components Updates (Degraded performance) Dashboard (Degraded performance)

  2. identified Jul 20, 2026, 01:09 AM UTC

    Status: Identified GitHub continues to report degraded availability across its services. As a result, some Mintlify documentation updates are still failing. Published documentation remains available. We are monitoring GitHub’s status "GitHub’s status": https://www.githubstatus.com/ and will continue to provide updates every 15 minutes. Affected components Updates (Degraded performance) Dashboard (Degraded performance)

  3. monitoring Jul 20, 2026, 01:32 AM UTC

    Status: Monitoring We are seeing recovery in documentation updates, and our monitoring checks have returned to normal. GitHub’s incident remains ongoing, so we are continuing to monitor for intermittent failures and will provide another update in 15 minutes. Affected components Updates (Degraded performance) Dashboard (Degraded performance)

  4. resolved Jul 20, 2026, 01:57 AM UTC

    Status: Resolved GitHub API errors have subsided, and documentation updates are back to operating normally. If you continue to experience issues, please contact [email protected] "[email protected]": mailto:[email protected]. Affected components Updates (Operational) Dashboard (Operational)

Read the full incident report →

Minor July 16, 2026

We are seeing upstream GitHub API degradation

Detected by Pingoru
Jul 16, 2026, 11:56 PM UTC
Resolved
Jul 16, 2026, 11:56 PM UTC
Duration
—
Affected: DisplayDashboardUpdatesSearch
Timeline · 6 updates
  1. investigating Jul 16, 2026, 10:35 PM UTC

    Status: Investigating GitHub-connected projects may be unable to load the editor or perform repository actions, and deployments may fail or be delayed. Published documentation remains accessible. We’ll share updates as recovery progresses. Affected components Display (Degraded performance) Updates (Degraded performance) Dashboard (Degraded performance) Search (Degraded performance)

  2. investigating Jul 16, 2026, 10:52 PM UTC

    Status: Investigating We continue to see upstream errors from GitHub affecting the editor, repository actions, and deployments. We have escalated the issue with GitHub and will share updates as recovery progresses. Affected components Display (Degraded performance) Updates (Degraded performance) Dashboard (Degraded performance) Search (Degraded performance)

  3. identified Jul 16, 2026, 11:39 PM UTC

    Status: Identified GitHub has confirmed degraded REST API availability, with approximately 35% of requests failing. This continues to affect GitHub-connected editor sessions, repository actions, and deployments. Published documentation remains accessible. We are monitoring GitHub’s investigation and will provide updates as service recovers. Affected components Display (Degraded performance) Updates (Degraded performance) Dashboard (Degraded performance) Search (Degraded performance)

  4. identified Jul 16, 2026, 11:41 PM UTC

    Status: Identified Published documentation and search continue to function normally. GitHub’s ongoing REST API degradation remains limited to GitHub-connected editor sessions, repository actions, and deployments. We are monitoring GitHub’s investigation. Affected components Dashboard (Degraded performance) Search (Operational) Display (Operational) Updates (Degraded performance)

  5. monitoring Jul 16, 2026, 11:48 PM UTC

    Status: Monitoring We are seeing recovery, and GitHub-connected editor sessions, repository actions, and deployments are working again. We will continue monitoring for stability. Affected components Updates (Operational) Dashboard (Operational) Search (Operational) Display (Operational)

  6. resolved Jul 16, 2026, 11:56 PM UTC

    Status: Resolved This incident is resolved. GitHub-connected editor sessions, repository actions, and deployments are operating normally. If you continue to experience issues, please contact [email protected] "[email protected]": mailto:[email protected]. Affected components Display (Operational) Updates (Operational) Dashboard (Operational) Search (Operational)

Read the full incident report →

Minor July 13, 2026

Editor publishing changes to repositories without branch protections

Detected by Pingoru
Jul 13, 2026, 08:00 PM UTC
Resolved
Jul 13, 2026, 08:00 PM UTC
Duration
—
Affected: DisplayDashboardUpdatesSearch
Timeline · 1 update
  1. resolved Jul 13, 2026, 08:00 PM UTC

    Status: Resolved The web editor was unintentionally auto making commits directly to the main branch on user typing edits. This impacted any customer who did not have GitHub branch protections enabled between approximately 07/13/2026 13:00 PST and 07/14/2026 15:44 PT when we deployed a fix Affected components Display (Operational) Updates (Operational) Dashboard (Operational) Search (Operational)

Read the full incident report →

Minor July 10, 2026

Increase in search failures

Detected by Pingoru
Jul 10, 2026, 05:32 PM UTC
Resolved
Jul 10, 2026, 05:32 PM UTC
Duration
—
Affected: Search
Timeline · 2 updates
  1. investigating Jul 10, 2026, 04:51 PM UTC

    Status: Investigating We have detected an uptick in search failures across a subset of customers. We are investigating root cause. Affected components Search (Degraded performance)

  2. resolved Jul 10, 2026, 05:32 PM UTC

    Status: Resolved This incident is only affecting a handful of customers and is not widespread, we are following up with affected customers directly. Affected components Search (Operational)

Read the full incident report →

Minor July 2, 2026

Docs Assistant Not Functioning

Detected by Pingoru
Jul 02, 2026, 10:09 PM UTC
Resolved
Jul 02, 2026, 10:09 PM UTC
Duration
—
Timeline · 2 updates
  1. investigating Jul 02, 2026, 09:56 PM UTC

    Status: Investigating We have discovered an issue with our model provider that is causing our docs assistant to not function properly. We are actively investigating a root cause.

  2. resolved Jul 02, 2026, 10:09 PM UTC

    Status: Resolved We've restored functionality to our docs assistant by reverting to a stable model. The assistant is now operating normally. We will share a timeline once we have more details.

Read the full incident report →

Minor July 1, 2026

Degraded Performance Across Mintlify Services

Detected by Pingoru
Jul 01, 2026, 10:22 PM UTC
Resolved
Jul 01, 2026, 10:22 PM UTC
Duration
—
Affected: DisplayDashboardUpdatesSearch
Timeline · 3 updates
  1. investigating Jul 01, 2026, 09:10 PM UTC

    Status: Investigating We're investigating elevated latency and intermittent errors (including 500s) affecting docs pages and related services. The cause has been traced to a traffic spike on our primary database cluster, which is degrading performance across the platform. Our team is working to stabilize the cluster and restore normal service. We'll post another update shortly. Affected components Display (Degraded performance) Updates (Degraded performance) Dashboard (Degraded performance) Search (Degraded performance)

  2. investigating Jul 01, 2026, 10:05 PM UTC

    Status: Investigating The earlier latency and errors affecting docs pages have been resolved, and all services are back to normal. Thanks for your patience. Affected components Updates (Operational) Dashboard (Operational) Search (Operational) Display (Operational)

  3. resolved Jul 01, 2026, 10:22 PM UTC

    Status: Resolved After a period of monitoring, we have confirmed a full return to healthy services. Affected components Display (Operational) Updates (Operational) Dashboard (Operational) Search (Operational)

Read the full incident report →

Minor June 25, 2026

Upstream Degradation of Github Webhooks

Detected by Pingoru
Jun 25, 2026, 06:16 PM UTC
Resolved
Jun 25, 2026, 06:16 PM UTC
Duration
—
Affected: Updates
Timeline · 2 updates
  1. monitoring Jun 25, 2026, 06:01 PM UTC

    Status: Monitoring Updates may not be processed normally because of an upstream issue with Github webhooks. Affected components Updates (Degraded performance)

  2. resolved Jun 25, 2026, 06:16 PM UTC

    Status: Resolved Github has fixed the degradation. Updates should be restored to normal functionality. Affected components Updates (Operational)

Read the full incident report →

Minor June 25, 2026

Degraded Assistant Performance

Detected by Pingoru
Jun 25, 2026, 03:14 AM UTC
Resolved
Jun 25, 2026, 03:14 AM UTC
Duration
—
Timeline · 3 updates
  1. investigating Jun 25, 2026, 02:07 AM UTC

    Status: Investigating Request verification on the Mintlify assistant is intermittently failing for some customers. We are actively investigating a root cause.

  2. identified Jun 25, 2026, 02:09 AM UTC

    Status: Identified We have identified a root cause and are deploying a fix.

  3. resolved Jun 25, 2026, 03:14 AM UTC

    Status: Resolved All assistant issues are resolved.

Read the full incident report →

Minor June 23, 2026

Updates stuck in queued state

Detected by Pingoru
Jun 23, 2026, 07:54 PM UTC
Resolved
Jun 23, 2026, 07:54 PM UTC
Duration
—
Affected: Updates
Timeline · 3 updates
  1. investigating Jun 23, 2026, 07:40 PM UTC

    Status: Investigating We are currently experiencing issues with updates and are investigating the issue Affected components Updates (Full outage)

  2. identified Jun 23, 2026, 07:52 PM UTC

    Status: Identified We have applied a fix and are investigating a root cause Affected components Updates (Operational)

  3. resolved Jun 23, 2026, 07:54 PM UTC

    Status: Resolved Updates are stable and we are investigating a root cause Affected components Updates (Operational)

Read the full incident report →

Major June 18, 2026

Re-deployments of updated sites are failing intermittently

Detected by Pingoru
Jun 18, 2026, 08:24 PM UTC
Resolved
Jun 18, 2026, 09:33 PM UTC
Duration
1h 8m
Affected: Updates
Timeline · 1 update
  1. investigating Jun 18, 2026, 08:24 PM UTC

    Status: Investigating We're investigating reports of deployments failing with an error for a subset of customers. Your published documentation remains live and unaffected. We'll share an update shortly. Affected components Updates (Degraded performance)

Read the full incident report →

Minor June 16, 2026

GitHub pushes not triggering updates

Detected by Pingoru
Jun 16, 2026, 09:15 PM UTC
Resolved
Jun 16, 2026, 09:15 PM UTC
Duration
—
Affected: Updates
Timeline · 3 updates
  1. investigating Jun 16, 2026, 08:18 PM UTC

    Status: Investigating We have received reports of some pushes to GitHub not triggering updates on Mintlify. Our team is actively investigating and will follow up with updates as we have them. Affected components Updates (Degraded performance)

  2. identified Jun 16, 2026, 08:36 PM UTC

    Status: Identified We've identified a potential source for the issue and are working on reverting the change to restore functionality. Affected components Updates (Degraded performance)

  3. resolved Jun 16, 2026, 09:15 PM UTC

    Status: Resolved The offending change has been rolled back and service restored. Our team will be queuing a manual update for any missed deploys, but for a quicker resolution, users can trigger a manual deploy "trigger a manual deploy": https://www.mintlify.com/docs/deploy/deployments#manually-trigger-a-deployment from the Mintlify dashboard. Affected components Updates (Operational)

Read the full incident report →

Minor June 14, 2026

Search results not clickable

Detected by Pingoru
Jun 14, 2026, 11:40 PM UTC
Resolved
Jun 14, 2026, 11:40 PM UTC
Duration
—
Affected: Search
Timeline · 3 updates
  1. investigating Jun 14, 2026, 10:04 PM UTC

    Status: Investigating We're aware of an issue where search results on documentation sites are displaying correctly but cannot be selected to navigate to the corresponding page. Search functionality is otherwise unaffected. Our team is actively working on a fix and we'll provide an update as soon as it's available. Affected components Search (Partial outage)

  2. identified Jun 14, 2026, 10:22 PM UTC

    Status: Identified We've identified and resolved the issue affecting search result navigation. A fix is currently being rolled out, and search results will be fully clickable again shortly. Affected components Search (Partial outage)

  3. resolved Jun 14, 2026, 11:40 PM UTC

    Status: Resolved We've confirmed search is stable and have re-deployed any failed deployment(s) in this period for affected customers. No action is required by any customers. We thank our customers for our patience, and we're taking action to ensure that outages of this nature occur less frequently. Affected components Search (Operational)

Read the full incident report →

Minor June 10, 2026

Search Issues

Detected by Pingoru
Jun 10, 2026, 09:33 PM UTC
Resolved
Jun 10, 2026, 09:33 PM UTC
Duration
—
Affected: Display
Timeline · 3 updates
  1. identified Jun 10, 2026, 08:37 PM UTC

    Status: Identified We're experiencing issues with search not returning results. We believe we've identified the issue and are working to remediate it. Affected components Display (Degraded performance)

  2. monitoring Jun 10, 2026, 08:46 PM UTC

    Status: Monitoring We've rectified the issue and are continuing to monitor the situation. Affected components Display (Operational)

  3. resolved Jun 10, 2026, 09:33 PM UTC

    Status: Resolved We've confirmed search is stable and have re-ran any failed search ingestion(s) in this period for affected customers. No action is required by any customers. We thank our customers for our patience, and we're taking action to ensure that outages of this nature occur less frequently. Affected components Display (Operational)

Read the full incident report →

Minor June 1, 2026

Page Revalidation Issues

Detected by Pingoru
Jun 01, 2026, 10:24 PM UTC
Resolved
Jun 01, 2026, 10:24 PM UTC
Duration
—
Affected: Updates
Timeline · 4 updates
  1. investigating Jun 01, 2026, 08:44 PM UTC

    Status: Investigating We're seeing some issues with page cache revalidation that is affecting updates from being published to documentation sites. We've begun an investigation and will have updates shortly. Affected components Updates (Degraded performance)

  2. identified Jun 01, 2026, 09:28 PM UTC

    Status: Identified We've identified the issue as being caused by rate limiting due to a migration we were attempting to run, and have taken steps to prevent it from occurring again. Additionally, we are retriggering revalidation for all customers affected by the issue. Affected components Updates (Degraded performance)

  3. monitoring Jun 01, 2026, 09:48 PM UTC

    Status: Monitoring All customers who had a failing update or revalidation should be revalidated. We are closely monitoring our systems while we re-examinee our approach to the scheduled migration to prevent this from happening again. Affected components Updates (Degraded performance)

  4. resolved Jun 01, 2026, 10:24 PM UTC

    Status: Resolved Updates are back to normal, and we are load testing the planned migration more comprehensively before attempting it again. Affected components Updates (Operational)

Read the full incident report →

Minor May 29, 2026

Documentation update failures for some AsyncAPI-backed sites

Detected by Pingoru
May 29, 2026, 07:22 PM UTC
Resolved
May 29, 2026, 07:22 PM UTC
Duration
—
Affected: Updates
Timeline · 3 updates
  1. identified May 29, 2026, 06:13 PM UTC

    Status: Identified We are investigating an issue causing documentation updates to fail for some sites that use AsyncAPI specifications. Affected components Updates (Degraded performance)

  2. identified May 29, 2026, 06:22 PM UTC

    Status: Identified We have identified the issue as a transitive dependency bump that led to parsing failures for valid AsyncAPI specifications. We have rolled back this dependency and are in the process of rolling it out. Affected components Updates (Degraded performance)

  3. resolved May 29, 2026, 07:22 PM UTC

    Status: Resolved A fix has been deployed and this issue is now resolved. Please reach out to [email protected] "[email protected]": mailto:[email protected] if you run into any further issues. Affected components Updates (Operational)

Read the full incident report →

Minor May 28, 2026

[Security Incident] Composio Connected Accounts

Detected by Pingoru
May 28, 2026, 10:24 PM UTC
Resolved
May 28, 2026, 10:24 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating May 23, 2026, 06:32 PM UTC

    Status: Investigating We were notified of a security incident involving our integrations provider, Composio, in which user credentials may have been accessed for third-party integrations in our Slack Agent and Workflows product. As a precaution, we are proactively rotating all affected customer credentials and will reach out directly to every impacted customer shortly. Note: GitHub and GitLab integrations were never exposed to Composio. These are handled in-house and remain secure.

  2. identified May 23, 2026, 08:41 PM UTC

    Status: Identified We have disabled the affected features, revoked all credentials associated with this vendor, and attemped to revoke all customer credentials associated with this vendor. Additionally, we have reached out via email to the subset of customers potentially affected by this incident. We are continuing to monitor the vendor's security published security bulletin for updates: https://composio.dev/blog/composio-may-2026-security-incident We are continuing to review internally to ensure the integrity of our systems, but no indicators of compromise have been discovered and we currently have no reason to believe any compromise has taken place.

  3. monitoring May 24, 2026, 02:20 AM UTC

    Status: Monitoring We have disabled the affected features, revoked all credentials associated with this vendor, and attempted to revoke all customer credentials associated with this vendor. Additionally, we have reached out via email to the entire subset of customers potentially affected by this incident. We are continuing to monitor the vendor's security published security bulletin for updates: https://composio.dev/blog/composio-may-2026-security-incident We have completed an in-depth review of corporate devices, production and development systems, and have found no indicators of compromise. Automated alerts have been configured, and we are continuing to monitor the situation.

  4. resolved May 28, 2026, 10:24 PM UTC

    Status: Resolved We are continuing to monitor the situation. https://composio.dev/blog/composio-may-2026-security-incident All customers affected by this incident have been notified, and an internal review has taken place to ensure no compromise of Mintlify systems. While we have terminated our existing integrations with Composio, we have been in contact with the Composio team and are actively exploring alternatives and improvements to securely reintroduce this functionality to parts of the Mintlify platform.

Read the full incident report →

Minor May 20, 2026

Search, Dashboard, and Updates Unavailable

Detected by Pingoru
May 20, 2026, 10:05 AM UTC
Resolved
May 20, 2026, 10:05 AM UTC
Duration
—
Affected: DisplayDashboardUpdates
Timeline · 4 updates
  1. investigating May 20, 2026, 07:46 AM UTC

    Status: Investigating Search is currently unavailable across our documentation site, our dashboard is inaccessible, and content updates are not propagating to the live site. Existing documentation pages remain fully accessible and can be viewed as normal. We're actively investigating the root cause and will share updates as we learn more. Affected components Display (Degraded performance) Updates (Full outage) Dashboard (Full outage)

  2. resolved May 20, 2026, 08:53 AM UTC

    Status: Resolved We've identified the root cause of the disruption, which traced back to a database failure on our side. Service has been restored, including search, the dashboard, the editor, and content updates. Existing documentation pages remained available throughout. We're monitoring closely to confirm full stability and will follow up with a post-mortem. Affected components Display (Operational) Updates (Operational) Dashboard (Operational)

  3. identified May 20, 2026, 09:03 AM UTC

    Status: Identified Search is currently unavailable across our documentation site, our dashboard is inaccessible, and content updates are not propagating to the live site. Existing documentation pages remain fully accessible and can be viewed as normal. We're actively investigating the root cause and will share updates as we learn more. Affected components Display (Partial outage) Updates (Full outage) Dashboard (Full outage)

  4. resolved May 20, 2026, 10:05 AM UTC

    Status: Resolved We've identified the root cause of the disruption, which traced back to a database failure on our side. Service has been restored, including search, the dashboard, the editor, and content updates. Existing documentation pages remained available throughout. We're monitoring closely to confirm full stability and will follow up with a post-mortem. Affected components Display (Operational) Updates (Operational) Dashboard (Operational)

Read the full incident report →

Minor May 13, 2026

Intermittent reports of updates not being triggered

Detected by Pingoru
May 13, 2026, 11:11 PM UTC
Resolved
May 13, 2026, 11:11 PM UTC
Duration
—
Affected: Updates
Timeline · 4 updates
  1. investigating May 13, 2026, 09:19 PM UTC

    Status: Investigating We are investigating reports of a small subset of GitHub pushes not resulting in deployments being created. Our team is investigating and will follow up with updates as we have them. Affected components Updates (Degraded performance)

  2. investigating May 13, 2026, 10:00 PM UTC

    Status: Investigating We have identified a potential bottleneck in webhook processing that may be causing this issue and are preparing a fix. Affected components Updates (Degraded performance)

  3. monitoring May 13, 2026, 10:39 PM UTC

    Status: Monitoring We have deployed a mitigation and are monitoring to ensure no recurrence. Affected components Updates (Degraded performance)

  4. resolved May 13, 2026, 11:11 PM UTC

    Status: Resolved We have seen recovery in our systems that process webhooks. Please reach out to [email protected] "[email protected]": mailto:[email protected] if you continue to experience issues with updates. Affected components Updates (Operational)

Read the full incident report →

Minor May 11, 2026

Slack app unable to create pull requests

Detected by Pingoru
May 11, 2026, 05:15 PM UTC
Resolved
May 11, 2026, 05:15 PM UTC
Duration
—
Affected: Dashboard
Timeline · 2 updates
  1. investigating May 11, 2026, 03:39 PM UTC

    Status: Investigating The Mintlify Slack app is currently unable to create pull requests. Other AI features and the dashboard are unaffected. We've identified the root cause and are deploying a fix. Affected components Dashboard (Degraded performance)

  2. resolved May 11, 2026, 05:15 PM UTC

    Status: Resolved We have rolled back the bad commit and have verified that the agent is operating normally. Affected components Dashboard (Operational)

Read the full incident report →

Minor May 5, 2026

Some docs sites are experiencing partial outages

Detected by Pingoru
May 05, 2026, 09:01 PM UTC
Resolved
May 05, 2026, 09:01 PM UTC
Duration
—
Timeline · 3 updates
  1. investigating May 05, 2026, 08:37 PM UTC

    Status: Investigating Several Mintlify customers have reported issues loading their sites, with some experiencing missing CSS/JS, and others unable to load pages at all, seeing 500 errors. Investigation is ongoing.

  2. monitoring May 05, 2026, 08:45 PM UTC

    Status: Monitoring After scaling up internal services and purging caches for affected sites, we are seeing affected sites back online and fully functioning. No customer action is required at this time. We're carefully monitoring for any additional issues while we work to find the root cause.

  3. resolved May 05, 2026, 09:01 PM UTC

    Status: Resolved All docs sites are online and fully-functioning. We are still investigating the root cause of this issue and will publish a more detailed report as soon as we know more details.

Read the full incident report →

Minor April 21, 2026

Upstream security event - Vercel

Detected by Pingoru
Apr 21, 2026, 09:05 PM UTC
Resolved
Apr 21, 2026, 09:05 PM UTC
Duration
—
Timeline · 3 updates
  1. monitoring Apr 19, 2026, 06:26 PM UTC

    Status: Monitoring Our team is aware of a security incident: https://vercel.com/kb/bulletin/vercel-april-2026-security-incident reported by one of our infrastructure providers, Vercel. We are working to determine the impact of this event to Mintlify and proactively performing a rotation of all secrets and credentials. At this point, through both internal investigation and communications from Vercel, we currently have no evidence that Mintlify or Mintlify customers were affected by this event. We will continue to investigate and post updates as new information becomes available.

  2. monitoring Apr 19, 2026, 07:21 PM UTC

    Status: Monitoring We have reviewed our audit logs for Vercel and other critical systems, and have not identified any suspicious behavior from any sources. We are continuing a complete credential rotation on any potentially affected systems. Additionally, as new evidence has come to light, including indications of compromise, we are reviewing third party integrations used in our organization for any evidence, of compromise, and have found nothing thus far. There continues to be no evidence that Mintlify or any Mintlify customers were affected by this event, and we are following the official bulletin and other threat feeds for updates as they appear. https://vercel.com/kb/bulletin/vercel-april-2026-security-incident

  3. resolved Apr 21, 2026, 09:05 PM UTC

    Status: Resolved The Mintlify team has confirmed that no suspicious or unexpected actions were taken against any Mintlify services or infrastructure that would indicate Mintlify was affected by Vercel's ongoing incident, and have taken steps to ensure no compromise could have occurred directly on Mintlify's own infrastructure. Additionally, as stated by Vercel and their security partners, no supply chain attack has been detected: https://vercel.com/kb/bulletin/vercel-april-2026-security-incident As such, the Mintlify team is closing this status page as resolved, but will continue to monitor the ongoing situation, and are available via our normal support channels to answer any questions.

Read the full incident report →