User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
textexpander.com · Cloud & developer
Is TextExpander down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what to try.
Your browser → textexpander.com—
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, and places with fewer than 3 reports are not shown. Updates every minute.
What's broken
Our checks
Reaching it
Last check reached it in 548 ms · 1 min ago.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 05:15 | 0 | 0.0 | 1981 ms | 0 |
| 05:30 | 0 | 0.0 | 1490 ms | 0 |
| 05:45 | 0 | 0.0 | 404 ms | 0 |
| 06:00 | 0 | 0.0 | 461 ms | 0 |
| 06:15 | 0 | 0.0 | 1149 ms | 0 |
| 06:30 | 0 | 0.0 | 1170 ms | 0 |
| 06:45 | 0 | 0.0 | 858 ms | 0 |
| 07:00 | 0 | 0.0 | 1635 ms | 0 |
| 07:15 | 0 | 0.0 | 1198 ms | 0 |
| 07:30 | 0 | 0.0 | 1354 ms | 0 |
| 07:45 | 0 | 0.0 | 945 ms | 0 |
| 08:00 | 0 | 0.0 | 1104 ms | 0 |
| 08:15 | 0 | 0.0 | 514 ms | 0 |
| 08:30 | 0 | 0.0 | 1248 ms | 0 |
| 08:45 | 0 | 0.0 | 782 ms | 0 |
| 09:00 | 0 | 0.0 | 1463 ms | 0 |
| 09:15 | 0 | 0.0 | 1282 ms | 0 |
| 09:30 | 0 | 0.0 | 1611 ms | 0 |
| 09:45 | 0 | 0.0 | 610 ms | 0 |
| 10:00 | 0 | 0.0 | 1344 ms | 0 |
| 10:15 | 0 | 0.0 | 629 ms | 0 |
| 10:30 | 0 | 0.0 | 2034 ms | 0 |
| 10:45 | 0 | 0.0 | 2004 ms | 0 |
| 11:00 | 0 | 0.0 | 512 ms | 0 |
| 11:15 | 0 | 0.0 | 1819 ms | 0 |
| 11:30 | 0 | 0.0 | 656 ms | 0 |
| 11:45 | 0 | 0.0 | 737 ms | 0 |
| 12:00 | 0 | 0.0 | 595 ms | 0 |
| 12:15 | 0 | 0.0 | 1754 ms | 0 |
| 12:30 | 0 | 0.0 | 1045 ms | 0 |
| 12:45 | 0 | 0.0 | 461 ms | 0 |
| 13:00 | 0 | 0.0 | 1288 ms | 0 |
| 13:15 | 0 | 0.0 | 936 ms | 0 |
| 13:30 | 0 | 0.0 | 496 ms | 0 |
| 13:45 | 0 | 0.0 | 1507 ms | 0 |
| 14:00 | 0 | 0.0 | 551 ms | 0 |
| 14:15 | 0 | 0.0 | 488 ms | 0 |
| 14:30 | 0 | 0.0 | 804 ms | 0 |
| 14:45 | 0 | 0.0 | 595 ms | 0 |
| 15:00 | 0 | 0.0 | 1079 ms | 0 |
| 15:15 | 0 | 0.0 | 687 ms | 0 |
| 15:30 | 0 | 0.0 | 399 ms | 0 |
| 15:45 | 0 | 0.0 | 670 ms | 0 |
| 16:00 | 0 | 0.0 | 529 ms | 0 |
| 16:15 | 0 | 0.0 | 1331 ms | 0 |
| 16:30 | 0 | 0.0 | 707 ms | 0 |
| 16:45 | 0 | 0.0 | 548 ms | 0 |
| 17:00 | 0 | 0.0 | 548 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
Embed a live TextExpander status badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · JSON · MCP server
Past outages
No outages on record for TextExpander yet. Outages of 10 minutes or more get their own page here.
Having trouble with TextExpander?
One report per service every 10 minutes from this network. No account.
Follow TextExpander
Get an email when TextExpander goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send TextExpander alerts to Slack, Discord or a webhook — free.
Questions
Is TextExpander down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
TextExpander not working for me but the status is fine. What now?
If TextExpander is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on TextExpander's side.
How does Damn is it down decide TextExpander's status?
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
How often is TextExpander checked?
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.