User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: No new inbound email | No user login activity detected. Our team is investigating | Potential issue with Pipeline creation. | No new inbound Facebook messages | No new outbound ...
Source: the vendor's status page · We are not affiliated with WooSender.
Estimated fix: Not enough WooSender history yet; similar AI outages lasted 27 min (median, typically 9 min–2 h; 41 outages).
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 228 ms.
Critical incident
No new inbound email | No user login activity detected. Our team is investigating | Potential issue with Pipeline creation. | No new inbound Facebook messages | No new outbound Facebook messages | No new inbound live chat | No appointment sync detected | No appointment sync detected | No new campaig Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 16 | 0 | 0.0 | 199 ms | 0 |
| Mon 18 | 0 | 0.0 | 346 ms | 0 |
| Mon 20 | 0 | 0.0 | 304 ms | 0 |
| Mon 22 | 0 | 0.0 | 248 ms | 0 |
| Tue 00 | 0 | 0.0 | 353 ms | 0 |
| Tue 03 | 0 | 0.0 | 298 ms | 0 |
| Tue 05 | 0 | 0.0 | 253 ms | 0 |
| Tue 07 | 0 | 0.0 | 272 ms | 0 |
| Tue 09 | 0 | 0.0 | 248 ms | 0 |
| Tue 11 | 0 | 0.0 | 229 ms | 0 |
| Tue 13 | 0 | 0.0 | 330 ms | 0 |
| Tue 16 | 0 | 0.0 | 304 ms | 0 |
| Tue 18 | 0 | 0.0 | 306 ms | 0 |
| Tue 20 | 0 | 0.0 | 286 ms | 0 |
| Tue 22 | 0 | 0.0 | 287 ms | 0 |
| Wed 01 | 0 | 0.0 | 295 ms | 0 |
| Wed 03 | 0 | 0.0 | 247 ms | 0 |
| Wed 05 | 0 | 0.0 | 276 ms | 0 |
| Wed 07 | 0 | 0.0 | 176 ms | 0 |
| Wed 10 | 0 | 0.0 | 207 ms | 0 |
| Wed 11 | 0 | 0.0 | 290 ms | 0 |
| Wed 13 | 0 | 0.0 | 280 ms | 0 |
| Wed 15 | 0 | 0.0 | 281 ms | 0 |
| Wed 17 | 0 | 0.0 | 257 ms | 0 |
| Wed 20 | 0 | 0.0 | 262 ms | 0 |
| Wed 22 | 0 | 0.0 | 60 ms | 0 |
| Thu 00 | 0 | 0.0 | 211 ms | 0 |
| Thu 02 | 0 | 0.0 | 295 ms | 0 |
| Thu 04 | 0 | 0.0 | 343 ms | 0 |
| Thu 06 | 0 | 0.0 | 296 ms | 0 |
| Thu 08 | 0 | 0.0 | 325 ms | 0 |
| Thu 10 | 0 | 0.0 | 231 ms | 0 |
| Thu 12 | 0 | 0.0 | 311 ms | 0 |
| Thu 15 | 0 | 0.0 | 291 ms | 0 |
| Thu 17 | 0 | 0.0 | 229 ms | 0 |
| Thu 19 | 0 | 0.0 | 290 ms | 0 |
| Thu 21 | 0 | 0.0 | 270 ms | 0 |
| Thu 23 | 0 | 0.0 | 366 ms | 0 |
| Fri 01 | 0 | 0.0 | 278 ms | 0 |
| Fri 03 | 0 | 0.0 | 347 ms | 0 |
| Fri 05 | 0 | 0.0 | 279 ms | 0 |
| Fri 06 | 0 | 0.0 | 293 ms | 0 |
| Fri 08 | 0 | 0.0 | 177 ms | 0 |
| Fri 09 | 0 | 0.0 | 178 ms | 0 |
| Fri 11 | 0 | 0.0 | 267 ms | 0 |
| Fri 13 | 0 | 0.0 | 317 ms | 0 |
| Fri 15 | 0 | 0.0 | 333 ms | 0 |
| Fri 17 | 0 | 0.0 | 228 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.
One report per service every 10 minutes from this network. No account.
Get an email when WooSender goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send WooSender alerts to Slack, Discord or a webhook — free.
We track WooSender (woosender.com) as part of the AI group. Replace your SDRs with WooSender. The autonomous AI Sales Agent and Automated Appointment Setter that books leads directly into your calendar.
WooSender publishes an official status page at status.woosender.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. We logged 1 public incident since monitoring began 7 days ago.
Response time over the last 24 hours: 279 ms average, 177–366 ms range across 13 successful checks.
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: No new inbound email | No user login activity detected. Our team is investigating | Potential issue with Pipeline creation. | No new inbound Facebook messages | No new outbound ...
The most recent public incident we recorded started 2026-11-07 and lasted 3 days 0 h. 1 incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
279 ms on average over the last 24 hours (177–366 ms).
Yes, at https://status.woosender.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 WooSender here at once, the problem is on WooSender'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 WooSender. 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.