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 10 min ago. Last stored result reached it in 569 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 7 | 0 | 0.0 | 161 ms | 0 |
| Nov 7 | 0 | 0.0 | 271 ms | 0 |
| Nov 8 | 0 | 0.0 | 305 ms | 0 |
| Nov 8 | 0 | 0.0 | 152 ms | 0 |
| Nov 8 | 0 | 0.0 | 245 ms | 0 |
| Nov 8 | 0 | 0.0 | 231 ms | 0 |
| Nov 9 | 0 | 0.0 | 231 ms | 0 |
| Nov 9 | 0 | 0.0 | 271 ms | 0 |
| Nov 9 | 0 | 0.0 | 258 ms | 0 |
| Nov 9 | 0 | 0.0 | 122 ms | 0 |
| Nov 10 | 0 | 0.0 | 261 ms | 0 |
| Nov 10 | 0 | 0.0 | 211 ms | 0 |
| Nov 10 | 0 | 0.0 | 122 ms | 0 |
| Nov 10 | 0 | 0.0 | 306 ms | 0 |
| Nov 11 | 0 | 0.0 | 291 ms | 0 |
| Nov 11 | 0 | 0.0 | 283 ms | 0 |
| Nov 11 | 0 | 0.0 | 249 ms | 0 |
| Nov 11 | 0 | 0.0 | 184 ms | 0 |
| Nov 12 | 0 | 0.0 | 258 ms | 0 |
| Nov 12 | 0 | 0.0 | 140 ms | 0 |
| Nov 12 | 0 | 0.0 | 186 ms | 0 |
| Nov 12 | 0 | 0.0 | 135 ms | 0 |
| Nov 13 | 0 | 0.0 | 289 ms | 0 |
| Nov 13 | 0 | 0.0 | 158 ms | 0 |
| Nov 13 | 0 | 0.0 | 180 ms | 0 |
| Nov 13 | 0 | 0.0 | 569 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.
No outages on record for Sent 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 Sent goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Sent alerts to Slack, Discord or a webhook — free.
Sent, at sent.dm, is one of the Telecom services we monitor. Sent connects your product to SMS, WhatsApp, and RCS, then handles routing, compliance, formatting, and delivery automatically.
Sent publishes an official status page at status.sent.dm; 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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 212 ms average, 97–569 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 Sent incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
212 ms on average over the last 24 hours (97–569 ms).
Yes, at https://status.sent.dm.
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 Sent here at once, the problem is on Sent'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 Sent. 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.