User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / 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 2 hr ago. Last stored result reached it in 40 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 13 | 0 | 0.0 | 69 ms | 0 |
| Mon 15 | 0 | 0.0 | 51 ms | 0 |
| Mon 17 | 0 | 0.0 | 72 ms | 0 |
| Mon 19 | 0 | 0.0 | 44 ms | 0 |
| Mon 21 | 0 | 0.0 | 186 ms | 0 |
| Mon 23 | 0 | 0.0 | 61 ms | 0 |
| Tue 01 | 0 | 0.0 | 84 ms | 0 |
| Tue 03 | 0 | 0.0 | 80 ms | 0 |
| Tue 05 | 0 | 0.0 | 75 ms | 0 |
| Tue 08 | 0 | 0.0 | 56 ms | 0 |
| Tue 10 | 0 | 0.0 | 55 ms | 0 |
| Tue 12 | 0 | 0.0 | 53 ms | 0 |
| Tue 14 | 0 | 0.0 | 134 ms | 0 |
| Tue 16 | 0 | 0.0 | 127 ms | 0 |
| Tue 19 | 0 | 0.0 | 71 ms | 0 |
| Tue 21 | 0 | 0.0 | 162 ms | 0 |
| Tue 23 | 0 | 0.0 | 68 ms | 0 |
| Wed 01 | 0 | 0.0 | 82 ms | 0 |
| Wed 04 | 0 | 0.0 | 49 ms | 0 |
| Wed 06 | 0 | 0.0 | 71 ms | 0 |
| Wed 08 | 0 | 0.0 | 283 ms | 0 |
| Wed 10 | 0 | 0.0 | 54 ms | 0 |
| Wed 12 | 0 | 0.0 | 66 ms | 0 |
| Wed 15 | 0 | 0.0 | 43 ms | 0 |
| Wed 17 | 0 | 0.0 | 90 ms | 0 |
| Wed 19 | 0 | 0.0 | 88 ms | 0 |
| Wed 21 | 0 | 0.0 | 61 ms | 0 |
| Wed 23 | 0 | 0.0 | 59 ms | 0 |
| Thu 01 | 0 | 0.0 | 121 ms | 0 |
| Thu 04 | 0 | 0.0 | 75 ms | 0 |
| Thu 06 | 0 | 0.0 | 99 ms | 0 |
| Thu 08 | 0 | 0.0 | 35 ms | 0 |
| Thu 10 | 0 | 0.0 | 39 ms | 0 |
| Thu 12 | 0 | 0.0 | 50 ms | 0 |
| Thu 14 | 0 | 0.0 | 60 ms | 0 |
| Thu 16 | 0 | 0.0 | 33 ms | 0 |
| Thu 18 | 0 | 0.0 | 129 ms | 0 |
| Thu 20 | 0 | 0.0 | 51 ms | 0 |
| Thu 22 | 0 | 0.0 | 389 ms | 0 |
| Fri 00 | 0 | 0.0 | 117 ms | 0 |
| Fri 02 | 0 | 0.0 | 57 ms | 0 |
| Fri 04 | 0 | 0.0 | 68 ms | 0 |
| Fri 06 | 0 | 0.0 | 131 ms | 0 |
| Fri 08 | 0 | 0.0 | 153 ms | 0 |
| Fri 11 | 0 | 0.0 | 51 ms | 0 |
| Fri 13 | 0 | 0.0 | 31 ms | 0 |
| Fri 15 | 0 | 0.0 | 38 ms | 0 |
| Fri 17 | 0 | 0.0 | 40 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 Notro 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 Notro goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Notro alerts to Slack, Discord or a webhook — free.
Notro is listed in our Cloud & developer category and checked at notro.io. Uma plataforma completa para assistência 24hs Auto, Residencial, Viagem, Funeral e Saúde
Notro publishes an official status page at status.notro.io; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with 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: 97 ms average, 21–389 ms range across 12 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Notro incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
97 ms on average over the last 24 hours (21–389 ms).
Yes, at https://status.notro.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 Notro here at once, the problem is on Notro'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 Notro. 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.