Vespa Cloud Outage History
4 incidents recorded over the last 365 days, 4 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 Vespa Cloud Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 2, 2026 | Vespa zone impaired: dev.aws-euw1-az1 | 1h 23m | Resolved |
| Oct 14, 2026 | Query timeouts for some applications | 27h 28m | Resolved |
| Oct 1, 2026 | Intermittent “Node Allocation Failure” in GCP test and staging environments | 650h 4m | Resolved |
| Aug 19, 2026 | Failing staging tests in AWS us-east-1c | 7h 29m | 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 Vespa 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 Vespa 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 Vespa 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 Vespa Cloud outage in this window ran 27d 2h, against a mean recovery of 7d 3h. If you depend on Vespa 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.