User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Money
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 31 min ago. Last stored result reached it in 64 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 13 | 0 | 0.0 | 68 ms | 0 |
| Mon 15 | 0 | 0.0 | 135 ms | 0 |
| Mon 18 | 0 | 0.0 | 63 ms | 0 |
| Mon 20 | 0 | 0.0 | 537 ms | 0 |
| Mon 22 | 0 | 0.0 | 148 ms | 0 |
| Tue 00 | 0 | 0.0 | 75 ms | 0 |
| Tue 02 | 0 | 0.0 | 97 ms | 0 |
| Tue 04 | 0 | 0.0 | 75 ms | 0 |
| Tue 06 | 0 | 0.0 | 169 ms | 0 |
| Tue 08 | 0 | 0.0 | 119 ms | 0 |
| Tue 10 | 0 | 0.0 | 106 ms | 0 |
| Tue 13 | 0 | 0.0 | 57 ms | 0 |
| Tue 15 | 0 | 0.0 | 144 ms | 0 |
| Tue 17 | 0 | 0.0 | 109 ms | 0 |
| Tue 19 | 0 | 0.0 | 475 ms | 0 |
| Tue 22 | 0 | 0.0 | 69 ms | 0 |
| Wed 00 | 0 | 0.0 | 103 ms | 0 |
| Wed 02 | 0 | 0.0 | 113 ms | 0 |
| Wed 04 | 0 | 0.0 | 83 ms | 0 |
| Wed 06 | 0 | 0.0 | 67 ms | 0 |
| Wed 09 | 0 | 0.0 | 26 ms | 0 |
| Wed 11 | 0 | 0.0 | 86 ms | 0 |
| Wed 13 | 0 | 0.0 | 81 ms | 0 |
| Wed 15 | 0 | 0.0 | 95 ms | 0 |
| Wed 17 | 0 | 0.0 | 104 ms | 0 |
| Wed 20 | 0 | 0.0 | 37 ms | 0 |
| Wed 22 | 0 | 0.0 | 111 ms | 0 |
| Thu 00 | 0 | 0.0 | 118 ms | 0 |
| Thu 02 | 0 | 0.0 | 45 ms | 0 |
| Thu 04 | 0 | 0.0 | 76 ms | 0 |
| Thu 06 | 0 | 0.0 | 55 ms | 0 |
| Thu 08 | 0 | 0.0 | 167 ms | 0 |
| Thu 10 | 0 | 0.0 | 49 ms | 0 |
| Thu 12 | 0 | 0.0 | 55 ms | 0 |
| Thu 14 | 0 | 0.0 | 144 ms | 0 |
| Thu 16 | 0 | 0.0 | 81 ms | 0 |
| Thu 19 | 0 | 0.0 | 80 ms | 0 |
| Thu 20 | 0 | 0.0 | 37 ms | 0 |
| Thu 22 | 0 | 0.0 | 68 ms | 0 |
| Fri 00 | 0 | 0.0 | 39 ms | 0 |
| Fri 02 | 0 | 0.0 | 81 ms | 0 |
| Fri 04 | 0 | 0.0 | 60 ms | 0 |
| Fri 06 | 0 | 0.0 | 26 ms | 0 |
| Fri 08 | 0 | 0.0 | 96 ms | 0 |
| Fri 10 | 0 | 0.0 | 40 ms | 0 |
| Fri 12 | 0 | 0.0 | 68 ms | 0 |
| Fri 14 | 0 | 0.0 | 32 ms | 0 |
| Fri 16 | 0 | 0.0 | 64 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 Getblock 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 Getblock goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Getblock alerts to Slack, Discord or a webhook — free.
Getblock is listed in our Money category and checked at getblock.io. GetBlock runs RPC nodes, indexed data, and compliance APIs on 130+ blockchains. SOC 2 Type II attested, 99.99% uptime. Free tier, no credit card.
Getblock publishes an official status page at status.getblock.io; when we can read it, its incident level is folded into the status shown here.
Typical issues with money services: login and two-factor problems, payments or transfers failing, and app errors.
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: 61 ms average, 26–110 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 Getblock incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
61 ms on average over the last 24 hours (26–110 ms).
Yes, at https://status.getblock.io.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For money services, watch for login and two-factor problems, payments or transfers failing, and app errors. If many people report Getblock here at once, the problem is on Getblock'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 Getblock. 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.