Vendor Status Watch

← all vendors

TextExpander status history

Current state: operational — “All Systems Operational” per http://status.textexpander.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

0incidents, last 30 days
0incidents, last 90 days
6incidents on record
Get TextExpander alerts in your Slack — free templateRSS for TextExpander

How long do TextExpander incidents last?

2.8 hmedian incident duration6 measured
3.1 h90th percentile1 in 10 ran longer
0 minmedian, major/critical only1 incident

From 6 incidents with a vendor-posted start and resolve time. Longest on record: Slower connection times — 6.1 h (2025-10-20 17:13 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.

Incidents on record (6)

StartedIncidentStatusImpactDuration
2026-06-15 20:59 UTCEmails not being sent from TextExpanderresolvednone2 h 42 min
2026-06-15 17:32 UTCEmails not getting sent from TextExpanderresolvednone2 h 53 min
2026-04-06 19:46 UTCUsers having trouble logging in.resolvednone1 h 19 min
2025-12-03 16:06 UTCSystem performance degredationresolvednone3 h 07 min
2025-10-20 17:13 UTCSlower connection timesresolvednone6 h 06 min
2025-10-20 08:30 UTCServer connection issuespostmortemmajor0 min

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch TextExpander with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "textexpander"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}