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 7 min ago. Last stored result reached it in 214 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 14 | 0 | 0.0 | 403 ms | 0 |
| Mon 16 | 0 | 0.0 | 599 ms | 0 |
| Mon 18 | 0 | 0.0 | 174 ms | 0 |
| Mon 20 | 0 | 0.0 | 229 ms | 0 |
| Mon 23 | 0 | 0.0 | 184 ms | 0 |
| Tue 01 | 0 | 0.0 | 240 ms | 0 |
| Tue 03 | 0 | 0.0 | 582 ms | 0 |
| Tue 05 | 0 | 0.0 | 521 ms | 0 |
| Tue 07 | 0 | 0.0 | 369 ms | 0 |
| Tue 09 | 0 | 0.0 | 445 ms | 0 |
| Tue 11 | 0 | 0.0 | 241 ms | 0 |
| Tue 13 | 0 | 0.0 | 677 ms | 0 |
| Tue 16 | 0 | 0.0 | 275 ms | 0 |
| Tue 18 | 0 | 0.0 | 480 ms | 0 |
| Tue 20 | 0 | 0.0 | 219 ms | 0 |
| Tue 22 | 0 | 0.0 | 86 ms | 0 |
| Wed 01 | 0 | 0.0 | 486 ms | 0 |
| Wed 03 | 0 | 0.0 | 263 ms | 0 |
| Wed 05 | 0 | 0.0 | 309 ms | 0 |
| Wed 07 | 0 | 0.0 | 685 ms | 0 |
| Wed 10 | 0 | 0.0 | 671 ms | 0 |
| Wed 12 | 0 | 0.0 | 951 ms | 0 |
| Wed 14 | 0 | 0.0 | 159 ms | 0 |
| Wed 16 | 0 | 0.0 | 98 ms | 0 |
| Wed 18 | 0 | 0.0 | 191 ms | 0 |
| Wed 21 | 0 | 0.0 | 226 ms | 0 |
| Wed 23 | 0 | 0.0 | 669 ms | 0 |
| Thu 01 | 0 | 0.0 | 403 ms | 0 |
| Thu 03 | 0 | 0.0 | 439 ms | 0 |
| Thu 05 | 0 | 0.0 | 97 ms | 0 |
| Thu 07 | 0 | 0.0 | 370 ms | 0 |
| Thu 09 | 0 | 0.0 | 68 ms | 0 |
| Thu 11 | 0 | 0.0 | 100 ms | 0 |
| Thu 13 | 0 | 0.0 | 323 ms | 0 |
| Thu 15 | 0 | 0.0 | 125 ms | 0 |
| Thu 17 | 0 | 0.0 | 148 ms | 0 |
| Thu 20 | 0 | 0.0 | 263 ms | 0 |
| Thu 22 | 0 | 0.0 | 177 ms | 0 |
| Fri 00 | 0 | 0.0 | 238 ms | 0 |
| Fri 02 | 0 | 0.0 | 657 ms | 0 |
| Fri 04 | 0 | 0.0 | 624 ms | 0 |
| Fri 06 | 0 | 0.0 | 69 ms | 0 |
| Fri 08 | 0 | 0.0 | 382 ms | 0 |
| Fri 10 | 0 | 0.0 | 59 ms | 0 |
| Fri 12 | 0 | 0.0 | 195 ms | 0 |
| Fri 14 | 0 | 0.0 | 197 ms | 0 |
| Fri 16 | 0 | 0.0 | 64 ms | 0 |
| Fri 18 | 0 | 0.0 | 214 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 Revolt 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 Revolt goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Revolt alerts to Slack, Discord or a webhook — free.
Revolt, at revolt.ly, is one of the Cloud & developer services we monitor. Automation for Edgenuity, Edmentum, and Subject.com. Auto-advance, supported quiz help, skip intros, and access verified answers where available.
Revolt publishes an official status page at status.revolt.ly; 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: 262 ms average, 59–657 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 Revolt incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
262 ms on average over the last 24 hours (59–657 ms).
Yes, at https://status.revolt.ly.
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 Revolt here at once, the problem is on Revolt'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 Revolt. 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.