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 288 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 23 | 0 | 0.0 | 208 ms | 0 |
| Tue 01 | 0 | 0.0 | 173 ms | 0 |
| Tue 04 | 0 | 0.0 | 257 ms | 0 |
| Tue 06 | 0 | 0.0 | 63 ms | 0 |
| Tue 08 | 0 | 0.0 | 58 ms | 0 |
| Tue 10 | 0 | 0.0 | 69 ms | 0 |
| Tue 12 | 0 | 0.0 | 144 ms | 0 |
| Tue 14 | 0 | 0.0 | 168 ms | 0 |
| Tue 17 | 0 | 0.0 | 287 ms | 0 |
| Tue 19 | 0 | 0.0 | 57 ms | 0 |
| Tue 21 | 0 | 0.0 | 60 ms | 0 |
| Tue 23 | 0 | 0.0 | 185 ms | 0 |
| Wed 01 | 0 | 0.0 | 179 ms | 0 |
| Wed 04 | 0 | 0.0 | 232 ms | 0 |
| Wed 06 | 0 | 0.0 | 45 ms | 0 |
| Wed 08 | 0 | 0.0 | 58 ms | 0 |
| Wed 11 | 0 | 0.0 | 61 ms | 0 |
| Wed 13 | 0 | 0.0 | 89 ms | 0 |
| Wed 15 | 0 | 0.0 | 71 ms | 0 |
| Wed 17 | 0 | 0.0 | 185 ms | 0 |
| Wed 19 | 0 | 0.0 | 237 ms | 0 |
| Wed 21 | 0 | 0.0 | 259 ms | 0 |
| Wed 23 | 0 | 0.0 | 161 ms | 0 |
| Thu 02 | 0 | 0.0 | 148 ms | 0 |
| Thu 04 | 0 | 0.0 | 81 ms | 0 |
| Thu 06 | 0 | 0.0 | 270 ms | 0 |
| Thu 08 | 0 | 0.0 | 257 ms | 0 |
| Thu 10 | 0 | 0.0 | 212 ms | 0 |
| Thu 12 | 0 | 0.0 | 232 ms | 0 |
| Thu 14 | 0 | 0.0 | 175 ms | 0 |
| Thu 16 | 0 | 0.0 | 206 ms | 0 |
| Thu 18 | 0 | 0.0 | 192 ms | 0 |
| Thu 20 | 0 | 0.0 | 300 ms | 0 |
| Thu 22 | 0 | 0.0 | 140 ms | 0 |
| Fri 00 | 0 | 0.0 | 196 ms | 0 |
| Fri 02 | 0 | 0.0 | 216 ms | 0 |
| Fri 04 | 0 | 0.0 | 227 ms | 0 |
| Fri 07 | 0 | 0.0 | 136 ms | 0 |
| Fri 09 | 0 | 0.0 | 192 ms | 0 |
| Fri 11 | 0 | 0.0 | 265 ms | 0 |
| Fri 13 | 0 | 0.0 | 248 ms | 0 |
| Fri 15 | 0 | 0.0 | 156 ms | 0 |
| Fri 17 | 0 | 0.0 | 154 ms | 0 |
| Fri 19 | 0 | 0.0 | 193 ms | 0 |
| Fri 21 | 0 | 0.0 | 68 ms | 0 |
| Fri 23 | 0 | 0.0 | 159 ms | 0 |
| Sat 01 | 0 | 0.0 | 271 ms | 0 |
| Sat 03 | 0 | 0.0 | 288 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 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Reown 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 Reown goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Reown alerts to Slack, Discord or a webhook — free.
We track Reown (reown.com) as part of the Cloud & developer group. Reown provides powerful and performant infrastructure for developing best-in-class blockchain apps.
Reown publishes an official status page at status.reown.com; 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 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 194 ms average, 68–288 ms range across 11 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Reown incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
194 ms on average over the last 24 hours (68–288 ms).
Yes, at https://status.reown.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 Reown here at once, the problem is on Reown'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 Reown. 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.