User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
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 38 min ago. Last stored result reached it in 262 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 12 | 0 | 0.0 | 243 ms | 0 |
| Tue 14 | 0 | 0.0 | 134 ms | 0 |
| Tue 17 | 0 | 0.0 | 149 ms | 0 |
| Tue 19 | 0 | 0.0 | 261 ms | 0 |
| Tue 21 | 0 | 0.0 | 184 ms | 0 |
| Tue 23 | 0 | 0.0 | 366 ms | 0 |
| Wed 02 | 0 | 0.0 | 261 ms | 0 |
| Wed 04 | 0 | 0.0 | 168 ms | 0 |
| Wed 06 | 0 | 0.0 | 263 ms | 0 |
| Wed 08 | 0 | 0.0 | 277 ms | 0 |
| Wed 11 | 0 | 0.0 | 252 ms | 0 |
| Wed 13 | 0 | 0.0 | 404 ms | 0 |
| Wed 15 | 0 | 0.0 | 266 ms | 0 |
| Wed 17 | 0 | 0.0 | 93 ms | 0 |
| Wed 19 | 0 | 0.0 | 383 ms | 0 |
| Wed 21 | 0 | 0.0 | 282 ms | 0 |
| Thu 00 | 0 | 0.0 | 227 ms | 0 |
| Thu 02 | 0 | 0.0 | 360 ms | 0 |
| Thu 04 | 0 | 0.0 | 296 ms | 0 |
| Thu 06 | 0 | 0.0 | 401 ms | 0 |
| Thu 08 | 0 | 0.0 | 217 ms | 0 |
| Thu 10 | 0 | 0.0 | 297 ms | 0 |
| Thu 12 | 0 | 0.0 | 374 ms | 0 |
| Thu 14 | 0 | 0.0 | 330 ms | 0 |
| Thu 16 | 0 | 0.0 | 208 ms | 0 |
| Thu 18 | 0 | 0.0 | 230 ms | 0 |
| Thu 20 | 0 | 0.0 | 185 ms | 0 |
| Thu 22 | 0 | 0.0 | 188 ms | 0 |
| Fri 00 | 0 | 0.0 | 167 ms | 0 |
| Fri 02 | 0 | 0.0 | 242 ms | 0 |
| Fri 04 | 0 | 0.0 | 195 ms | 0 |
| Fri 07 | 0 | 0.0 | 256 ms | 0 |
| Fri 09 | 0 | 0.0 | 277 ms | 0 |
| Fri 10 | 0 | 0.0 | 158 ms | 0 |
| Fri 11 | 0 | 0.0 | 235 ms | 0 |
| Fri 13 | 0 | 0.0 | 420 ms | 0 |
| Fri 15 | 0 | 0.0 | 262 ms | 0 |
| Fri 17 | 0 | 0.0 | 289 ms | 0 |
| Fri 19 | 0 | 0.0 | 284 ms | 0 |
| Fri 21 | 0 | 0.0 | 152 ms | 0 |
| Fri 23 | 0 | 0.0 | 239 ms | 0 |
| Sat 01 | 0 | 0.0 | 185 ms | 0 |
| Sat 03 | 0 | 0.0 | 270 ms | 0 |
| Sat 05 | 0 | 0.0 | 227 ms | 0 |
| Sat 07 | 0 | 0.0 | 157 ms | 0 |
| Sat 09 | 0 | 0.0 | 280 ms | 0 |
| Sat 11 | 0 | 0.0 | 174 ms | 0 |
| Sat 14 | 0 | 0.0 | 262 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 Betty Blocks 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 Betty Blocks goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Betty Blocks alerts to Slack, Discord or a webhook — free.
We track Betty Blocks (bettyblocks.com) as part of the AI group. The AI Application Generation Platform built for digital sovereignty. Generate apps with prompts and own the code, AI, and infrastructure.
Betty Blocks publishes an official status page at status.bettyblocks.com; when we can read it, its incident level is folded into the status shown here.
Common problems for AI services: slow or failed responses, rate-limit errors, and API timeouts.
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: 232 ms average, 152–289 ms range across 12 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Betty Blocks incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
232 ms on average over the last 24 hours (152–289 ms).
Yes, at https://status.bettyblocks.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report Betty Blocks here at once, the problem is on Betty Blocks'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 Betty Blocks. 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.