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 6 min ago. Last stored result reached it in 1089 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 1041 ms | 0 |
| Nov 7 | 0 | 0.0 | 716 ms | 0 |
| Nov 7 | 0 | 0.0 | 695 ms | 0 |
| Nov 7 | 0 | 0.0 | 739 ms | 0 |
| Nov 7 | 0 | 0.0 | 963 ms | 0 |
| Nov 8 | 0 | 0.0 | 900 ms | 0 |
| Nov 8 | 0 | 0.0 | 932 ms | 0 |
| Nov 8 | 0 | 0.0 | 1033 ms | 0 |
| Nov 8 | 0 | 0.0 | 1024 ms | 0 |
| Nov 9 | 0 | 0.0 | 996 ms | 0 |
| Nov 9 | 0 | 0.0 | 1027 ms | 0 |
| Nov 9 | 0 | 0.0 | 952 ms | 0 |
| Nov 9 | 0 | 0.0 | 1028 ms | 0 |
| Nov 10 | 0 | 0.0 | 983 ms | 0 |
| Nov 10 | 0 | 0.0 | 977 ms | 0 |
| Nov 10 | 0 | 0.0 | 1098 ms | 0 |
| Nov 10 | 0 | 0.0 | 925 ms | 0 |
| Nov 11 | 0 | 0.0 | 939 ms | 0 |
| Nov 11 | 0 | 0.0 | 1028 ms | 0 |
| Nov 11 | 0 | 0.0 | 1006 ms | 0 |
| Nov 11 | 0 | 0.0 | 966 ms | 0 |
| Nov 12 | 0 | 0.0 | 999 ms | 0 |
| Nov 12 | 0 | 0.0 | 950 ms | 0 |
| Nov 12 | 0 | 0.0 | 1112 ms | 0 |
| Nov 12 | 0 | 0.0 | 967 ms | 0 |
| Nov 13 | 0 | 0.0 | 975 ms | 0 |
| Nov 13 | 0 | 0.0 | 984 ms | 0 |
| Nov 13 | 0 | 0.0 | 971 ms | 0 |
| Nov 13 | 0 | 0.0 | 1089 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 Rigi 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 Rigi goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Rigi alerts to Slack, Discord or a webhook — free.
We track Rigi (rigi.club) as part of the Cloud & developer group. Instant Entertainment,Anytime, Anywhere! Quick, captivating, and endlessly scroll-worthy content at your fingertips.
Rigi publishes an official status page at status.rigi.club; 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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 998 ms average, 955–1096 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Rigi incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
998 ms on average over the last 24 hours (955–1096 ms).
Yes, at https://status.rigi.club.
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 Rigi here at once, the problem is on Rigi'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 Rigi. 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.