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 24 min ago. Last stored result reached it in 1346 ms.
All clear
All systems operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 1564 ms | 0 |
| Nov 7 | 0 | 0.0 | 1538 ms | 0 |
| Nov 7 | 0 | 0.0 | 1513 ms | 0 |
| Nov 7 | 0 | 0.0 | 1541 ms | 0 |
| Nov 7 | 0 | 0.0 | 1299 ms | 0 |
| Nov 8 | 0 | 0.0 | 1403 ms | 0 |
| Nov 8 | 0 | 0.0 | 1461 ms | 0 |
| Nov 8 | 0 | 0.0 | 1538 ms | 0 |
| Nov 8 | 0 | 0.0 | 1540 ms | 0 |
| Nov 9 | 0 | 0.0 | 1482 ms | 0 |
| Nov 9 | 0 | 0.0 | 1440 ms | 0 |
| Nov 9 | 0 | 0.0 | 1473 ms | 0 |
| Nov 9 | 0 | 0.0 | 1464 ms | 0 |
| Nov 10 | 0 | 0.0 | 1443 ms | 0 |
| Nov 10 | 0 | 0.0 | 1473 ms | 0 |
| Nov 10 | 0 | 0.0 | 1431 ms | 0 |
| Nov 10 | 0 | 0.0 | 1492 ms | 0 |
| Nov 11 | 0 | 0.0 | 1561 ms | 0 |
| Nov 11 | 0 | 0.0 | 1433 ms | 0 |
| Nov 11 | 0 | 0.0 | 1550 ms | 0 |
| Nov 11 | 0 | 0.0 | 1395 ms | 0 |
| Nov 12 | 0 | 0.0 | 1602 ms | 0 |
| Nov 12 | 0 | 0.0 | 1462 ms | 0 |
| Nov 12 | 0 | 0.0 | 1604 ms | 0 |
| Nov 12 | 0 | 0.0 | 1473 ms | 0 |
| Nov 13 | 0 | 0.0 | 1467 ms | 0 |
| Nov 13 | 0 | 0.0 | 1515 ms | 0 |
| Nov 13 | 0 | 0.0 | 1516 ms | 0 |
| Nov 13 | 0 | 0.0 | 1346 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: 1446 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.
1446 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.