Mintlify Outage History

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.

Status: Resolved The backlog has been fully resolved. We've identified the root causes and are deploying fixes to prevent similar incidents in the future. Affected components Updates (Operational)

Status: Resolved The Slack agent is back online after successfully migrating to a new model and all functionality has been restored. Affected components Dashboard (Operational)

Status: Resolved The intermittent outages and slow load times on our documentation sites have been resolved. The root cause was an upstream server issue. All services should be operating normally.

Status: Resolved The fix has been deployed and the Mintlify Slack agent is back up and fully operational.

Status: Resolved Search issues were caused by a misconfigured setting affecting a small subset of customers. This has been corrected and search is operating normally. Affected components Display (Operational)

Status: Resolved The redeployment queue has been cleared and job times have returned to normal. We are continuing to investigate the underlying cause. Affected components Updates (Operational)

Status: Resolved Search functionality experienced a service disruption affecting both unauthenticated and authenticated users. The incident lasted approximately 92 minutes. A fix for unauthenticated sites was deployed first, but authenticated sites required additional remediation due to a separate edge case in the authentication path. Impact • Affected window: 7:12 PM – 8:44 PM PT • Users affected: All users relying on search in authenticated contexts • User experience: Search queries returned errors or failed to return results during the affected period Timeline Time (PT) Event 7:12 PM Upstream provider begins index migration; search functionality starts failing ~7:20 PM Incident detected via monitoring/alerts ~7:22 PM On-call engineer begins investigation; root cause identified as upstream index migration ~7:30 PM Decision made to fail over to backup indices 7:54 PM Migration to backup indices complete; search restored for unauthenticated sites ~8:06 PM Separate edge case identified affecting authenticated sites 8:44 PM Fix deployed for authenticated sites; full resolution confirmed — search restored across all sites Root Cause An upstream provider initiated an index migration, which caused search functionality to begin failing. Unauthenticated and authenticated search requests followed different code paths, so failing over to backup indices resolved the issue for unauthenticated sites first. Authenticated sites hit a separate edge case that required additional remediation, extending the total incident duration. Note: We are completing our migration to a completely new search system tomorrow, which provide significantly improved stability going forward. Affected components Display (Operational)

Status: Resolved A search outage affected all Mintlify-powered sites after our upstream search provider executed a migration on our search indices. The migration rendered existing indices unavailable, causing search functionality to return errors or no results across all customer sites. The incident was resolved by failing over to backup indices. Impact • Scope: All Mintlify sites with search functionality • User experience: Search queries returned errors or empty results for the duration of the outage • Duration of impact: ~42 minutes Timeline (all times PT) Time Event 7:12 PM Upstream provider begins index migration; search functionality starts failing ~7:20 PM Incident detected via monitoring/alerts ~7:22 PM On-call engineer begins investigation; root cause identified as upstream index migration ~7:30 PM Decision made to fail over to backup indices 7:54 PM Migration to backup indices complete; search functionality restored across all sites Root Cause Our upstream search provider initiated a migration of our search indices without adequate coordination. This migration caused the primary indices to become unavailable, which in turn broke search queries across all Mintlify sites. Resolution Within approximately 10 minutes of detecting the incident, the team initiated a failover to pre-existing backup indices. Once the migration to backup indices completed, full search functionality was restored. Affected components Display (Operational)

Status: Resolved Access to all sites is now restored and we will be publishing a detailed post-mortem here shortly. Affected components Display (Operational)

Status: Resolved From 12:04 to 12:09 PDT, most docs sites experienced either a partial or total outage when attempting to view pages. We caught the issue internally immediately, and were able to roll back code for all affected sites within minutes. This was caused by incorrect debug code pushed by one of our developers. No further action is required on our customers' part to resolve the issue. Affected components Display (Operational)

Status: Resolved We identified a small subset of customers with missing documents and repaired those indices with a manual update. Please report any search issues you may be seeing to [email protected] so we can address if there are further repairs needed. Affected components Display (Operational)

Status: Resolved GitHub has resolved the webhook degradation. Preview builds and redeploys should now function normally. Affected components Updates (Operational)

Status: Resolved The issue should be resolved. Affected components Display (Operational)

Status: Resolved We investigated the reports and determined there was no underlying system issue. The affected cases were isolated and are being resolved. Preview generations and deployment updates are operating normally. Affected components Updates (Operational)

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

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)

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)

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

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)

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

Status: Resolved Search pipeline is no longer backed up. Updates will resume to be at their usual cadence.

Status: Resolved The ingestion queue is flushed. Search indexes will be updated at the usual pace

Status: Resolved Github has resolved their incident with increased 401 errors on github

Status: Resolved The fix has been deployed and the assistant should now work as expected.

Status: Resolved The fix has been deployed and the assistant should now work as expected.

Status: Resolved The fix has been deployed and the assistant should now work as expected.

Status: Resolved The fix has been deployed and the assistant should now work as expected.

Status: Resolved Github has resolved their incident

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)

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