Vendor Status Watch

← all vendors

Teleport status history

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

1incidents, last 30 days
3incidents, last 90 days
23incidents on record
Incidents per week, last 12 weeks:

How long do Teleport incidents last?

102 minmedian incident duration23 measured
13.6 h90th percentile1 in 10 ran longer
91 minmedian, major/critical only10 incidents

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)

StartedIncidentStatusImpactDuration
2026-09-03 22:24 UTCTeleport us-west-2 increased error ratesresolvedminor1 h 28 min
2026-07-24 11:53 UTCTeleport us-west-2 connectivityresolvedminor1 h 26 min
2026-07-14 16:36 UTCAgent Version Upgraderesolvedminor56 min
2026-06-11 17:03 UTCNew Tenant Onboarding Failuresresolvedmajor1 h 37 min
2026-06-01 18:31 UTCNew Trials Fail to Provisionresolvedcritical1 h 45 min
2026-06-01 17:59 UTCSSH connections failing for agents on 18.8.2resolvedminor3 h 18 min
2026-05-29 02:23 UTCNew Trials Fail to Provision Certificatesresolvedcritical17 h 42 min
2026-05-20 19:21 UTCApp Access for Beams is Temporarily Disabledresolvedmajor3 h 42 min
2026-05-19 13:59 UTCJIT connections failing for agents on versions below 18.7.6postmortemminor8 h 20 min
2026-05-17 11:34 UTCSome tenants experiencing backend failuresresolvednone43 min
2026-05-09 11:59 UTCDegraded connectivity for certain large tenantsresolvedminor1 h 14 min
2026-05-08 19:28 UTCTeleport Cloud Signups - Failure to create new Cloud tenantresolvednone1 h 42 min
2026-04-01 20:13 UTCAccess Graph is unavailable for Trialsresolvedminor5 h 36 min
2026-03-10 10:22 UTCNew Tenant Onboarding Failuresresolvedmajor5 h 53 min
2026-01-26 18:03 UTCTeleport Cloud Slack Access Integration Issuesresolvedminor23 d 21 h
2026-01-06 18:36 UTCTeleport Cloud outage us-west-2postmortemmajor25 min
2025-11-18 11:50 UTCTeleport website and documentation are unreachable.resolvedminor6 h 24 min
2025-11-17 13:20 UTCWindows Desktop access interruptions due to v18.3.1 rolloutresolvedminor13 h 35 min
2025-10-20 16:02 UTCTeleport us-east-1 connectivitypostmortemminor6 h 56 min
2025-10-20 09:46 UTCTeleport Cloud Outagepostmortemmajor3 min
2025-10-07 18:11 UTCTeleport Cloud Signup Failuresresolvedmajor31 min
2025-09-29 15:14 UTCTeleport Cloud Signups - Failure to create new Cloud tenantresolvedcritical14 min
2025-09-24 18:23 UTCSSH access interruptions due to v18.2.1 rolloutresolvedmajor1 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
}