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 2 hr ago. Last stored result reached it in 256 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 08 | 0 | 0.0 | 269 ms | 0 |
| Tue 10 | 0 | 0.0 | 482 ms | 0 |
| Tue 12 | 0 | 0.0 | 298 ms | 0 |
| Tue 14 | 0 | 0.0 | 259 ms | 0 |
| Tue 17 | 0 | 0.0 | 537 ms | 0 |
| Tue 19 | 0 | 0.0 | 461 ms | 0 |
| Tue 21 | 0 | 0.0 | 105 ms | 0 |
| Tue 23 | 0 | 0.0 | 266 ms | 0 |
| Wed 02 | 0 | 0.0 | 281 ms | 0 |
| Wed 04 | 0 | 0.0 | 345 ms | 0 |
| Wed 06 | 0 | 0.0 | 376 ms | 0 |
| Wed 08 | 0 | 0.0 | 568 ms | 0 |
| Wed 11 | 0 | 0.0 | 360 ms | 0 |
| Wed 13 | 0 | 0.0 | 250 ms | 0 |
| Wed 15 | 0 | 0.0 | 416 ms | 0 |
| Wed 17 | 0 | 0.0 | 156 ms | 0 |
| Wed 19 | 0 | 0.0 | 298 ms | 0 |
| Wed 22 | 0 | 0.0 | 415 ms | 0 |
| Thu 00 | 0 | 0.0 | 116 ms | 0 |
| Thu 02 | 0 | 0.0 | 280 ms | 0 |
| Thu 04 | 0 | 0.0 | 276 ms | 0 |
| Thu 06 | 0 | 0.0 | 526 ms | 0 |
| Thu 08 | 0 | 0.0 | 383 ms | 0 |
| Thu 10 | 0 | 0.0 | 381 ms | 0 |
| Thu 12 | 0 | 0.0 | 372 ms | 0 |
| Thu 14 | 0 | 0.0 | 441 ms | 0 |
| Thu 16 | 0 | 0.0 | 504 ms | 0 |
| Thu 18 | 0 | 0.0 | 256 ms | 0 |
| Thu 20 | 0 | 0.0 | 305 ms | 0 |
| Thu 22 | 0 | 0.0 | 527 ms | 0 |
| Thu 23 | 0 | 0.0 | 338 ms | 0 |
| Fri 01 | 0 | 0.0 | 382 ms | 0 |
| Fri 04 | 0 | 0.0 | 311 ms | 0 |
| Fri 06 | 0 | 0.0 | 410 ms | 0 |
| Fri 08 | 0 | 0.0 | 453 ms | 0 |
| Fri 10 | 0 | 0.0 | 135 ms | 0 |
| Fri 11 | 0 | 0.0 | 258 ms | 0 |
| Fri 13 | 0 | 0.0 | 522 ms | 0 |
| Fri 15 | 0 | 0.0 | 214 ms | 0 |
| Fri 17 | 0 | 0.0 | 263 ms | 0 |
| Fri 19 | 0 | 0.0 | 208 ms | 0 |
| Fri 21 | 0 | 0.0 | 430 ms | 0 |
| Fri 23 | 0 | 0.0 | 169 ms | 0 |
| Sat 00 | 0 | 0.0 | 147 ms | 0 |
| Sat 02 | 0 | 0.0 | 300 ms | 0 |
| Sat 04 | 0 | 0.0 | 127 ms | 0 |
| Sat 05 | 0 | 0.0 | 323 ms | 0 |
| Sat 08 | 0 | 0.0 | 256 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 Blink.new 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 Blink.new goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Blink.new alerts to Slack, Discord or a webhook — free.
Blink.new is listed in our AI category and checked at blink.new. Build and host studio-quality business websites with AI — custom domain, hosting, and SEO included. The same prompt ships full-stack web and mobile apps.
Blink.new publishes an official status page at status.blink.new; when we can read it, its incident level is folded into the status shown here.
Typical issues with AI services: slow or failed responses, rate-limit errors, and API timeouts.
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: 240 ms average, 49–522 ms range across 17 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Blink.new incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
240 ms on average over the last 24 hours (49–522 ms).
Yes, at https://status.blink.new.
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 Blink.new here at once, the problem is on Blink.new'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 Blink.new. 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.