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 41 min ago. Last stored result reached it in 375 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 | 383 ms | 0 |
| Tue 10 | 0 | 0.0 | 409 ms | 0 |
| Tue 12 | 0 | 0.0 | 378 ms | 0 |
| Tue 14 | 0 | 0.0 | 349 ms | 0 |
| Tue 17 | 0 | 0.0 | 249 ms | 0 |
| Tue 19 | 0 | 0.0 | 354 ms | 0 |
| Tue 21 | 0 | 0.0 | 446 ms | 0 |
| Tue 23 | 0 | 0.0 | 423 ms | 0 |
| Wed 02 | 0 | 0.0 | 299 ms | 0 |
| Wed 04 | 0 | 0.0 | 265 ms | 0 |
| Wed 06 | 0 | 0.0 | 352 ms | 0 |
| Wed 08 | 0 | 0.0 | 285 ms | 0 |
| Wed 11 | 0 | 0.0 | 485 ms | 0 |
| Wed 13 | 0 | 0.0 | 400 ms | 0 |
| Wed 15 | 0 | 0.0 | 380 ms | 0 |
| Wed 17 | 0 | 0.0 | 382 ms | 0 |
| Wed 19 | 0 | 0.0 | 406 ms | 0 |
| Wed 21 | 0 | 0.0 | 394 ms | 0 |
| Wed 23 | 0 | 0.0 | 375 ms | 0 |
| Thu 02 | 0 | 0.0 | 423 ms | 0 |
| Thu 04 | 0 | 0.0 | 300 ms | 0 |
| Thu 06 | 0 | 0.0 | 249 ms | 0 |
| Thu 08 | 0 | 0.0 | 330 ms | 0 |
| Thu 10 | 0 | 0.0 | 392 ms | 0 |
| Thu 12 | 0 | 0.0 | 411 ms | 0 |
| Thu 14 | 0 | 0.0 | 391 ms | 0 |
| Thu 16 | 0 | 0.0 | 373 ms | 0 |
| Thu 18 | 0 | 0.0 | 343 ms | 0 |
| Thu 20 | 0 | 0.0 | 371 ms | 0 |
| Thu 22 | 0 | 0.0 | 298 ms | 0 |
| Fri 00 | 0 | 0.0 | 235 ms | 0 |
| Fri 02 | 0 | 0.0 | 398 ms | 0 |
| Fri 04 | 0 | 0.0 | 389 ms | 0 |
| Fri 06 | 0 | 0.0 | 384 ms | 0 |
| Fri 08 | 0 | 0.0 | 359 ms | 0 |
| Fri 11 | 0 | 0.0 | 390 ms | 0 |
| Fri 13 | 0 | 0.0 | 411 ms | 0 |
| Fri 15 | 0 | 0.0 | 385 ms | 0 |
| Fri 17 | 0 | 0.0 | 267 ms | 0 |
| Fri 19 | 0 | 0.0 | 286 ms | 0 |
| Fri 21 | 0 | 0.0 | 389 ms | 0 |
| Fri 23 | 0 | 0.0 | 292 ms | 0 |
| Sat 00 | 0 | 0.0 | 184 ms | 0 |
| Sat 02 | 0 | 0.0 | 399 ms | 0 |
| Sat 04 | 0 | 0.0 | 329 ms | 0 |
| Sat 06 | 0 | 0.0 | 385 ms | 0 |
| Sat 07 | 0 | 0.0 | 295 ms | 0 |
| Sat 08 | 0 | 0.0 | 375 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 AiSensy 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 AiSensy goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send AiSensy alerts to Slack, Discord or a webhook — free.
We track AiSensy (aisensy.com) as part of the AI group. AiSensy is the AI-first WhatsApp Marketing Platform built on official WhatsApp Business APIs. Broadcast offers, automate notifications & solve for support.
AiSensy publishes an official status page at status.aisensy.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 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 337 ms average, 184–411 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public AiSensy incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
337 ms on average over the last 24 hours (184–411 ms).
Yes, at https://status.aisensy.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 AiSensy here at once, the problem is on AiSensy'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 AiSensy. 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.