CrateDB Cloud Outage History
11 incidents recorded over the last 365 days. 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 CrateDB Cloud Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 4, 2026 | CrateDB Cloud - Scheduled Infrastructure Maintenance GCP US-Central1Verification is currently underway for the maintenance items. | 2h 0m | Scheduled |
| Nov 4, 2026 | CrateDB Cloud - Scheduled Infrastructure Maintenance AWS US-West-2Scheduled maintenance is currently in progress. We will provide updates as necessary. | 2h 0m | Scheduled |
| Nov 3, 2026 | CrateDB Cloud - Scheduled Infrastructure Maintenance AWS EU-West-1Scheduled maintenance is currently in progress. We will provide updates as necessary. | 2h 0m | Scheduled |
| Nov 3, 2026 | CrateDB Cloud - Scheduled Infrastructure Maintenance AWS US-East-1Scheduled maintenance is currently in progress. We will provide updates as necessary. | 2h 0m | Scheduled |
| Nov 3, 2026 | CrateDB Cloud - Scheduled Infrastructure Maintenance - STACKITScheduled maintenance is currently in progress. We will provide updates as necessary. | 2h 0m | Scheduled |
| Sep 24, 2026 | CrateDB Cloud - Scheduled Infrastructure Maintenance on AzureThe scheduled maintenance has been completed. | 36h 0m | Scheduled |
| Sep 22, 2026 | CrateDB Cloud - Scheduled Infrastructure Maintenance AWSThe scheduled maintenance has been completed. | 36h 0m | Scheduled |
| Jun 25, 2026 | Cloud Console MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Feb 18, 2026 | CrateDB Cloud - Scheduled Infrastructure Maintenance AWSThe scheduled maintenance has been completed. | 36h 0m | Scheduled |
| Feb 17, 2026 | CrateDB Cloud - Scheduled Infrastructure Maintenance Azure EastUS2The scheduled maintenance has been completed. | 8h 0m | Scheduled |
| Feb 16, 2026 | CrateDB Cloud - Scheduled Infrastructure Maintenance on Azure WestEuropeThe scheduled maintenance has been completed. | 8h 0m | Scheduled |
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 CrateDB Cloud 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 CrateDB Cloud 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 CrateDB Cloud 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 CrateDB Cloud outage in this window ran 1d 12h, against a mean recovery of 12h 16m. If you depend on CrateDB Cloud 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.