User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Telecom
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 1 hr ago. Last stored result reached it in 1636 ms.
All clear
All systems operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 17 | 0 | 0.0 | 1530 ms | 0 |
| Mon 20 | 0 | 0.0 | 1584 ms | 0 |
| Mon 22 | 0 | 0.0 | 1343 ms | 0 |
| Tue 00 | 0 | 0.0 | 1575 ms | 0 |
| Tue 02 | 0 | 0.0 | 1448 ms | 0 |
| Tue 04 | 0 | 0.0 | 1159 ms | 0 |
| Tue 06 | 0 | 0.0 | 1473 ms | 0 |
| Tue 08 | 0 | 0.0 | 1430 ms | 0 |
| Tue 10 | 0 | 0.0 | 1559 ms | 0 |
| Tue 12 | 0 | 0.0 | 1429 ms | 0 |
| Tue 15 | 0 | 0.0 | 1431 ms | 0 |
| Tue 17 | 0 | 0.0 | 1503 ms | 0 |
| Tue 19 | 0 | 0.0 | 1500 ms | 0 |
| Tue 22 | 0 | 0.0 | 1492 ms | 0 |
| Tue 23 | 0 | 0.0 | 1402 ms | 0 |
| Wed 00 | 0 | 0.0 | 1495 ms | 0 |
| Wed 02 | 0 | 0.0 | 1561 ms | 0 |
| Wed 04 | 0 | 0.0 | 1569 ms | 0 |
| Wed 06 | 0 | 0.0 | 1400 ms | 0 |
| Wed 09 | 0 | 0.0 | 1562 ms | 0 |
| Wed 11 | 0 | 0.0 | 1433 ms | 0 |
| Wed 13 | 0 | 0.0 | 1585 ms | 0 |
| Wed 15 | 0 | 0.0 | 1550 ms | 0 |
| Wed 17 | 0 | 0.0 | 1476 ms | 0 |
| Wed 20 | 0 | 0.0 | 1285 ms | 0 |
| Wed 22 | 0 | 0.0 | 1504 ms | 0 |
| Thu 00 | 0 | 0.0 | 1320 ms | 0 |
| Thu 02 | 0 | 0.0 | 1599 ms | 0 |
| Thu 04 | 0 | 0.0 | 1605 ms | 0 |
| Thu 06 | 0 | 0.0 | 1353 ms | 0 |
| Thu 08 | 0 | 0.0 | 1465 ms | 0 |
| Thu 10 | 0 | 0.0 | 1462 ms | 0 |
| Thu 12 | 0 | 0.0 | 1606 ms | 0 |
| Thu 15 | 0 | 0.0 | 1604 ms | 0 |
| Thu 17 | 0 | 0.0 | 1543 ms | 0 |
| Thu 19 | 0 | 0.0 | 1538 ms | 0 |
| Thu 21 | 0 | 0.0 | 1435 ms | 0 |
| Thu 22 | 0 | 0.0 | 1473 ms | 0 |
| Fri 00 | 0 | 0.0 | 1504 ms | 0 |
| Fri 02 | 0 | 0.0 | 1429 ms | 0 |
| Fri 04 | 0 | 0.0 | 1223 ms | 0 |
| Fri 06 | 0 | 0.0 | 1515 ms | 0 |
| Fri 08 | 0 | 0.0 | 1375 ms | 0 |
| Fri 10 | 0 | 0.0 | 1542 ms | 0 |
| Fri 12 | 0 | 0.0 | 1516 ms | 0 |
| Fri 14 | 0 | 0.0 | 1469 ms | 0 |
| Fri 16 | 0 | 0.0 | 1520 ms | 0 |
| Fri 17 | 0 | 0.0 | 1558 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 SendPulse 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 SendPulse goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send SendPulse alerts to Slack, Discord or a webhook — free.
SendPulse is listed in our Telecom category and checked at sendpulse.com. Multi-channel marketing automation platform with email, web push, SMS, and chatbots for Facebook, Telegram, WhatsApp, and Instagram — all combined in a free C
SendPulse publishes an official status page at status.sendpulse.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with telecom services: no service or data, account and billing pages failing, and app sign-in problems.
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: 1458 ms average, 930–1636 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 SendPulse incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
1458 ms on average over the last 24 hours (930–1636 ms).
Yes, at https://status.sendpulse.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For telecom services, watch for no service or data, account and billing pages failing, and app sign-in problems. If many people report SendPulse here at once, the problem is on SendPulse'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 SendPulse. 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.