Mintlify Outage History

Mintlify is up right now

Mintlify had 37 outages in the last 2 years — averaging 1.5 incidents per month.

There were 37 Mintlify outages since February 3, 2026. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.mintlify.com

Minor March 5, 2026

Unresponsive Slack Bots

Detected by Pingoru
Mar 05, 2026, 09:12 PM UTC
Resolved
Mar 05, 2026, 09:12 PM UTC
Duration
—
Affected: Dashboard
Timeline · 2 updates
  1. investigating Mar 05, 2026, 06:27 PM UTC

    Status: Investigating Mintlify's Slack agent and assistant are intermittently not responding due to a wider Slack outage. They remain working via DMs just not in channels. Affected components Dashboard (Degraded performance)

  2. resolved Mar 05, 2026, 09:12 PM UTC

    Status: Resolved Slack outage has been resolved. We've returned to fully functionality Affected components Dashboard (Operational)

Read the full incident report →

Minor March 5, 2026

Search Degradation

Detected by Pingoru
Mar 05, 2026, 05:23 PM UTC
Resolved
Mar 05, 2026, 05:23 PM UTC
Duration
—
Affected: Display
Timeline · 5 updates
  1. investigating Mar 05, 2026, 02:17 PM UTC

    Status: Investigating Some users may experience a degraded search experience on recently-updated documentation sites. Our team is aware and working on a fix. Affected components Display (Degraded performance)

  2. identified Mar 05, 2026, 03:02 PM UTC

    Status: Identified Our team has identified the issue and we are deploying some changes to fix it. Affected components Display (Degraded performance)

  3. identified Mar 05, 2026, 03:32 PM UTC

    Status: Identified Our team has deployed a fix, and is working to backfill results for the customers affected by the outage. Affected components Display (Degraded performance)

  4. monitoring Mar 05, 2026, 04:41 PM UTC

    Status: Monitoring Search latency and performance is back to normal levels with a few exceptions which our team is investigating. Most customers should be unaffected. Affected components Display (Degraded performance)

  5. resolved Mar 05, 2026, 05:23 PM UTC

    Status: Resolved Search latency should be in line with normal performance for all customers. We are continuing to investigate and prevent any further issues. Affected components Display (Operational)

Read the full incident report →

Minor March 4, 2026

Deployment Update Delays

Detected by Pingoru
Mar 04, 2026, 12:34 AM UTC
Resolved
Mar 04, 2026, 12:34 AM UTC
Duration
—
Affected: Updates
Timeline · 2 updates
  1. investigating Mar 03, 2026, 11:47 PM UTC

    Status: Investigating We've experience a large spike in traffic to update documentation sites and are seeing deployment updates taking longer than usual. We’re actively increasing workflow capacity and clearing the backlog to restore normal processing times. Affected components Updates (Degraded performance)

  2. resolved Mar 04, 2026, 12:34 AM UTC

    Status: Resolved The temporary spike in queued redeployments has been cleared, and updates have returned to processing normally again. We will continue monitoring to redeployments. Affected components Updates (Operational)

Read the full incident report →

Minor March 3, 2026

Github outage

Detected by Pingoru
Mar 03, 2026, 08:14 PM UTC
Resolved
Mar 03, 2026, 08:14 PM UTC
Duration
—
Affected: Updates
Timeline · 2 updates
  1. investigating Mar 03, 2026, 07:17 PM UTC

    Status: Investigating GitHub has declared an outage affecting APIs and Actions: https://www.githubstatus.com/incidents/n07yy1bk6kc4 Updates requiring GitHub may be degraded Affected components Updates (Degraded performance)

  2. resolved Mar 03, 2026, 08:14 PM UTC

    Status: Resolved GitHub has implemented a fix and we are seeing full recovery. Affected components Updates (Operational)

Read the full incident report →

Minor March 3, 2026

Investigating Deployment Delays

Detected by Pingoru
Mar 03, 2026, 01:31 PM UTC
Resolved
Mar 03, 2026, 01:31 PM UTC
Duration
—
Affected: Updates
Timeline · 2 updates
  1. investigating Mar 03, 2026, 12:47 PM UTC

    Status: Investigating We’re currently experiencing delays in documentation updates and site redeployments. Some changes may take longer than usual to go live. This is due to a backlog in our deployment workflow queue caused by a spike in redeployments. We’re actively increasing workflow capacity and clearing the backlog to restore normal processing times. Affected components Updates (Degraded performance)

  2. resolved Mar 03, 2026, 01:31 PM UTC

    Status: Resolved The deployment backlog has been cleared and documentation updates are processing normally again. The delays were caused by a temporary spike in redeployments, which has now been resolved. We’ll continue monitoring to ensure stability. If you’re still experiencing delays, please reach out to support. Affected components Updates (Operational)

Read the full incident report →

Minor February 19, 2026

on-site ai assistant is failing to respond

Detected by Pingoru
Feb 19, 2026, 03:24 PM UTC
Resolved
Feb 19, 2026, 03:24 PM UTC
Duration
—
Affected: Display
Timeline · 3 updates
  1. identified Feb 19, 2026, 08:11 AM UTC

    Status: Identified we are seeing an issue with rate limiting on one of our services relevant to the assistant and currently deploying a fix Affected components Display (Degraded performance)

  2. identified Feb 19, 2026, 08:23 AM UTC

    Status: Identified The fix has been deployed and the assistant should now work as expected. Affected components Display (Operational)

  3. resolved Feb 19, 2026, 03:24 PM UTC

    Status: Resolved The fix has been deployed and the assistant should now work as expected. Affected components Display (Operational)

