Teleport had 28 outages in the last 2 years totaling 677h 29m of downtime — averaging 1.2 incidents per month.
There were 28 Teleport outages since October 7, 2024 totaling 677h 29m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating the issue.
The issue has been identifier and a fix is being implemented.
The incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
We have identified a regression introduced in 18.8.2 that can impact agent SSH connectivity. We will be rolling back agents to 18.7.4 and will provide an update when this is complete.
This was an isolated incident and does not appear to be impacting other customers at this time. We will continue to monitor the situation closely and provide updates as necessary.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
Application access for Beams (via `tsh beams publish`) is temporarily disabled due to an ongoing issue. Attempting to access published beams will result in "Access Denied" until resolved.
Application access for beams is now available.
We've identified a regression introduced in v18.7.6 that breaks the JIT flow when connecting to agents running versions below 18.7.6. The issue is present in cluster versions 18.7.6, 18.8.0, and 18.8.1, and affects a subset of customers. We are still confirming which agent types are impacted and will share a list shortly. We'll provide another update as mitigation rolls out.
We've confirmed that the regression only affects database agents running versions below 18.7.6 when connecting to clusters on 18.7.6, 18.8.0, or 18.8.1.
We are actively rolling back any customers cluster version to 18.7.4 and will continue to monitor.
Rollbacks to a stable cluster version have been completed successfully for all affected customers. We're now focused on developing a fix, which is expected to ship in the next version release.
A 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.
We have observed a few tenants experiencing issues interacting with their backends. All tenants have recovered automatically. We are continuing to monitor and investigate the cause of the disruption.
This incident has been resolved.
Teleport Cloud experienced minor degraded connectivity for a period of 30 minutes for certain large tenants. Connectivity has recovered, and we are monitoring.
This incident has been resolved.
Teleport Cloud Signups rely on Let's Encrypt for Certificate generation. Let's Encrypt is currently experiencing an outage which blocks the creation of new signups. This does not impact existing Teleport Cloud clusters.
We are continuing to work on a fix for this issue.
This incident has been resolved.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating issues with the Slack Access integration for Teleport Cloud.
We are experiencing ongoing connectivity issues with Slack that have de-authenticated some users of our Slack hosted plugin. To address this temporarily and reconnect Slack, you can delete the integration, wait one hour, and re-create it: 1. Navigate to https://[your-cluster]/web/integrations 2. Locate the Slack integration and click "Options" then "Delete" 3. Wait one hour 4. Click "Enroll New Integration" and follow the prompts Note that you may need to repeat these steps if your Slack integration becomes disconnected again. We are working on a permanent fix.
We have identified the root cause of the issue. A fix will roll out next week as part of scheduled cluster upgrades. Apologies for the disruption.
A 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 Slack integration
We're currently investigating an increase in errors in us-west-2.
We've identified the cause and have remediated the issue. We're monitoring the system for full recovery.
The platform has recovered and is fully operational.
On 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 services, enforce stricter resource limits, and ensure that a single infrastructure disruption cannot prevent credential refresh or delay service recovery in the future.
Teleport website (goteleport.com) is experiencing intermittent connection problems due to a Cloudflare outage - https://www.cloudflarestatus.com/. In the meantime, you can access documentation using an alternative domain - https://docs.amplify.goteleport.com/docs/
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Following Teleport Tenants’ upgrade to v18.3.1, some Teleport agents were auto-upgraded to v18.3.1 and are unable to access resources via Windows Desktop. Rollout of Teleport v18.3.1 was suspended.
Teleport Agents that were upgraded to v18.3.1 and have Windows Desktop access configured were scheduled to be downgraded to v18.2.8 during the next configured maintenance window.
This incident has been resolved.
AWS is continuing to experience network degradation in its us-east-1 region which is impacting Teleport Cloud services in that region. Single region Teleport clusters in us-east-1 may see disruption. We are monitoring AWS and will ensure services are restored once AWS services are available. https://health.aws.amazon.com/health/status
This incident has been resolved.
On 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.goteleport.com/resources?s=ku9gorp0blta6u96pazrhw&name=teleport-cloud-rca:-2025-10-20-us-east-region-connectivity)
AWS is experiencing an outage in its us-east-1 region which is impacting Teleport Cloud services in that region. Teleport clusters whose primary auth region is us-east-1 are unavailable. We are monitoring AWS and will ensure services are restored once AWS services are available. https://health.aws.amazon.com/health/status
The issue has been resolved and all services have been restored.
On 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.goteleport.com/resources?s=ku9gorp0blta6u96pazrhw&name=teleport-cloud-rca:-2025-10-20-us-east-region-connectivity)
We've identified an issue that is currently preventing new cloud signups. We are actively investigating.
We are continuing to investigate this issue.
We've successfully onboarded deployments and are monitoring that the system is fully recovered.
This incident has been resolved.
Some Cloud tenants upgraded to v18.2.1 on 9/24 at 16 UTC are unable to access resources via SSH. Rollback to v18.2.0 is in progress.
Rollsback to v18.2.0 is progressing.
Cloud tenants previously running 18.2.1 or 18.2.2 have been rolled back to 18.2.0.
Teleport Cloud's email validation service provider is experiencing intermittent API errors. This impacts cloud trial signups and managing contacts in Teleport clusters.
This incident has been resolved.
We are currently investigating connectivity degradation on our infrastructure.
We've identified the issue and have confirmed that connectivity disruption is only affecting a subset of tenants. Additionally, new signups are currently unavailable until the issue is resolved.
Services have been restored in all regions.
This incident has been resolved.
Teleport Cloud customers experienced a service disruption intermittently impacting connectivity for about 40 minutes. The root cause of the incident was a bug in the Envoy Gateway ingress service that resulted in excessive memory utilization and ultimately restarts. The incident was triggered by the restart of all tenant services due to an undocumented background EKS storage migration that occurred during a scheduled maintenance period to upgrade the Kubernetes control plane. In response to the incident, the Teleport team shut down ingress controllers which prevented routing updates from triggering ingress service OOM events. This reduced customer impact by stabilizing ingress connectivity. Once the EKS storage migration and tenant service restarts were completed, the team rolled back the Envoy gateway version which stabilized the platform.
We're experiencing an elevated level of errors impacting cross region connectivity.
The issue has been identified and the system is recovering.
This incident has been resolved.
A small number of customers \(<5\) with a custom backend configuration experienced a connectivity issue in us-west-2 lasting around 30 minutes due to a Cilium failure that was inadvertently blocking connections between Auth servers and their backend.
We've been notified that new v17 agents may fail to start or upgrade due to the v17 version not being found. We've identified the problem and are working on deploying the fix.
A fix has been deployed and we will continue to monitor the remediation.
An issue was reported regarding the ability to connect to the usage reporting server.
The root cause of this issue was the inability to submit large batches of usage events due to a platform limitation with the payload size. Customers sending large batches of usage events received an error in Teleport Auth logs and a cluster alert. Impact was limited to a subset of customers. No effect to the health or stability of Teleport occurred during this time.
The Access Graph page in Teleport clusters might not load for some customers. An issue has been identified and we are working on a fix.
The fix will be progressively rolled out alongside the current 16.4.11 upgrade. We will continue to monitor until the rollout is complete.
This incident has been resolved.