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 9 min ago. Last stored result reached it in 560 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 00 | 0 | 0.0 | 189 ms | 0 |
| Tue 02 | 0 | 0.0 | 250 ms | 0 |
| Tue 04 | 0 | 0.0 | 301 ms | 0 |
| Tue 06 | 0 | 0.0 | 288 ms | 0 |
| Tue 08 | 0 | 0.0 | 289 ms | 0 |
| Tue 10 | 0 | 0.0 | 476 ms | 0 |
| Tue 12 | 0 | 0.0 | 361 ms | 0 |
| Tue 14 | 0 | 0.0 | 269 ms | 0 |
| Tue 17 | 0 | 0.0 | 529 ms | 0 |
| Tue 19 | 0 | 0.0 | 429 ms | 0 |
| Tue 21 | 0 | 0.0 | 290 ms | 0 |
| Wed 00 | 0 | 0.0 | 470 ms | 0 |
| Wed 02 | 0 | 0.0 | 434 ms | 0 |
| Wed 04 | 0 | 0.0 | 391 ms | 0 |
| Wed 06 | 0 | 0.0 | 471 ms | 0 |
| Wed 08 | 0 | 0.0 | 243 ms | 0 |
| Wed 11 | 0 | 0.0 | 374 ms | 0 |
| Wed 13 | 0 | 0.0 | 346 ms | 0 |
| Wed 15 | 0 | 0.0 | 314 ms | 0 |
| Wed 17 | 0 | 0.0 | 331 ms | 0 |
| Wed 19 | 0 | 0.0 | 236 ms | 0 |
| Wed 21 | 0 | 0.0 | 404 ms | 0 |
| Thu 00 | 0 | 0.0 | 157 ms | 0 |
| Thu 02 | 0 | 0.0 | 436 ms | 0 |
| Thu 04 | 0 | 0.0 | 447 ms | 0 |
| Thu 06 | 0 | 0.0 | 414 ms | 0 |
| Thu 09 | 0 | 0.0 | 489 ms | 0 |
| Thu 11 | 0 | 0.0 | 377 ms | 0 |
| Thu 13 | 0 | 0.0 | 261 ms | 0 |
| Thu 15 | 0 | 0.0 | 275 ms | 0 |
| Thu 17 | 0 | 0.0 | 264 ms | 0 |
| Thu 19 | 0 | 0.0 | 222 ms | 0 |
| Thu 21 | 0 | 0.0 | 342 ms | 0 |
| Thu 23 | 0 | 0.0 | 307 ms | 0 |
| Fri 01 | 0 | 0.0 | 453 ms | 0 |
| Fri 03 | 0 | 0.0 | 266 ms | 0 |
| Fri 05 | 0 | 0.0 | 250 ms | 0 |
| Fri 07 | 0 | 0.0 | 432 ms | 0 |
| Fri 09 | 0 | 0.0 | 545 ms | 0 |
| Fri 10 | 0 | 0.0 | 386 ms | 0 |
| Fri 11 | 0 | 0.0 | 438 ms | 0 |
| Fri 13 | 0 | 0.0 | 398 ms | 0 |
| Fri 14 | 0 | 0.0 | 417 ms | 0 |
| Fri 16 | 0 | 0.0 | 438 ms | 0 |
| Fri 17 | 0 | 0.0 | 573 ms | 0 |
| Fri 18 | 0 | 0.0 | 448 ms | 0 |
| Fri 20 | 0 | 0.0 | 433 ms | 0 |
| Fri 21 | 0 | 0.0 | 560 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 Chatfuel 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 Chatfuel goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Chatfuel alerts to Slack, Discord or a webhook — free.
Chatfuel is listed in our AI category and checked at chatfuel.com. Chatfuel's AI agent replies, qualifies, books, and follows up on WhatsApp, Instagram, and Facebook — automatically. Official Meta Business Partner.
Chatfuel publishes an official status page at status.chatfuel.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with 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: 431 ms average, 250–616 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 Chatfuel incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
431 ms on average over the last 24 hours (250–616 ms).
Yes, at https://status.chatfuel.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 Chatfuel here at once, the problem is on Chatfuel'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 Chatfuel. 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.