User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
rise.trade · 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 262 ms.
All clear
All systems operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 15 | 0 | 0.0 | 308 ms | 0 |
| Tue 17 | 0 | 0.0 | 267 ms | 0 |
| Tue 19 | 0 | 0.0 | 184 ms | 0 |
| Tue 22 | 0 | 0.0 | 1055 ms | 0 |
| Wed 00 | 0 | 0.0 | 340 ms | 0 |
| Wed 02 | 0 | 0.0 | 316 ms | 0 |
| Wed 04 | 0 | 0.0 | 254 ms | 0 |
| Wed 06 | 0 | 0.0 | 232 ms | 0 |
| Wed 09 | 0 | 0.0 | 234 ms | 0 |
| Wed 11 | 0 | 0.0 | 208 ms | 0 |
| Wed 13 | 0 | 0.0 | 367 ms | 0 |
| Wed 15 | 0 | 0.0 | 286 ms | 0 |
| Wed 17 | 0 | 0.0 | 208 ms | 0 |
| Wed 20 | 0 | 0.0 | 242 ms | 0 |
| Wed 22 | 0 | 0.0 | 260 ms | 0 |
| Thu 00 | 0 | 0.0 | 479 ms | 0 |
| Thu 02 | 0 | 0.0 | 310 ms | 0 |
| Thu 04 | 0 | 0.0 | 347 ms | 0 |
| Thu 06 | 0 | 0.0 | 366 ms | 0 |
| Thu 08 | 0 | 0.0 | 215 ms | 0 |
| Thu 10 | 0 | 0.0 | 334 ms | 0 |
| Thu 12 | 0 | 0.0 | 234 ms | 0 |
| Thu 14 | 0 | 0.0 | 223 ms | 0 |
| Thu 17 | 0 | 0.0 | 282 ms | 0 |
| Thu 19 | 0 | 0.0 | 252 ms | 0 |
| Thu 21 | 0 | 0.0 | 321 ms | 0 |
| Thu 23 | 0 | 0.0 | 264 ms | 0 |
| Fri 01 | 0 | 0.0 | 248 ms | 0 |
| Fri 03 | 0 | 0.0 | 267 ms | 0 |
| Fri 05 | 0 | 0.0 | 975 ms | 0 |
| Fri 07 | 0 | 0.0 | 336 ms | 0 |
| Fri 09 | 0 | 0.0 | 289 ms | 0 |
| Fri 10 | 0 | 0.0 | 296 ms | 0 |
| Fri 11 | 0 | 0.0 | 281 ms | 0 |
| Fri 13 | 0 | 0.0 | 309 ms | 0 |
| Fri 15 | 0 | 0.0 | 292 ms | 0 |
| Fri 17 | 0 | 0.0 | 246 ms | 0 |
| Fri 19 | 0 | 0.0 | 236 ms | 0 |
| Fri 20 | 0 | 0.0 | 397 ms | 0 |
| Fri 22 | 0 | 0.0 | 262 ms | 0 |
| Fri 23 | 0 | 0.0 | 240 ms | 0 |
| Sat 01 | 0 | 0.0 | 275 ms | 0 |
| Sat 03 | 0 | 0.0 | 258 ms | 0 |
| Sat 05 | 0 | 0.0 | 309 ms | 0 |
| Sat 07 | 0 | 0.0 | 297 ms | 0 |
| Sat 09 | 0 | 0.0 | 276 ms | 0 |
| Sat 12 | 0 | 0.0 | 1066 ms | 0 |
| Sat 14 | 0 | 0.0 | 262 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 RISEx Mainnet 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 RISEx Mainnet goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send RISEx Mainnet alerts to Slack, Discord or a webhook — free.
We track RISEx Mainnet (rise.trade) as part of the Cloud & developer group. Trade perpetuals on a fully onchain, composable orderbook with 1ms updates. Earn yield on idle collateral. Built on RISE, secured by Ethereum.
RISEx Mainnet publishes an official status page at status.rise.trade; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong 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: 330 ms average, 204–1066 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 RISEx Mainnet incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
330 ms on average over the last 24 hours (204–1066 ms).
Yes, at https://status.rise.trade.
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 RISEx Mainnet here at once, the problem is on RISEx Mainnet'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 RISEx Mainnet. 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.