User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Telecom
Is Sent down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → sent.dm—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 1 hr ago. Last stored result reached it in 121 ms.
Official status
All clear
No active incidents in the official feed Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 14 | 0 | 0.0 | 428 ms | 0 |
| Mon 16 | 0 | 0.0 | 258 ms | 0 |
| Mon 18 | 0 | 0.0 | 122 ms | 0 |
| Mon 20 | 0 | 0.0 | 102 ms | 0 |
| Mon 22 | 0 | 0.0 | 163 ms | 0 |
| Tue 00 | 0 | 0.0 | 261 ms | 0 |
| Tue 03 | 0 | 0.0 | 106 ms | 0 |
| Tue 05 | 0 | 0.0 | 640 ms | 0 |
| Tue 07 | 0 | 0.0 | 254 ms | 0 |
| Tue 09 | 0 | 0.0 | 167 ms | 0 |
| Tue 11 | 0 | 0.0 | 205 ms | 0 |
| Tue 13 | 0 | 0.0 | 157 ms | 0 |
| Tue 15 | 0 | 0.0 | 109 ms | 0 |
| Tue 18 | 0 | 0.0 | 306 ms | 0 |
| Tue 20 | 0 | 0.0 | 144 ms | 0 |
| Tue 22 | 0 | 0.0 | 334 ms | 0 |
| Wed 00 | 0 | 0.0 | 133 ms | 0 |
| Wed 03 | 0 | 0.0 | 291 ms | 0 |
| Wed 05 | 0 | 0.0 | 293 ms | 0 |
| Wed 07 | 0 | 0.0 | 294 ms | 0 |
| Wed 09 | 0 | 0.0 | 271 ms | 0 |
| Wed 12 | 0 | 0.0 | 249 ms | 0 |
| Wed 14 | 0 | 0.0 | 335 ms | 0 |
| Wed 16 | 0 | 0.0 | 103 ms | 0 |
| Wed 18 | 0 | 0.0 | 111 ms | 0 |
| Wed 20 | 0 | 0.0 | 184 ms | 0 |
| Wed 22 | 0 | 0.0 | 253 ms | 0 |
| Thu 01 | 0 | 0.0 | 194 ms | 0 |
| Thu 03 | 0 | 0.0 | 154 ms | 0 |
| Thu 05 | 0 | 0.0 | 259 ms | 0 |
| Thu 07 | 0 | 0.0 | 158 ms | 0 |
| Thu 09 | 0 | 0.0 | 140 ms | 0 |
| Thu 11 | 0 | 0.0 | 127 ms | 0 |
| Thu 14 | 0 | 0.0 | 223 ms | 0 |
| Thu 16 | 0 | 0.0 | 148 ms | 0 |
| Thu 18 | 0 | 0.0 | 152 ms | 0 |
| Thu 20 | 0 | 0.0 | 106 ms | 0 |
| Thu 22 | 0 | 0.0 | 165 ms | 0 |
| Fri 00 | 0 | 0.0 | 334 ms | 0 |
| Fri 02 | 0 | 0.0 | 289 ms | 0 |
| Fri 04 | 0 | 0.0 | 181 ms | 0 |
| Fri 06 | 0 | 0.0 | 202 ms | 0 |
| Fri 08 | 0 | 0.0 | 113 ms | 0 |
| Fri 10 | 0 | 0.0 | 220 ms | 0 |
| Fri 11 | 0 | 0.0 | 113 ms | 0 |
| Fri 12 | 0 | 0.0 | 97 ms | 0 |
| Fri 14 | 0 | 0.0 | 272 ms | 0 |
| Fri 16 | 0 | 0.0 | 121 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
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.
Embed this status: free live Sent badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Sent yet. Outages of 10 minutes or more get their own page here.
Having trouble with Sent?
One report per service every 10 minutes from this network. No account.
Follow Sent
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.
About Sent
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: 181 ms average, 97–334 ms range across 14 successful checks.
Questions
Is Sent down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Sent last down?
We have not recorded a public Sent incident since monitoring began 7 days ago.
What is Sent's uptime?
From our own checks: 100% over 7 days of checks.
How fast does Sent respond?
181 ms on average over the last 24 hours (97–334 ms).
Does Sent have an official status page?
Yes, at https://status.sent.dm.
Sent not working for me but the status is fine. What now?
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.