Redpanda Outage History
17 incidents recorded over the last 365 days, 17 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Redpanda Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 29, 2026 | CVE-2026-98432 InvestigationPlease see our Technical Service Bulletin for further information, and future updates. <https://knowledgebase.redpanda.com/articles/5048937749-guidance-for-linux-kernel-ipv4-tcp-use-after-free-cve-2026-98432> | 7h 33m | Resolved |
| Oct 22, 2026 | CVE-2026-111943 (emudhra) ResponseRedpanda has reviewed and confirmed that Redpanda Cloud and its associated applications are not at risk of [CVE-2026-111943](https://nvd.nist.gov/vuln/detail/cve-2026-111943). Self-Hosted Customers will receive a… | 7h 50m | Resolved |
| Sep 28, 2026 | Partial outage for customers signing into cloud.redpanda.comNo observed impact, and all systems are back to normal. | 3h 1m | Resolved |
| Sep 16, 2026 | Scheduled Database MaintenanceThe scheduled database maintenance has been successfully completed. All Cloud functionality is operating normally. | 36 min | Resolved |
| Aug 4, 2026 | Some users unable to access cloud.redpanda.comWe've identified, and resolved the issue, you will need to refresh the page if you are stuck on the loading screen. | 18 min | Resolved |
| Jul 31, 2026 | Elevated authorization errors in Redpanda CloudRedpanda is aware of an incident that may have impacted cloud customers. A fix for this problem has been implemented and the impact is resolved. | 5h 29m | Resolved |
| Jul 8, 2026 | New Signs Ups Are Failing Authorize to RedpandaRedpanda is aware of an incident that may have impacted new account sign-ups to Redpanda Cloud. A fix has been implemented and the impact is resolved. | 6h 10m | Resolved |
| Apr 27, 2026 | DNS Issue affecting Redpanda Cloud APIThis issue has been fully resolved. | 6h 5m | Resolved |
| Apr 22, 2026 | Scheduled Maintenance - Database MigrationDatabase Migration Completed | 1h 30m | Resolved |
| Apr 14, 2026 | Customers unable to log in Redpanda is aware of an incident that may have impacted cloud customers. A fix for this problem has been implemented and the impact is resolved. | 53 min | Resolved |
| Mar 19, 2026 | New user account access issuesRedpanda is aware of an incident that may have impacted cloud customers. A fix for this problem has been implemented and the impact is resolved. | 3h 14m | Resolved |
| Mar 10, 2026 | Cluster Creation IssueRedpanda is aware of an incident that may have impacted cloud customers. A fix for this problem has been implemented and the impact is resolved. | 5h 20m | Resolved |
| Feb 5, 2026 | Unable to Sign Up for ServerlessRedpanda is aware of an incident that may have impacted new serverless customers during signup. A fix for this problem has been implemented, and the impact has been resolved. | 18h 59m | Resolved |
| Jan 29, 2026 | Remote MCP Unavailable for New GCP ClustersRedpanda is aware of an incident that may have affected cloud customers when using the Remote MCP feature. The feature has been temporarily disabled, and a fix for this feature will be rolled out. | 200h 3m | Resolved |
| Dec 6, 2025 | Currently new AWS clusters are unable to be createdIssue has been resolved. AWS cluster creation is now working as expected. | 12h 49m | Resolved |
| Nov 11, 2025 | GCP cluster creations issues in us-central1All GCP cluster creation issues have been resolved | 7h 18m | Resolved |
| Nov 8, 2025 | Issues around creating new clustersThe issue with the external dependency has been resolved and cluster creation is no longer impacted. | 2h 17m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Redpanda incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Redpanda Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Redpanda acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Redpanda outage in this window ran 8d 8h, against a mean recovery of 17h 2m. If you depend on Redpanda in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.