User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Productivity
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 1058 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 03 | 0 | 0.0 | 1289 ms | 0 |
| Tue 05 | 0 | 0.0 | 931 ms | 0 |
| Tue 07 | 0 | 0.0 | 1038 ms | 0 |
| Tue 09 | 0 | 0.0 | 1211 ms | 0 |
| Tue 11 | 0 | 0.0 | 784 ms | 0 |
| Tue 13 | 0 | 0.0 | 885 ms | 0 |
| Tue 16 | 0 | 0.0 | 561 ms | 0 |
| Tue 18 | 0 | 0.0 | 907 ms | 0 |
| Tue 20 | 0 | 0.0 | 709 ms | 0 |
| Tue 22 | 0 | 0.0 | 1202 ms | 0 |
| Wed 01 | 0 | 0.0 | 785 ms | 0 |
| Wed 03 | 0 | 0.0 | 803 ms | 0 |
| Wed 05 | 0 | 0.0 | 867 ms | 0 |
| Wed 07 | 0 | 0.0 | 1053 ms | 0 |
| Wed 10 | 0 | 0.0 | 905 ms | 0 |
| Wed 11 | 0 | 0.0 | 855 ms | 0 |
| Wed 13 | 0 | 0.0 | 722 ms | 0 |
| Wed 15 | 0 | 0.0 | 536 ms | 0 |
| Wed 17 | 0 | 0.0 | 1212 ms | 0 |
| Wed 20 | 0 | 0.0 | 1097 ms | 0 |
| Wed 22 | 0 | 0.0 | 1320 ms | 0 |
| Thu 00 | 0 | 0.0 | 517 ms | 0 |
| Thu 02 | 0 | 0.0 | 868 ms | 0 |
| Thu 04 | 0 | 0.0 | 934 ms | 0 |
| Thu 06 | 0 | 0.0 | 841 ms | 0 |
| Thu 08 | 0 | 0.0 | 943 ms | 0 |
| Thu 10 | 0 | 0.0 | 1061 ms | 0 |
| Thu 12 | 0 | 0.0 | 1125 ms | 0 |
| Thu 15 | 0 | 0.0 | 1114 ms | 0 |
| Thu 17 | 0 | 0.0 | 890 ms | 0 |
| Thu 19 | 0 | 0.0 | 802 ms | 0 |
| Thu 21 | 0 | 0.0 | 450 ms | 0 |
| Thu 22 | 0 | 0.0 | 642 ms | 0 |
| Fri 00 | 0 | 0.0 | 890 ms | 0 |
| Fri 02 | 0 | 0.0 | 954 ms | 0 |
| Fri 04 | 0 | 0.0 | 952 ms | 0 |
| Fri 06 | 0 | 0.0 | 1035 ms | 0 |
| Fri 08 | 0 | 0.0 | 1561 ms | 0 |
| Fri 10 | 0 | 0.0 | 774 ms | 0 |
| Fri 11 | 0 | 0.0 | 876 ms | 0 |
| Fri 13 | 0 | 0.0 | 578 ms | 0 |
| Fri 15 | 0 | 0.0 | 1019 ms | 0 |
| Fri 17 | 0 | 0.0 | 529 ms | 0 |
| Fri 18 | 0 | 0.0 | 613 ms | 0 |
| Fri 20 | 0 | 0.0 | 809 ms | 0 |
| Fri 22 | 0 | 0.0 | 609 ms | 0 |
| Fri 23 | 0 | 0.0 | 802 ms | 0 |
| Sat 01 | 0 | 0.0 | 1058 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 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Rebel 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 Rebel goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Rebel alerts to Slack, Discord or a webhook — free.
We track Rebel (rebel.com) as part of the Productivity group. Register a domain, build your site, and run professional email with Rebel. Canadian registrar, transparent pricing, and real human support for entrepreneurs.
Rebel publishes an official status page at status.rebel.com; when we can read it, its incident level is folded into the status shown here.
Common problems for productivity services: files not syncing, editors not loading, and sign-in problems.
Measured uptime from our checks: 100% over 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 863 ms average, 529–1561 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Rebel incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
863 ms on average over the last 24 hours (529–1561 ms).
Yes, at https://status.rebel.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For productivity services, watch for files not syncing, editors not loading, and sign-in problems. If many people report Rebel here at once, the problem is on Rebel'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 Rebel. 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.