User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
zupper.com.br · Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 14 min ago. Last stored result reached it in 1093 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 15 | 0 | 0.0 | 1341 ms | 0 |
| Mon 18 | 0 | 0.0 | 1240 ms | 0 |
| Mon 20 | 0 | 0.0 | 1656 ms | 0 |
| Mon 22 | 0 | 0.0 | 1339 ms | 0 |
| Tue 00 | 0 | 0.0 | 1174 ms | 0 |
| Tue 02 | 0 | 0.0 | 1099 ms | 0 |
| Tue 04 | 0 | 0.0 | 1470 ms | 0 |
| Tue 06 | 0 | 0.0 | 1167 ms | 0 |
| Tue 08 | 0 | 0.0 | 1644 ms | 0 |
| Tue 11 | 0 | 0.0 | 1070 ms | 0 |
| Tue 13 | 0 | 0.0 | 963 ms | 0 |
| Tue 15 | 0 | 0.0 | 1063 ms | 0 |
| Tue 17 | 0 | 0.0 | 1187 ms | 0 |
| Tue 20 | 0 | 0.0 | 1176 ms | 0 |
| Tue 22 | 0 | 0.0 | 937 ms | 0 |
| Wed 00 | 0 | 0.0 | 1413 ms | 0 |
| Wed 02 | 0 | 0.0 | 1009 ms | 0 |
| Wed 05 | 0 | 0.0 | 1074 ms | 0 |
| Wed 07 | 0 | 0.0 | 1236 ms | 0 |
| Wed 09 | 0 | 0.0 | 1290 ms | 0 |
| Wed 11 | 0 | 0.0 | 1065 ms | 0 |
| Wed 13 | 0 | 0.0 | 1382 ms | 0 |
| Wed 15 | 0 | 0.0 | 1229 ms | 0 |
| Wed 18 | 0 | 0.0 | 1190 ms | 0 |
| Wed 20 | 0 | 0.0 | 1162 ms | 0 |
| Wed 22 | 0 | 0.0 | 1296 ms | 0 |
| Thu 00 | 0 | 0.0 | 1106 ms | 0 |
| Thu 02 | 0 | 0.0 | 900 ms | 0 |
| Thu 04 | 0 | 0.0 | 1748 ms | 0 |
| Thu 07 | 0 | 0.0 | 1284 ms | 0 |
| Thu 09 | 0 | 0.0 | 1322 ms | 0 |
| Thu 11 | 0 | 0.0 | 842 ms | 0 |
| Thu 13 | 0 | 0.0 | 1078 ms | 0 |
| Thu 15 | 0 | 0.0 | 902 ms | 0 |
| Thu 17 | 0 | 0.0 | 1128 ms | 0 |
| Thu 19 | 0 | 0.0 | 895 ms | 0 |
| Thu 21 | 0 | 0.0 | 1002 ms | 0 |
| Thu 23 | 0 | 0.0 | 999 ms | 0 |
| Fri 01 | 0 | 0.0 | 1108 ms | 0 |
| Fri 03 | 0 | 0.0 | 1502 ms | 0 |
| Fri 04 | 0 | 0.0 | 2065 ms | 0 |
| Fri 06 | 0 | 0.0 | 1474 ms | 0 |
| Fri 08 | 0 | 0.0 | 1766 ms | 0 |
| Fri 10 | 0 | 0.0 | 1153 ms | 0 |
| Fri 12 | 0 | 0.0 | 1613 ms | 0 |
| Fri 14 | 0 | 0.0 | 1629 ms | 0 |
| Fri 16 | 0 | 0.0 | 1093 ms | 0 |
| Fri 17 | 0 | 0.0 | 1317 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Zupper yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Zupper goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Zupper alerts to Slack, Discord or a webhook — free.
We track Zupper (zupper.com.br) as part of the Cloud & developer group. Encontre as melhores ofertas de passagens aéreas para destinos nacionais e internacionais. Viaje mais com Zupper – Brasil na alma, Mundo na mala.
Zupper publishes an official status page at status.zupper.com.br; when we can read it, its incident level is folded into the status shown here.
Common problems for cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 1341 ms average, 895–2065 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Zupper incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
1341 ms on average over the last 24 hours (895–2065 ms).
Yes, at https://status.zupper.com.br.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Zupper here at once, the problem is on Zupper's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Zupper. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.