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 28 min ago. Last stored result reached it in 292 ms.
All clear
All systems operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 17 | 0 | 0.0 | 320 ms | 0 |
| Mon 19 | 0 | 0.0 | 273 ms | 0 |
| Mon 21 | 0 | 0.0 | 371 ms | 0 |
| Tue 00 | 0 | 0.0 | 334 ms | 0 |
| Tue 02 | 0 | 0.0 | 329 ms | 0 |
| Tue 04 | 0 | 0.0 | 417 ms | 0 |
| Tue 06 | 0 | 0.0 | 390 ms | 0 |
| Tue 08 | 0 | 0.0 | 414 ms | 0 |
| Tue 10 | 0 | 0.0 | 309 ms | 0 |
| Tue 12 | 0 | 0.0 | 369 ms | 0 |
| Tue 14 | 0 | 0.0 | 284 ms | 0 |
| Tue 17 | 0 | 0.0 | 268 ms | 0 |
| Tue 19 | 0 | 0.0 | 424 ms | 0 |
| Tue 21 | 0 | 0.0 | 369 ms | 0 |
| Tue 23 | 0 | 0.0 | 379 ms | 0 |
| Wed 02 | 0 | 0.0 | 390 ms | 0 |
| Wed 04 | 0 | 0.0 | 330 ms | 0 |
| Wed 06 | 0 | 0.0 | 421 ms | 0 |
| Wed 08 | 0 | 0.0 | 352 ms | 0 |
| Wed 11 | 0 | 0.0 | 521 ms | 0 |
| Wed 13 | 0 | 0.0 | 427 ms | 0 |
| Wed 15 | 0 | 0.0 | 396 ms | 0 |
| Wed 17 | 0 | 0.0 | 318 ms | 0 |
| Wed 19 | 0 | 0.0 | 452 ms | 0 |
| Wed 21 | 0 | 0.0 | 469 ms | 0 |
| Thu 00 | 0 | 0.0 | 406 ms | 0 |
| Thu 02 | 0 | 0.0 | 496 ms | 0 |
| Thu 04 | 0 | 0.0 | 385 ms | 0 |
| Thu 06 | 0 | 0.0 | 380 ms | 0 |
| Thu 08 | 0 | 0.0 | 382 ms | 0 |
| Thu 10 | 0 | 0.0 | 373 ms | 0 |
| Thu 12 | 0 | 0.0 | 420 ms | 0 |
| Thu 14 | 0 | 0.0 | 380 ms | 0 |
| Thu 16 | 0 | 0.0 | 354 ms | 0 |
| Thu 18 | 0 | 0.0 | 615 ms | 0 |
| Thu 20 | 0 | 0.0 | 325 ms | 0 |
| Thu 22 | 0 | 0.0 | 259 ms | 0 |
| Fri 00 | 0 | 0.0 | 408 ms | 0 |
| Fri 02 | 0 | 0.0 | 350 ms | 0 |
| Fri 04 | 0 | 0.0 | 400 ms | 0 |
| Fri 07 | 0 | 0.0 | 286 ms | 0 |
| Fri 09 | 0 | 0.0 | 278 ms | 0 |
| Fri 11 | 0 | 0.0 | 326 ms | 0 |
| Fri 13 | 0 | 0.0 | 365 ms | 0 |
| Fri 15 | 0 | 0.0 | 334 ms | 0 |
| Fri 17 | 0 | 0.0 | 335 ms | 0 |
| Fri 19 | 0 | 0.0 | 339 ms | 0 |
| Fri 21 | 0 | 0.0 | 282 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 Betterfly 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 Betterfly goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Betterfly alerts to Slack, Discord or a webhook — free.
We track Betterfly (betterfly.com) as part of the AI group. The AI-powered platform where benefits, prevention, and rewards work as one. Book a demo.
Betterfly publishes an official status page at status.betterfly.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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 333 ms average, 259–440 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Betterfly incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
333 ms on average over the last 24 hours (259–440 ms).
Yes, at https://status.betterfly.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 Betterfly here at once, the problem is on Betterfly'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 Betterfly. 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.