User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
cloudez.io · 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 40 min ago. Last stored result reached it in 709 ms.
All clear
All systems operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 21:00 | 0 | 0.0 | 632 ms | 0 |
| 22:45 | 0 | 0.0 | 866 ms | 0 |
| 01:00 | 0 | 0.0 | 501 ms | 0 |
| 03:00 | 0 | 0.0 | 604 ms | 0 |
| 05:00 | 0 | 0.0 | 917 ms | 0 |
| 07:15 | 0 | 0.0 | 1108 ms | 0 |
| 09:15 | 0 | 0.0 | 878 ms | 0 |
| 11:15 | 0 | 0.0 | 777 ms | 0 |
| 13:30 | 0 | 0.0 | 716 ms | 0 |
| 15:30 | 0 | 0.0 | 724 ms | 0 |
| 17:30 | 0 | 0.0 | 760 ms | 0 |
| 19:30 | 0 | 0.0 | 709 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 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Cloudez 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 Cloudez goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Cloudez alerts to Slack, Discord or a webhook — free.
Cloudez is listed in our Cloud & developer category and checked at cloudez.io. Tecnologia de automação é o que fazemos de melhor, mas nossa missão é impulsionar o mercado digital brasileiro. Conheça a Cloudez e o Cloudez Partners
Cloudez publishes an official status page at status.cloudez.io; when we can read it, its incident level is folded into the status shown here.
Typical issues with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 744 ms average, 216–1108 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 Cloudez incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
744 ms on average over the last 24 hours (216–1108 ms).
Yes, at https://status.cloudez.io.
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 Cloudez here at once, the problem is on Cloudez'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 Cloudez. 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.