User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
blockdaemon.com · Cloud & developer
The vendor's status page lists scheduled maintenance. Our own checks and user reports have not confirmed a problem. Official status: Service Under Maintenance
Estimated fix: Not enough Blockdaemon history yet; similar Cloud & developer outages lasted 2 h (median, typically 48 min–11 h; 80 outages).
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 20 min ago. Last stored result reached it in 103 ms.
Maintenance
Service Under Maintenance Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 12 | 0 | 0.0 | 42 ms | 0 |
| Mon 14 | 0 | 0.0 | 48 ms | 0 |
| Mon 16 | 0 | 0.0 | 1613 ms | 0 |
| Mon 18 | 0 | 0.0 | 128 ms | 0 |
| Mon 20 | 0 | 0.0 | 84 ms | 0 |
| Mon 22 | 0 | 0.0 | 77 ms | 0 |
| Tue 00 | 0 | 0.0 | 101 ms | 0 |
| Tue 03 | 0 | 0.0 | 196 ms | 0 |
| Tue 05 | 0 | 0.0 | 94 ms | 0 |
| Tue 07 | 0 | 0.0 | 93 ms | 0 |
| Tue 09 | 0 | 0.0 | 53 ms | 0 |
| Tue 11 | 0 | 0.0 | 80 ms | 0 |
| Tue 13 | 0 | 0.0 | 78 ms | 0 |
| Tue 15 | 0 | 0.0 | 122 ms | 0 |
| Tue 18 | 0 | 0.0 | 63 ms | 0 |
| Tue 20 | 0 | 0.0 | 119 ms | 0 |
| Tue 22 | 0 | 0.0 | 48 ms | 0 |
| Wed 00 | 0 | 0.0 | 369 ms | 0 |
| Wed 03 | 0 | 0.0 | 82 ms | 0 |
| Wed 05 | 0 | 0.0 | 33 ms | 0 |
| Wed 07 | 0 | 0.0 | 38 ms | 0 |
| Wed 09 | 0 | 0.0 | 29 ms | 0 |
| Wed 12 | 0 | 0.0 | 48 ms | 0 |
| Wed 14 | 0 | 0.0 | 111 ms | 0 |
| Wed 16 | 0 | 0.0 | 69 ms | 0 |
| Wed 18 | 0 | 0.0 | 59 ms | 0 |
| Wed 20 | 0 | 0.0 | 149 ms | 0 |
| Wed 22 | 0 | 0.0 | 102 ms | 0 |
| Thu 01 | 0 | 0.0 | 37 ms | 0 |
| Thu 03 | 0 | 0.0 | 97 ms | 0 |
| Thu 05 | 0 | 0.0 | 43 ms | 0 |
| Thu 07 | 0 | 0.0 | 78 ms | 0 |
| Thu 09 | 0 | 0.0 | 76 ms | 0 |
| Thu 11 | 0 | 0.0 | 104 ms | 0 |
| Thu 13 | 0 | 0.0 | 84 ms | 0 |
| Thu 15 | 0 | 0.0 | 110 ms | 0 |
| Thu 17 | 0 | 0.0 | 138 ms | 0 |
| Thu 19 | 0 | 0.0 | 42 ms | 0 |
| Thu 21 | 0 | 0.0 | 91 ms | 0 |
| Thu 23 | 0 | 0.0 | 24 ms | 0 |
| Fri 01 | 0 | 0.0 | 98 ms | 0 |
| Fri 03 | 0 | 0.0 | 144 ms | 0 |
| Fri 05 | 0 | 0.0 | 52 ms | 0 |
| Fri 08 | 0 | 0.0 | 77 ms | 0 |
| Fri 10 | 0 | 0.0 | 60 ms | 0 |
| Fri 12 | 0 | 0.0 | 52 ms | 0 |
| Fri 14 | 0 | 0.0 | 85 ms | 0 |
| Fri 16 | 0 | 0.0 | 103 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 Blockdaemon 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 Blockdaemon goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Blockdaemon alerts to Slack, Discord or a webhook — free.
We track Blockdaemon (blockdaemon.com) as part of the Cloud & developer group. Helping financial institutions scale digital ecosystems. Secure, composable infrastructure for tokenization, custody, stablecoins, and yield management.
Blockdaemon publishes an official status page at status.blockdaemon.com; 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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 76 ms average, 17–144 ms range across 13 successful checks.
The vendor's status page lists scheduled maintenance. Our own checks and user reports have not confirmed a problem. Official status: Service Under Maintenance
We have not recorded a public Blockdaemon incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
76 ms on average over the last 24 hours (17–144 ms).
Yes, at https://status.blockdaemon.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 Blockdaemon here at once, the problem is on Blockdaemon'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 Blockdaemon. 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.