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 1 hr ago. Last stored result reached it in 969 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 | 952 ms | 0 |
| Mon 16 | 0 | 0.0 | 962 ms | 0 |
| Mon 19 | 0 | 0.0 | 946 ms | 0 |
| Mon 21 | 0 | 0.0 | 1028 ms | 0 |
| Mon 23 | 0 | 0.0 | 1115 ms | 0 |
| Tue 01 | 0 | 0.0 | 995 ms | 0 |
| Tue 03 | 0 | 0.0 | 907 ms | 0 |
| Tue 05 | 0 | 0.0 | 1064 ms | 0 |
| Tue 07 | 0 | 0.0 | 977 ms | 0 |
| Tue 09 | 0 | 0.0 | 978 ms | 0 |
| Tue 11 | 0 | 0.0 | 967 ms | 0 |
| Tue 14 | 0 | 0.0 | 1138 ms | 0 |
| Tue 16 | 0 | 0.0 | 1058 ms | 0 |
| Tue 18 | 0 | 0.0 | 939 ms | 0 |
| Tue 20 | 0 | 0.0 | 590 ms | 0 |
| Tue 23 | 0 | 0.0 | 980 ms | 0 |
| Wed 01 | 0 | 0.0 | 960 ms | 0 |
| Wed 03 | 0 | 0.0 | 966 ms | 0 |
| Wed 05 | 0 | 0.0 | 582 ms | 0 |
| Wed 08 | 0 | 0.0 | 980 ms | 0 |
| Wed 10 | 0 | 0.0 | 1076 ms | 0 |
| Wed 12 | 0 | 0.0 | 1111 ms | 0 |
| Wed 14 | 0 | 0.0 | 935 ms | 0 |
| Wed 16 | 0 | 0.0 | 1006 ms | 0 |
| Wed 18 | 0 | 0.0 | 1066 ms | 0 |
| Wed 21 | 0 | 0.0 | 937 ms | 0 |
| Wed 23 | 0 | 0.0 | 966 ms | 0 |
| Thu 01 | 0 | 0.0 | 963 ms | 0 |
| Thu 03 | 0 | 0.0 | 1081 ms | 0 |
| Thu 05 | 0 | 0.0 | 999 ms | 0 |
| Thu 07 | 0 | 0.0 | 1091 ms | 0 |
| Thu 09 | 0 | 0.0 | 950 ms | 0 |
| Thu 11 | 0 | 0.0 | 940 ms | 0 |
| Thu 13 | 0 | 0.0 | 1055 ms | 0 |
| Thu 16 | 0 | 0.0 | 1168 ms | 0 |
| Thu 18 | 0 | 0.0 | 1010 ms | 0 |
| Thu 20 | 0 | 0.0 | 971 ms | 0 |
| Thu 22 | 0 | 0.0 | 963 ms | 0 |
| Fri 00 | 0 | 0.0 | 981 ms | 0 |
| Fri 02 | 0 | 0.0 | 975 ms | 0 |
| Fri 04 | 0 | 0.0 | 968 ms | 0 |
| Fri 06 | 0 | 0.0 | 1092 ms | 0 |
| Fri 08 | 0 | 0.0 | 984 ms | 0 |
| Fri 10 | 0 | 0.0 | 955 ms | 0 |
| Fri 12 | 0 | 0.0 | 1034 ms | 0 |
| Fri 14 | 0 | 0.0 | 1019 ms | 0 |
| Fri 16 | 0 | 0.0 | 957 ms | 0 |
| Fri 17 | 0 | 0.0 | 969 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: 992 ms average, 955–1096 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 Rigi incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
992 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.