Read the full incident report →

Minor February 17, 2026

Github outage impacting some documentation updates.

Detected by Pingoru
Feb 17, 2026, 07:24 PM UTC
Resolved
Feb 17, 2026, 07:24 PM UTC
Duration
—
Timeline · 2 updates
  1. monitoring Feb 17, 2026, 06:43 PM UTC

    Status: Monitoring Github is currently experiencing an outage. Preview deployments and documentation updates may take a while to propagate. View Github's Status page for more up-to-date info: https://www.githubstatus.com

  2. resolved Feb 17, 2026, 07:24 PM UTC

    Status: Resolved Github has resolved their incident

Read the full incident report →

Minor February 12, 2026

Intermittant issues with page loads

Detected by Pingoru
Feb 12, 2026, 11:10 PM UTC
Resolved
Feb 12, 2026, 11:10 PM UTC
Duration
—
Affected: Display
Timeline · 4 updates
  1. investigating Feb 12, 2026, 09:01 PM UTC

    Status: Investigating We are investigating reports of intermittent slowness or 5xx responses for uncached page loads. We will follow up with updates as we have them. Affected components Display (Degraded performance)

  2. investigating Feb 12, 2026, 09:20 PM UTC

    Status: Investigating We have identified the removal of a caching component as the potential cause of the issues. We are working to restore this component and have upsized our services in the meantime to prevent degradation. Affected components Display (Degraded performance)

  3. monitoring Feb 12, 2026, 10:01 PM UTC

    Status: Monitoring We have seen widespread recovery after upsizing our services. We will continue to monitor for any further degradation in service. Affected components Display (Degraded performance)

  4. resolved Feb 12, 2026, 11:10 PM UTC

    Status: Resolved We have restored the caching layer that was removed and have seen continued return to normal error rates and latency. If you are experiencing issues with page renders, please reach out to us at [email protected] "[email protected]": mailto:[email protected] Affected components Display (Operational)

Read the full incident report →

Minor February 7, 2026

Search Quality Degredation

Detected by Pingoru
Feb 07, 2026, 11:27 PM UTC
Resolved
Feb 07, 2026, 11:27 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating Feb 06, 2026, 07:10 PM UTC

    Status: Investigating We are investigating reports of specific search indexes being partially degraded. We are identifying the root cause and formulating a solution to repair all broken indexes. Any customers that feel that they are affected should run a manual update which will repair their index automatically.

  2. identified Feb 06, 2026, 07:26 PM UTC

    Status: Identified We have identified a fix that will repair most broken indexes and are working on deploying it now.

  3. monitoring Feb 07, 2026, 10:37 PM UTC

    Status: Monitoring We have identified the root cause of fragmented indexes as a step in our ingestion pipeline when embing documents. A fix has been rolled out over night and we have not noticed any further ingestion failures. We identified and fixed 50 deployment's indexes and are doing a final scan to ensure all indexes are healthy.

  4. resolved Feb 07, 2026, 11:27 PM UTC

    Status: Resolved We have identified all indices which are half complete and ran manual updates to repair them.

Read the full incident report →

Minor February 5, 2026

Editor displaying parsing errors for some users

Detected by Pingoru
Feb 05, 2026, 09:02 PM UTC
Resolved
Feb 05, 2026, 09:02 PM UTC
Duration
—
Affected: Dashboard
Timeline · 4 updates
  1. investigating Feb 05, 2026, 08:24 PM UTC

    Status: Investigating We are currently investigating an issue affecting the editor that may cause it to showcase parsing errors. We will follow up with updates as we have them. Affected components Dashboard (Degraded performance)

  2. identified Feb 05, 2026, 08:31 PM UTC

    Status: Identified We have identified and rolled back the change causing the editor to become unresponsive. The fix has been deployed, but some users may continue to experience the issue due to cached assets. We are actively working to clear affected caches. Affected components Dashboard (Degraded performance)

  3. monitoring Feb 05, 2026, 08:47 PM UTC

    Status: Monitoring We have deployed an update to clear affected caches. We are monitoring to confirm full resolution. If you continue to experience any issues, please contact support. Affected components Dashboard (Degraded performance)

  4. resolved Feb 05, 2026, 09:02 PM UTC

    Status: Resolved This issue has been fully resolved. The root cause was identified and a fix has been deployed. All editor functionality has been restored. If you are still experiencing any issues, please contact support. Affected components Dashboard (Operational)

Read the full incident report →

Minor February 3, 2026

Degraded Performance - Updates

Detected by Pingoru
Feb 03, 2026, 01:46 PM UTC
Resolved
Feb 03, 2026, 01:46 PM UTC
Duration
—
Affected: Updates
Timeline · 3 updates
  1. investigating Feb 03, 2026, 01:25 PM UTC

    Status: Investigating We're aware of delays affecting update processing and are currently investigating the cause. We'll post an update as soon as we have more information. Affected components Updates (Degraded performance)

  2. monitoring Feb 03, 2026, 01:37 PM UTC

    Status: Monitoring We scaled up capacity to address elevated queue times. Processing is recovering and delays should clear shortly. We'll continue monitoring before marking this resolved. Affected components Updates (Degraded performance)

  3. resolved Feb 03, 2026, 01:46 PM UTC

    Status: Resolved The update processing delays have been fully resolved. All queues are operating normally again. Affected components Updates (Operational)

Read the full incident report →