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 9 min ago. Last stored result reached it in 91 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 20 | 0 | 0.0 | 1662 ms | 0 |
| Mon 22 | 0 | 0.0 | 88 ms | 0 |
| Tue 00 | 0 | 0.0 | 1642 ms | 0 |
| Tue 02 | 0 | 0.0 | 137 ms | 0 |
| Tue 04 | 0 | 0.0 | 99 ms | 0 |
| Tue 07 | 0 | 0.0 | 1460 ms | 0 |
| Tue 09 | 0 | 0.0 | 86 ms | 0 |
| Tue 11 | 0 | 0.0 | 142 ms | 0 |
| Tue 13 | 0 | 0.0 | 54 ms | 0 |
| Tue 15 | 0 | 0.0 | 121 ms | 0 |
| Tue 17 | 0 | 0.0 | 1352 ms | 0 |
| Tue 20 | 0 | 0.0 | 1432 ms | 0 |
| Tue 22 | 0 | 0.0 | 102 ms | 0 |
| Wed 00 | 0 | 0.0 | 148 ms | 0 |
| Wed 02 | 0 | 0.0 | 1007 ms | 0 |
| Wed 05 | 0 | 0.0 | 50 ms | 0 |
| Wed 07 | 0 | 0.0 | 1576 ms | 0 |
| Wed 09 | 0 | 0.0 | 244 ms | 0 |
| Wed 11 | 0 | 0.0 | 72 ms | 0 |
| Wed 13 | 0 | 0.0 | 142 ms | 0 |
| Wed 16 | 0 | 0.0 | 88 ms | 0 |
| Wed 18 | 0 | 0.0 | 95 ms | 0 |
| Wed 20 | 0 | 0.0 | 172 ms | 0 |
| Wed 21 | 0 | 0.0 | 1634 ms | 0 |
| Wed 23 | 0 | 0.0 | 1499 ms | 0 |
| Thu 02 | 0 | 0.0 | 1476 ms | 0 |
| Thu 04 | 0 | 0.0 | 170 ms | 0 |
| Thu 06 | 0 | 0.0 | 69 ms | 0 |
| Thu 08 | 0 | 0.0 | 81 ms | 0 |
| Thu 10 | 0 | 0.0 | 1432 ms | 0 |
| Thu 12 | 0 | 0.0 | 1441 ms | 0 |
| Thu 14 | 0 | 0.0 | 1575 ms | 0 |
| Thu 16 | 0 | 0.0 | 124 ms | 0 |
| Thu 18 | 0 | 0.0 | 133 ms | 0 |
| Thu 20 | 0 | 0.0 | 101 ms | 0 |
| Thu 22 | 0 | 0.0 | 1297 ms | 0 |
| Fri 00 | 0 | 0.0 | 324 ms | 0 |
| Fri 02 | 0 | 0.0 | 124 ms | 0 |
| Fri 03 | 0 | 0.0 | 111 ms | 0 |
| Fri 05 | 0 | 0.0 | 1503 ms | 0 |
| Fri 07 | 0 | 0.0 | 1572 ms | 0 |
| Fri 09 | 0 | 0.0 | 1673 ms | 0 |
| Fri 11 | 0 | 0.0 | 60 ms | 0 |
| Fri 13 | 0 | 0.0 | 722 ms | 0 |
| Fri 15 | 0 | 0.0 | 1603 ms | 0 |
| Fri 17 | 0 | 0.0 | 385 ms | 0 |
| Fri 18 | 0 | 0.0 | 1326 ms | 0 |
| Fri 19 | 0 | 0.0 | 91 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 ClickSend 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 ClickSend goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send ClickSend alerts to Slack, Discord or a webhook — free.
ClickSend, at clicksend.com, is one of the Telecom services we monitor. Communicate with your customers and staff via SMS and MMS with ClickSend. From single to scale by web app, API or integration.
ClickSend publishes an official status page at status.clicksend.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: 709 ms average, 14–1673 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 ClickSend incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
709 ms on average over the last 24 hours (14–1673 ms).
Yes, at https://status.clicksend.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 ClickSend here at once, the problem is on ClickSend'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 ClickSend. 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.