Is Zuplo Down?
- Zuplo's status page
- Operational · no open incidents
- FlareWarden checks
- Website reachable · 8 of 8 regions · 277 ms
Right now
The verdict is the worse of these two. How we decide
Zuplo's status page
status.zuplo.com · read · checked every 3 minutes
| Component | Status |
|---|---|
| API Gateways (Cloud Gateway) | Operational |
| Core Runtime (Cloud Gateway) | Operational |
| Api Key Validation (Cloud Gateway) | Operational |
| Rate Limiting & Quota Services (Cloud Gateway) | Operational |
| API Key Management | Operational |
| Build & Deployment Services | Operational |
| Portal | Operational |
| Website | Operational |
| Documentation | Operational |
| Developer Portals | Operational |
FlareWarden checks
zuplo.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours
- Regions up
- 8 of 8
- Response
- 277 ms
- Checked
By region
- Ashburn reachable, 211 ms
- Frankfurt reachable, 259 ms
- Johannesburg reachable, 475 ms
- London reachable, 200 ms
- Los Angeles reachable, 205 ms
- Newark reachable, 218 ms
- São Paulo reachable, 304 ms
- Tokyo reachable, 350 ms
Timing by region
| Region | DNS | TCP | TLS | TTFB |
|---|---|---|---|---|
| Ashburn | 30 ms | 6 ms | 26 ms | 192 ms |
| Frankfurt | 97 ms | 1 ms | 11 ms | 248 ms |
| Johannesburg | 209 ms | 1 ms | 75 ms | 438 ms |
| London | 19 ms | 2 ms | 11 ms | 190 ms |
| Los Angeles | 43 ms | 2 ms | 25 ms | 194 ms |
| Newark | 14 ms | 2 ms | 19 ms | 208 ms |
| São Paulo | 164 ms | 1 ms | 8 ms | 296 ms |
| Tokyo | 145 ms | 1 ms | 10 ms | 344 ms |
History
Incidents Zuplo reported
Since Oct 22, 15 days · from status.zuplo.com
- Incidents
- 0
- Major or critical
- 0
- Median to resolve
- —
No incidents reported in this window.
Zuplo website availability
Measured by FlareWarden · zuplo.com
- Last 7 days
- 100%
- Last 30 days
- 100%
- Last 90 days
- 100%
- Avg response, 30 days
- 268ms
Last 30 days
17-day clean streakMeasured by FlareWarden's own checks of zuplo.com from multiple regions every 6 hours. Zuplo's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 17 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
What Zuplo does
Zuplo is an API gateway and API management platform. Teams define routes and policies such as API key authentication and rate limiting in code kept in Git, then deploy them to Zuplo's Managed Edge across 300+ data centers, to a managed dedicated instance on a cloud they choose, or to their own Kubernetes cluster. Zuplo can also host the developer portal where an API's users read its docs.
What an outage looks like
Most Zuplo incidents hit the control side: builds and deployments fail or hang, saves in the portal.zuplo.com working copy stall, or the portal itself will not load or sign in. Hosted developer portals have returned errors and failed to load static assets. Gateway traffic is reported separately, in four Cloud Gateway rows: API Gateways, Core Runtime, API key validation and rate limiting.
What to do about it
Check status.zuplo.com and note which rows are affected. If only Portal or Build & Deployment Services are named, hold deploys and retry after the incident resolves: in past deployment incidents Zuplo said existing gateways kept running. If a developer portal still fails afterwards, Zuplo has advised redeploying it manually. Support is the Zuplo Discord for every plan, plus support@zuplo.com on enterprise plans.
Is it down for everyone, or just you?
If this page says Zuplo is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.
Related services
Zuplo outage FAQ
Do my APIs go down when the Zuplo portal is down?
Is it Zuplo or Cloudflare?
Why does my developer portal fail when the API works?
Does a Zuplo incident affect managed dedicated customers too?
How long do Zuplo incidents usually last?
How we measure this
- We request Zuplo's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
- Response times average only the regions that actually served the page, so a timeout never inflates the number.
- Where Zuplo publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of Zuplo itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.
Get alerted when Zuplo goes down
We check Zuplo every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.
Start Free Monitoring