User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
textus.com · Cloud & developer
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 32 min ago. Last stored result reached it in 157 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 14 | 0 | 0.0 | 121 ms | 0 |
| Mon 16 | 0 | 0.0 | 127 ms | 0 |
| Mon 18 | 0 | 0.0 | 59 ms | 0 |
| Mon 20 | 0 | 0.0 | 82 ms | 0 |
| Mon 23 | 0 | 0.0 | 79 ms | 0 |
| Tue 01 | 0 | 0.0 | 148 ms | 0 |
| Tue 03 | 0 | 0.0 | 155 ms | 0 |
| Tue 05 | 0 | 0.0 | 107 ms | 0 |
| Tue 07 | 0 | 0.0 | 108 ms | 0 |
| Tue 09 | 0 | 0.0 | 167 ms | 0 |
| Tue 11 | 0 | 0.0 | 147 ms | 0 |
| Tue 13 | 0 | 0.0 | 359 ms | 0 |
| Tue 16 | 0 | 0.0 | 41 ms | 0 |
| Tue 18 | 0 | 0.0 | 170 ms | 0 |
| Tue 20 | 0 | 0.0 | 182 ms | 0 |
| Tue 23 | 0 | 0.0 | 112 ms | 0 |
| Wed 01 | 0 | 0.0 | 146 ms | 0 |
| Wed 03 | 0 | 0.0 | 230 ms | 0 |
| Wed 05 | 0 | 0.0 | 194 ms | 0 |
| Wed 07 | 0 | 0.0 | 146 ms | 0 |
| Wed 08 | 0 | 0.0 | 206 ms | 0 |
| Wed 10 | 0 | 0.0 | 90 ms | 0 |
| Wed 12 | 0 | 0.0 | 173 ms | 0 |
| Wed 14 | 0 | 0.0 | 83 ms | 0 |
| Wed 16 | 0 | 0.0 | 62 ms | 0 |
| Wed 18 | 0 | 0.0 | 59 ms | 0 |
| Wed 21 | 0 | 0.0 | 126 ms | 0 |
| Wed 23 | 0 | 0.0 | 118 ms | 0 |
| Thu 01 | 0 | 0.0 | 279 ms | 0 |
| Thu 03 | 0 | 0.0 | 114 ms | 0 |
| Thu 05 | 0 | 0.0 | 151 ms | 0 |
| Thu 07 | 0 | 0.0 | 65 ms | 0 |
| Thu 09 | 0 | 0.0 | 114 ms | 0 |
| Thu 11 | 0 | 0.0 | 57 ms | 0 |
| Thu 13 | 0 | 0.0 | 72 ms | 0 |
| Thu 15 | 0 | 0.0 | 105 ms | 0 |
| Thu 18 | 0 | 0.0 | 181 ms | 0 |
| Thu 20 | 0 | 0.0 | 113 ms | 0 |
| Thu 22 | 0 | 0.0 | 53 ms | 0 |
| Fri 00 | 0 | 0.0 | 119 ms | 0 |
| Fri 02 | 0 | 0.0 | 145 ms | 0 |
| Fri 04 | 0 | 0.0 | 127 ms | 0 |
| Fri 06 | 0 | 0.0 | 26 ms | 0 |
| Fri 08 | 0 | 0.0 | 91 ms | 0 |
| Fri 10 | 0 | 0.0 | 72 ms | 0 |
| Fri 12 | 0 | 0.0 | 133 ms | 0 |
| Fri 14 | 0 | 0.0 | 136 ms | 0 |
| Fri 16 | 0 | 0.0 | 157 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 TextUs 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 TextUs goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send TextUs alerts to Slack, Discord or a webhook — free.
TextUs, at textus.com, is one of the Cloud & developer services we monitor. TextUs is a business texting app for iOS and Android. Text from your work number, get push notifications, and keep your inbox in your pocket. Free with license.
TextUs publishes an official status page at status.next.textus.com; when we can read it, its incident level is folded into the status shown here.
Common problems for cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
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: 110 ms average, 21–181 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public TextUs incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
110 ms on average over the last 24 hours (21–181 ms).
Yes, at https://status.next.textus.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report TextUs here at once, the problem is on TextUs'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 TextUs. 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.