Teleport status history
Current state: operational — “All Systems Operational” per https://status.teleport.sh (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Teleport incidents last?
From 23 incidents with a vendor-posted start and resolve time. Longest on record: Teleport Cloud Slack Access Integration Issues — 23.9 days (2026-01-26 18:03 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 (23)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-09-03 22:24 UTC | Teleport us-west-2 increased error rates | resolved | minor | 1 h 28 min |
| 2026-07-24 11:53 UTC | Teleport us-west-2 connectivity | resolved | minor | 1 h 26 min |
| 2026-07-14 16:36 UTC | Agent Version Upgrade | resolved | minor | 56 min |
| 2026-06-11 17:03 UTC | New Tenant Onboarding Failures | resolved | major | 1 h 37 min |
| 2026-06-01 18:31 UTC | New Trials Fail to Provision | resolved | critical | 1 h 45 min |
| 2026-06-01 17:59 UTC | SSH connections failing for agents on 18.8.2 | resolved | minor | 3 h 18 min |
| 2026-05-29 02:23 UTC | New Trials Fail to Provision Certificates | resolved | critical | 17 h 42 min |
| 2026-05-20 19:21 UTC | App Access for Beams is Temporarily Disabled | resolved | major | 3 h 42 min |
| 2026-05-19 13:59 UTC | JIT connections failing for agents on versions below 18.7.6 | postmortem | minor | 8 h 20 min |
| 2026-05-17 11:34 UTC | Some tenants experiencing backend failures | resolved | none | 43 min |
| 2026-05-09 11:59 UTC | Degraded connectivity for certain large tenants | resolved | minor | 1 h 14 min |
| 2026-05-08 19:28 UTC | Teleport Cloud Signups - Failure to create new Cloud tenant | resolved | none | 1 h 42 min |
| 2026-04-01 20:13 UTC | Access Graph is unavailable for Trials | resolved | minor | 5 h 36 min |
| 2026-03-10 10:22 UTC | New Tenant Onboarding Failures | resolved | major | 5 h 53 min |
| 2026-01-26 18:03 UTC | Teleport Cloud Slack Access Integration Issues | resolved | minor | 23 d 21 h |
| 2026-01-06 18:36 UTC | Teleport Cloud outage us-west-2 | postmortem | major | 25 min |
| 2025-11-18 11:50 UTC | Teleport website and documentation are unreachable. | resolved | minor | 6 h 24 min |
| 2025-11-17 13:20 UTC | Windows Desktop access interruptions due to v18.3.1 rollout | resolved | minor | 13 h 35 min |
| 2025-10-20 16:02 UTC | Teleport us-east-1 connectivity | postmortem | minor | 6 h 56 min |
| 2025-10-20 09:46 UTC | Teleport Cloud Outage | postmortem | major | 3 min |
| 2025-10-07 18:11 UTC | Teleport Cloud Signup Failures | resolved | major | 31 min |
| 2025-09-29 15:14 UTC | Teleport Cloud Signups - Failure to create new Cloud tenant | resolved | critical | 14 min |
| 2025-09-24 18:23 UTC | SSH access interruptions due to v18.2.1 rollout | resolved | major | 1 h 25 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 Teleport with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"teleport"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}