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 740 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 911 ms | 0 |
| Nov 7 | 0 | 0.0 | 894 ms | 0 |
| Nov 7 | 0 | 0.0 | 903 ms | 0 |
| Nov 7 | 0 | 0.0 | 863 ms | 0 |
| Nov 8 | 0 | 0.0 | 907 ms | 0 |
| Nov 8 | 0 | 0.0 | 808 ms | 0 |
| Nov 8 | 0 | 0.0 | 935 ms | 0 |
| Nov 8 | 0 | 0.0 | 867 ms | 0 |
| Nov 9 | 0 | 0.0 | 889 ms | 0 |
| Nov 9 | 0 | 0.0 | 881 ms | 0 |
| Nov 9 | 0 | 0.0 | 938 ms | 0 |
| Nov 9 | 0 | 0.0 | 904 ms | 0 |
| Nov 10 | 0 | 0.0 | 941 ms | 0 |
| Nov 10 | 0 | 0.0 | 922 ms | 0 |
| Nov 10 | 0 | 0.0 | 872 ms | 0 |
| Nov 10 | 0 | 0.0 | 933 ms | 0 |
| Nov 11 | 0 | 0.0 | 826 ms | 0 |
| Nov 11 | 0 | 0.0 | 935 ms | 0 |
| Nov 11 | 0 | 0.0 | 891 ms | 0 |
| Nov 11 | 0 | 0.0 | 878 ms | 0 |
| Nov 12 | 0 | 0.0 | 888 ms | 0 |
| Nov 12 | 0 | 0.0 | 748 ms | 0 |
| Nov 12 | 0 | 0.0 | 998 ms | 0 |
| Nov 12 | 0 | 0.0 | 935 ms | 0 |
| Nov 13 | 0 | 0.0 | 804 ms | 0 |
| Nov 13 | 0 | 0.0 | 801 ms | 0 |
| Nov 13 | 0 | 0.0 | 847 ms | 0 |
| Nov 13 | 0 | 0.0 | 855 ms | 0 |
| Nov 14 | 0 | 0.0 | 806 ms | 0 |
| Nov 14 | 0 | 0.0 | 710 ms | 0 |
| Nov 14 | 0 | 0.0 | 740 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 Rise Up 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 Rise Up goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Rise Up alerts to Slack, Discord or a webhook — free.
Rise Up, at riseup.ai, is one of the Cloud & developer services we monitor. Passez de la théorie à la pratique grâce à la formation personnalisée et au coaching sur-mesure, enrichis par l’IA, pour un impact métier mesurable.
Rise Up publishes an official status page at status.riseup.ai; 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: 817 ms average, 654–1139 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 Rise Up incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
817 ms on average over the last 24 hours (654–1139 ms).
Yes, at https://status.riseup.ai.
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 Rise Up here at once, the problem is on Rise Up'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 Rise Up. 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.