Zuplo Outage History
12 incidents recorded over the last 365 days, 12 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 Zuplo Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Aug 5, 2026 | Slow file saves on working copyThe fix has resolved the issue. | 1h 35m | Resolved |
| Jul 7, 2026 | Unable to deploy newer versions of your Developer PortalsWe have resolved the issue. Re-deploying your Developer Portal works now. This was due to a resource capacity issue on one of our cloud providers. | 1h 3m | Resolved |
| May 28, 2026 | Degraded performance on building Developer Portals on working-copyOne of our cloud providers were having capacity issues. We have rolled out a fix to increase the build resources for working-copy and the Developer Portal builds have now stabilized. | 11 min | Resolved |
| May 22, 2026 | Intermittent failures with deploymentsThe cloud provider, Cloudflare, has resolved the issue. You can now continue deploying and updating your API Gateways. | 1h 17m | Resolved |
| May 11, 2026 | Intermittent issues deploying for managed-dedicated customersThe fix has been rolled and the issue is resolved. | 3h 16m | Resolved |
| Mar 23, 2026 | Developer Portal CDN IssuesThe issue has been resolved. We are working to add additional tests and processes to verify this type of change going forward. | 5 min | Resolved |
| Mar 17, 2026 | Elevated Error Rate on Developer PortalsThe fix is rolled out and error rates have returned to normal. | 12 min | Resolved |
| Mar 6, 2026 | Developer Portals Failing at High RatesThe issue has been resolved. | 54 min | Resolved |
| Dec 8, 2025 | Elevated Error Rate with Deployments & Management OperationsWe have identified the issue. Upon further investigation this was a limited issue only impacting deletion of existing projects. We have identified only a few customers were impacted. The issue has been resolved. | 20 min | Resolved |
| Dec 5, 2025 | Degraded performance system-wideThe issue has been resolved and all our systems are now operational. | 16 min | Resolved |
| Nov 18, 2025 | Elevated ErrorsCloudflare has reported the incident is fully resolved. We are no longer seeing increased error rates on our services. | 7h 17m | Resolved |
| Nov 6, 2025 | Deployments on Managed Dedicated Clusters are failingWe've rolled out a fix for the issues affecting Managed Dedicated deployments | 19 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 Zuplo 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 Zuplo 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 Zuplo 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 Zuplo outage in this window ran 7h 17m, against a mean recovery of 1h 24m. If you depend on Zuplo 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.