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 35 min ago. Last stored result reached it in 102 ms.
All clear
All systems operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 20 | 0 | 0.0 | 209 ms | 0 |
| Mon 22 | 0 | 0.0 | 131 ms | 0 |
| Tue 00 | 0 | 0.0 | 199 ms | 0 |
| Tue 02 | 0 | 0.0 | 201 ms | 0 |
| Tue 04 | 0 | 0.0 | 172 ms | 0 |
| Tue 07 | 0 | 0.0 | 167 ms | 0 |
| Tue 09 | 0 | 0.0 | 76 ms | 0 |
| Tue 11 | 0 | 0.0 | 70 ms | 0 |
| Tue 13 | 0 | 0.0 | 170 ms | 0 |
| Tue 15 | 0 | 0.0 | 178 ms | 0 |
| Tue 17 | 0 | 0.0 | 235 ms | 0 |
| Tue 20 | 0 | 0.0 | 114 ms | 0 |
| Tue 22 | 0 | 0.0 | 216 ms | 0 |
| Wed 00 | 0 | 0.0 | 217 ms | 0 |
| Wed 02 | 0 | 0.0 | 204 ms | 0 |
| Wed 05 | 0 | 0.0 | 235 ms | 0 |
| Wed 07 | 0 | 0.0 | 173 ms | 0 |
| Wed 09 | 0 | 0.0 | 187 ms | 0 |
| Wed 11 | 0 | 0.0 | 233 ms | 0 |
| Wed 13 | 0 | 0.0 | 99 ms | 0 |
| Wed 15 | 0 | 0.0 | 185 ms | 0 |
| Wed 18 | 0 | 0.0 | 200 ms | 0 |
| Wed 20 | 0 | 0.0 | 94 ms | 0 |
| Wed 22 | 0 | 0.0 | 181 ms | 0 |
| Thu 00 | 0 | 0.0 | 90 ms | 0 |
| Thu 02 | 0 | 0.0 | 216 ms | 0 |
| Thu 04 | 0 | 0.0 | 169 ms | 0 |
| Thu 06 | 0 | 0.0 | 231 ms | 0 |
| Thu 08 | 0 | 0.0 | 243 ms | 0 |
| Thu 10 | 0 | 0.0 | 95 ms | 0 |
| Thu 12 | 0 | 0.0 | 185 ms | 0 |
| Thu 15 | 0 | 0.0 | 215 ms | 0 |
| Thu 17 | 0 | 0.0 | 211 ms | 0 |
| Thu 19 | 0 | 0.0 | 182 ms | 0 |
| Thu 21 | 0 | 0.0 | 326 ms | 0 |
| Thu 23 | 0 | 0.0 | 73 ms | 0 |
| Fri 01 | 0 | 0.0 | 86 ms | 0 |
| Fri 03 | 0 | 0.0 | 219 ms | 0 |
| Fri 05 | 0 | 0.0 | 294 ms | 0 |
| Fri 07 | 0 | 0.0 | 158 ms | 0 |
| Fri 09 | 0 | 0.0 | 242 ms | 0 |
| Fri 10 | 0 | 0.0 | 167 ms | 0 |
| Fri 12 | 0 | 0.0 | 114 ms | 0 |
| Fri 14 | 0 | 0.0 | 161 ms | 0 |
| Fri 16 | 0 | 0.0 | 255 ms | 0 |
| Fri 17 | 0 | 0.0 | 158 ms | 0 |
| Fri 19 | 0 | 0.0 | 106 ms | 0 |
| Fri 21 | 0 | 0.0 | 102 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 1RPC 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 1RPC goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send 1RPC alerts to Slack, Discord or a webhook — free.
We track 1RPC (1rpc.io) as part of the Cloud & developer group. Protect your privacy with TEE-attested relays that erase metadata and verify AI execution across supported networks.
1RPC publishes an official status page at status.1rpc.io; 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: 160 ms average, 73–294 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 1RPC incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
160 ms on average over the last 24 hours (73–294 ms).
Yes, at https://status.1rpc.io.
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 1RPC here at once, the problem is on 1RPC'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 1RPC. 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.