https://approjects-vendor-status-watch.static.hf.space/v/teleport.htmlIncidents from Teleport's public status page, polled daily.Wed, 16 Sep 2026 12:28:20 +0000https://stspg.io/ypsfw49n76g7teleport:2026-09-03T22:24:23.542ZThu, 03 Sep 2026 22:24:23 +0000This incident has been resolved.https://stspg.io/9ct3nqy3xrg2teleport:2026-07-24T11:53:56.019ZFri, 24 Jul 2026 11:53:56 +0000This incident has been resolved.https://stspg.io/btmbjvzlrkygteleport:2026-07-14T16:36:34.730ZTue, 14 Jul 2026 16:36:34 +0000Some customers using deprecated apt or rpm managed update systems were automatically misconfigured to update agents to an unavailable version. The misconfiguration has been addressed by locking all agent versions to 18.9.1 for Cloud Tenants running 18.9.1 or 18.9.2. v18 tenants will be upgraded to 18.10.0 by end of next week and agents will update to 18.10.0 during normal scheduled maintenance windows.https://stspg.io/vcvtktgz0ckwteleport:2026-06-11T17:03:50.847ZThu, 11 Jun 2026 17:03:50 +0000The incident has been resolved.https://stspg.io/z40bn3zvysn6teleport:2026-06-01T18:31:35.355ZMon, 01 Jun 2026 18:31:35 +0000This incident has been resolved.https://stspg.io/n9079xxnrrbsteleport:2026-06-01T17:59:05.518ZMon, 01 Jun 2026 17:59:05 +0000This incident has been resolved.https://stspg.io/7wgmw0369t93teleport:2026-05-29T02:23:23.096ZFri, 29 May 2026 02:23:23 +0000This incident has been resolved.https://stspg.io/vx7vsn8prcxqteleport:2026-05-20T19:21:47.593ZWed, 20 May 2026 19:21:47 +0000Application access for beams is now available.https://stspg.io/7s1n8686gykwteleport:2026-05-19T13:59:29.925ZTue, 19 May 2026 13:59:29 +0000A regression introduced in Teleport v18.7.6 broke the Just-in-Time \(JIT\) access flow when connecting to database agents running versions earlier than 18.7.6. The defect affected clusters on versions 18.7.6, 18.8.0, and 18.8.1. The 18.8.0 and \(upcoming\) 18.8.1 tenant upgrades would have impacted ~16% of Cloud customers, specifically those using database access. To prevent disruption, affected customers were rolled back to a stable version while the fix lands in 18.8.2.https://stspg.io/nwf5j20zv2jjteleport:2026-05-17T11:34:30.769ZSun, 17 May 2026 11:34:30 +0000This incident has been resolved.https://stspg.io/h0gfshxv2sz6teleport:2026-05-09T11:59:22.675ZSat, 09 May 2026 11:59:22 +0000This incident has been resolved.https://stspg.io/9hcp519wjcx7teleport:2026-05-08T19:28:32.131ZFri, 08 May 2026 19:28:32 +0000This incident has been resolved.https://stspg.io/n6syy23msxp5teleport:2026-04-01T20:13:02.976ZWed, 01 Apr 2026 20:13:02 +0000This incident has been resolved.https://stspg.io/yb213zbzcvzpteleport:2026-03-10T10:22:33.995ZTue, 10 Mar 2026 10:22:33 +0000This incident has been resolved.https://stspg.io/jcvxhph4sht0teleport:2026-01-26T18:03:27.740ZMon, 26 Jan 2026 18:03:27 +0000A fix has been rolled out to Teleport Cloud customers. Customers will need to perform the following actions to fix their Slack integration. Delete the Slack integration from your Teleport Cloud Cluster: 1. Navigate to https://[your-cluster]/web/integrations 2. Locate the Slack integration and click "Options" then "Delete" Have one of your Slack admins uninstall the Teleport Cloud app: 1. Navigate to your Slack 2. Go to "Admin" in the sidebar 3. Click "Apps & workflows" 4. Search for "Teleport Cloud" 5. Click "App Details" 6. Go to "Configuration" 7. Under "Remove App", click "Remove App" Setup the Slack Integration again in your Teleport Cloud cluster: 1. Navigate to https://[your-cluster]/web/integrations 2. Click "Enroll New Integration" 3. Follow the prompts for configuring the Slackhttps://stspg.io/vbpfll2rqjryteleport:2026-01-06T18:36:01.724ZTue, 06 Jan 2026 18:36:01 +0000On January 6, 2026 at 18:24 UTC, approximately 24% of Teleport Cloud customers experienced an interruption to Teleport Auth and/or Proxy services for up to 24 minutes. The incident was caused by two concurrent infrastructure events that compounded each other. A resource exhaustion issue on multiple nodes temporarily disrupted scheduling. At the same time, an unrelated scaling event interrupted a backend service responsible for refreshing cloud credentials used by Teleport Auth, which led to authentication failures. Once the affected infrastructure was removed, service recovery began immediately. Backend services were restored, credentials were refreshed, and impacted Teleport services gradually returned to a healthy state. We are making changes to improve isolation between critical servhttps://stspg.io/vyfbnk95bzl5teleport:2025-11-18T11:50:38.509ZTue, 18 Nov 2025 11:50:38 +0000This incident has been resolved.https://stspg.io/6q34k6gt5y7kteleport:2025-11-17T13:20:14.482ZMon, 17 Nov 2025 13:20:14 +0000This incident has been resolved.https://stspg.io/q0bwmshyhd8rteleport:2025-10-20T16:02:58.803ZMon, 20 Oct 2025 16:02:58 +0000On October 20, 2025, between 06:48 and 22:07 UTC, some Teleport Cloud customers experienced issues connecting to their cluster. These issues were triggered by an AWS outage impacting the US East region \(N. Virginia: us-east-1\). The severity of the impact was dependent on the type of Teleport Cloud deployment and where users or agents were located. * Customers with single-region auth service deployments in the US East region were unable to connect to their cluster * Customers with multi-region auth service deployments in the US East region experienced intermittent connectivity issues * Users and agents located near the US East region experienced intermittent connectivity issues For more details, please download the full RCA: [RCA: 2025-10-20 US East Region Connectivity](https://trust.https://stspg.io/txw42drhxt19teleport:2025-10-20T09:46:27.528ZMon, 20 Oct 2025 09:46:27 +0000On October 20, 2025, between 06:48 and 22:07 UTC, some Teleport Cloud customers experienced issues connecting to their cluster. These issues were triggered by an AWS outage impacting the US East region \(N. Virginia: us-east-1\). The severity of the impact was dependent on the type of Teleport Cloud deployment and where users or agents were located. * Customers with single-region auth service deployments in the US East region were unable to connect to their cluster * Customers with multi-region auth service deployments in the US East region experienced intermittent connectivity issues * Users and agents located near the US East region experienced intermittent connectivity issues For more details, please download the full RCA: [RCA: 2025-10-20 US East Region Connectivity](https://trust.https://stspg.io/x5hmk6v1xclwteleport:2025-10-07T18:11:09.035ZTue, 07 Oct 2025 18:11:09 +0000This incident has been resolved.https://stspg.io/xgt76pd6vcz0teleport:2025-09-29T15:14:37.063ZMon, 29 Sep 2025 15:14:37 +0000This incident has been resolved.https://stspg.io/drkmhymxbm1bteleport:2025-09-24T18:23:36.257ZWed, 24 Sep 2025 18:23:36 +0000Cloud tenants previously running 18.2.1 or 18.2.2 have been rolled back to 18.2.0.