Poolside Cloud Outage History
6 incidents recorded over the last 365 days, 6 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 Poolside Cloud Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Aug 25, 2026 | laguna-s-2.1 inference api has partial outageThis incident has been resolved. laguna-s-2.1 is operating normally. We apologize for any disruption caused. | 39 min | Resolved |
| Aug 11, 2026 | Laguna S 2.1 inference degradedThis incident has been resolved. We apologize for any disruption caused. | 57 min | Resolved |
| Aug 11, 2026 | Laguna S 2.1 inference degradedThis incident has been resolved and the free endpoint is operating normally. We apologize for any disruption caused. | 2h 23m | Resolved |
| Jul 1, 2026 | Inference API service degradationThis incident has been resolved. **Inference API** is operating normally. We apologize for any disruption caused. | 31 min | Resolved |
| Jun 17, 2026 | inference issues with lagunaM modelThis incident has been resolved. Inference of LagunaM is operating normally. We apologize for any disruption caused. | 39 min | Resolved |
| May 25, 2026 | Ability to create API tokens impactedWe have confirmed that the issue creating API keys has now been resolved. | 46 min | 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 Poolside 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 Poolside 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 Poolside 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 Poolside Cloud outage in this window ran 2h 23m, against a mean recovery of 59 min. If you depend on Poolside 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.