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 27 min ago. Last stored result reached it in 360 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 21 | 0 | 0.0 | 328 ms | 0 |
| Mon 23 | 0 | 0.0 | 332 ms | 0 |
| Tue 01 | 0 | 0.0 | 341 ms | 0 |
| Tue 04 | 0 | 0.0 | 407 ms | 0 |
| Tue 06 | 0 | 0.0 | 373 ms | 0 |
| Tue 08 | 0 | 0.0 | 394 ms | 0 |
| Tue 10 | 0 | 0.0 | 327 ms | 0 |
| Tue 12 | 0 | 0.0 | 361 ms | 0 |
| Tue 14 | 0 | 0.0 | 361 ms | 0 |
| Tue 17 | 0 | 0.0 | 293 ms | 0 |
| Tue 19 | 0 | 0.0 | 300 ms | 0 |
| Tue 21 | 0 | 0.0 | 403 ms | 0 |
| Tue 23 | 0 | 0.0 | 370 ms | 0 |
| Wed 02 | 0 | 0.0 | 294 ms | 0 |
| Wed 04 | 0 | 0.0 | 309 ms | 0 |
| Wed 06 | 0 | 0.0 | 368 ms | 0 |
| Wed 08 | 0 | 0.0 | 373 ms | 0 |
| Wed 11 | 0 | 0.0 | 331 ms | 0 |
| Wed 13 | 0 | 0.0 | 380 ms | 0 |
| Wed 15 | 0 | 0.0 | 301 ms | 0 |
| Wed 17 | 0 | 0.0 | 312 ms | 0 |
| Wed 19 | 0 | 0.0 | 377 ms | 0 |
| Wed 21 | 0 | 0.0 | 376 ms | 0 |
| Wed 23 | 0 | 0.0 | 408 ms | 0 |
| Thu 02 | 0 | 0.0 | 414 ms | 0 |
| Thu 04 | 0 | 0.0 | 255 ms | 0 |
| Thu 06 | 0 | 0.0 | 337 ms | 0 |
| Thu 08 | 0 | 0.0 | 377 ms | 0 |
| Thu 10 | 0 | 0.0 | 423 ms | 0 |
| Thu 12 | 0 | 0.0 | 244 ms | 0 |
| Thu 14 | 0 | 0.0 | 379 ms | 0 |
| Thu 16 | 0 | 0.0 | 438 ms | 0 |
| Thu 18 | 0 | 0.0 | 365 ms | 0 |
| Thu 20 | 0 | 0.0 | 397 ms | 0 |
| Thu 22 | 0 | 0.0 | 390 ms | 0 |
| Fri 00 | 0 | 0.0 | 348 ms | 0 |
| Fri 02 | 0 | 0.0 | 265 ms | 0 |
| Fri 04 | 0 | 0.0 | 443 ms | 0 |
| Fri 07 | 0 | 0.0 | 355 ms | 0 |
| Fri 09 | 0 | 0.0 | 334 ms | 0 |
| Fri 11 | 0 | 0.0 | 334 ms | 0 |
| Fri 13 | 0 | 0.0 | 289 ms | 0 |
| Fri 15 | 0 | 0.0 | 217 ms | 0 |
| Fri 17 | 0 | 0.0 | 290 ms | 0 |
| Fri 19 | 0 | 0.0 | 365 ms | 0 |
| Fri 21 | 0 | 0.0 | 375 ms | 0 |
| Fri 23 | 0 | 0.0 | 383 ms | 0 |
| Sat 01 | 0 | 0.0 | 360 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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for RWX 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 RWX goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send RWX alerts to Slack, Discord or a webhook — free.
RWX is listed in our Cloud & developer category and checked at rwx.com. RWX is the CI/CD platform for the agentic dev cycle. Validate changes without a commit. Give your agents sandboxes that share your build config and cache.
RWX publishes an official status page at status.rwx.com; 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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 336 ms average, 217–443 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 RWX incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
336 ms on average over the last 24 hours (217–443 ms).
Yes, at https://status.rwx.com.
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 RWX here at once, the problem is on RWX'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 RWX. 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.