Potential downtime
Timeline · 1 update
- investigating Aug 27, 2026, 02:34 AM UTC
Pingdom says we're down and the team is taking a closer look.
Redocly Outage History
Redocly is up right nowRedocly had 11 outages in the last 2 years totaling 27h 16m of downtime — averaging 0.5 incidents per month.
There were 11 Redocly outages since October 20, 2025 totaling 27h 16m of downtime. Each is summarised below — incident details, duration, and resolution information.
Degraded performance due to a GitHub outage
Timeline · 2 updates
- investigating Aug 17, 2026, 02:41 PM UTC
GitHub is currently experiencing an incident, which may cause delays or intermittent failures in features that depend on it — repository syncing, pushes and pulls, builds, and deploys. Your content and existing published sites are not affected. We're tracking GitHub's status page and will update this page as the situation changes.
- resolved Aug 17, 2026, 10:56 PM UTC
GitHub has resolved the incident. Thanks for your patience.
Intermittent delays in background processing (EU region)
Timeline · 1 update
- resolved Aug 04, 2026, 07:35 AM UTC
Our EU region experienced an issue with the internal messaging system that coordinates background work. Most activity was processed normally, but a small number of operations, such as editor sessions and project updates from Git providers may have been delayed in some cases. The issue was identified and fully resolved the same day. US region was not affected.
Issues with project deploys
Timeline · 3 updates
- investigating May 12, 2026, 03:02 PM UTC
We have identified an issue affecting project deployments and are actively working toward a resolution.
- investigating May 12, 2026, 05:03 PM UTC
We've fixed the core issue, and are waiting for things to recover.
- resolved May 12, 2026, 06:41 PM UTC
We've now resolved the incident. New production and preview deployments did not apply the recent changes. Already-running deployments continued to serve traffic normally, and no data was lost. After resolving the underlying issue, we automatically re-deployed all affected projects, and they now include the latest changes. No action is required on your side. We apologize for the inconvenience. Thanks for your patience.
We're currently having issues with project deploys and previews
Timeline · 3 updates
- investigating Apr 23, 2026, 12:21 PM UTC
Some people are experiencing problems with project deploys and previews. We already identified the issue and are working on the fix. Please standby for further updates.
- investigating Apr 23, 2026, 12:41 PM UTC
We've fixed the core issue, and are waiting for things to recover.
- resolved Apr 23, 2026, 01:30 PM UTC
We've now resolved the incident. Thanks for your patience.
We're having the problem with Reunite API
Timeline · 1 update
- resolved Jan 26, 2026, 06:33 PM UTC
We've now resolved the incident. Thanks for your patience. Root Cause The outage was caused by a loss of quorum within our primary cluster management layer. As new instances were being rotated into the cluster, the management nodes experienced a sharp increase in resource utilization. This spike in load prevented the nodes from communicating effectively, leading to the loss of a cluster leader and a subsequent breakdown in task scheduling and service discovery.
We're currently having issues
Timeline · 1 update
- resolved Jan 14, 2026, 11:26 PM UTC
We've now resolved the incident. Thanks for your patience.
Project deployments and GitHub status updates degradation
Timeline · 1 update
- resolved Dec 23, 2025, 10:02 AM UTC
We've now resolved the incident. Thanks for your patience.
API Performance Degradation
Timeline · 1 update
- resolved Dec 14, 2025, 02:53 PM UTC
A database migration triggered a deadlock, causing temporary API latency and timeouts. The migration was aborted, and service health was restored immediately. We have updated our migration procedures to prevent recurrence.
Service degradation: deployments and webview editor
Timeline · 1 update
- resolved Dec 05, 2025, 09:26 AM UTC
The has been resolved. Thanks for your patience.
Outage under investigation
Timeline · 1 update
- resolved Nov 11, 2025, 04:47 PM UTC
We've identified the root cause as an issue with a release procedure.