Teleport Outage History
Teleport is up right nowPingoru has recorded 52 incidents for Teleport: 20 in the last 12 months and 3 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 1 | 6 of 720 (1%) |
| May 2026 | 6 | 33 of 744 (4%) |
| June 2026 | 3 | 5 of 720 (1%) |
| July 2026 | 2 | 2 of 744 (0%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 1 | 2 of 720 (0%) |
| October 2026 | 2 | 97 of 522 (18%) |
Incidents, newest first
Notice October 18, 2026 Trials Suspended 1d 9h Cloud Signups
Started Oct 18, 2026, 04:36 AM UTC· resolved Oct 19, 2026, 01:50 PM UTC
- identified Oct 18, 2026, 04:36 AM UTC
Trials are temporarily unavailable.
- resolved Oct 19, 2026, 01:50 PM UTC
Provisioning Trials has been resumed.
Minor September 3, 2026 Teleport us-west-2 increased error rates 1h 28m Cloud Service
Started Sep 03, 2026, 10:24 PM UTC· resolved Sep 03, 2026, 11:53 PM UTC
- investigating Sep 03, 2026, 10:24 PM UTC
AWS is experiencing increased API errors in its us-west-2 region which is impacting Teleport Cloud services in that region. Single region Teleport clusters in us-west-2 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
- monitoring Sep 03, 2026, 11:37 PM UTC
We are continuing to monitor the situation.
- resolved Sep 03, 2026, 11:53 PM UTC
This incident has been resolved.
Minor July 24, 2026 Teleport us-west-2 connectivity 1h 26m Cloud Service
Started Jul 24, 2026, 11:53 AM UTC· resolved Jul 24, 2026, 01:20 PM UTC
- identified Jul 24, 2026, 11:53 AM UTC
AWS is experiencing connectivity issues in its us-west-2 region which is impacting Teleport Cloud services in that region. Single region Teleport clusters in us-west-2 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
- monitoring Jul 24, 2026, 12:37 PM UTC
We are monitoring AWS and will ensure services are restored once AWS services are available.
- resolved Jul 24, 2026, 01:20 PM UTC
This incident has been resolved.
Minor July 14, 2026 Agent Version Upgrade 56m Cloud Service
Started Jul 14, 2026, 04:36 PM UTC· resolved Jul 14, 2026, 05:32 PM UTC
- investigating Jul 14, 2026, 04:36 PM UTC
We are investigating issues with agent upgrades and will provide updates here soon.
- identified Jul 14, 2026, 04:41 PM UTC
Newly created agents may fail to join a Cloud deployment. We've identified the root cause and are actively working on a fix.
- resolved Jul 14, 2026, 05:32 PM UTC
Some 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.
Major June 11, 2026 New Tenant Onboarding Failures 1h 37m Cloud Signups
Started Jun 11, 2026, 05:03 PM UTC· resolved Jun 11, 2026, 06:40 PM UTC
- investigating Jun 11, 2026, 05:03 PM UTC
We are currently investigating the issue.
- identified Jun 11, 2026, 05:06 PM UTC
The issue has been identifier and a fix is being implemented.
- resolved Jun 11, 2026, 06:40 PM UTC
The incident has been resolved.
Critical June 1, 2026 New Trials Fail to Provision 1h 45m Cloud Signups
Started Jun 01, 2026, 06:31 PM UTC· resolved Jun 01, 2026, 08:17 PM UTC
- investigating Jun 01, 2026, 06:31 PM UTC
We are currently investigating this issue.
- resolved Jun 01, 2026, 08:17 PM UTC
This incident has been resolved.
Minor June 1, 2026 SSH connections failing for agents on 18.8.2 3h 18m Cloud Service
Started Jun 01, 2026, 05:59 PM UTC· resolved Jun 01, 2026, 09:17 PM UTC
- investigating Jun 01, 2026, 05:59 PM UTC
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.
- investigating Jun 01, 2026, 09:17 PM UTC
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.
- resolved Jun 01, 2026, 09:17 PM UTC
This incident has been resolved.
Critical May 29, 2026 New Trials Fail to Provision Certificates 17h 42m Cloud Signups
Started May 29, 2026, 02:23 AM UTC· resolved May 29, 2026, 08:05 PM UTC
- investigating May 29, 2026, 02:23 AM UTC
We are currently investigating this issue.
- resolved May 29, 2026, 08:05 PM UTC
This incident has been resolved.
Major May 20, 2026 App Access for Beams is Temporarily Disabled 3h 42m Cloud Service
Started May 20, 2026, 07:21 PM UTC· resolved May 20, 2026, 11:04 PM UTC
- identified May 20, 2026, 07:21 PM UTC
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.
- resolved May 20, 2026, 11:04 PM UTC
Application access for beams is now available.
Minor May 19, 2026 JIT connections failing for agents on versions below 18.7.6 8h 20m Cloud Service
Started May 19, 2026, 01:59 PM UTC· resolved May 19, 2026, 10:19 PM UTC
- identified May 19, 2026, 01:59 PM UTC
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.
- identified May 19, 2026, 02:27 PM UTC
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.
- monitoring May 19, 2026, 06:59 PM UTC
We are actively rolling back any customers cluster version to 18.7.4 and will continue to monitor.
- resolved May 19, 2026, 10:19 PM UTC
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.
- postmortem May 29, 2026, 06:21 PM UTC
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.
Notice May 17, 2026 Some tenants experiencing backend failures 43m Cloud Service
Started May 17, 2026, 11:34 AM UTC· resolved May 17, 2026, 12:17 PM UTC
- monitoring May 17, 2026, 11:34 AM UTC
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.
- resolved May 17, 2026, 12:17 PM UTC
This incident has been resolved.
Minor May 9, 2026 Degraded connectivity for certain large tenants 1h 14m Cloud Service
Started May 09, 2026, 11:59 AM UTC· resolved May 09, 2026, 01:13 PM UTC
- monitoring May 09, 2026, 11:59 AM UTC
Teleport Cloud experienced minor degraded connectivity for a period of 30 minutes for certain large tenants. Connectivity has recovered, and we are monitoring.
- resolved May 09, 2026, 01:13 PM UTC
This incident has been resolved.
Notice May 8, 2026 Teleport Cloud Signups - Failure to create new Cloud tenant 1h 42m Cloud Signups
Started May 08, 2026, 07:28 PM UTC· resolved May 08, 2026, 09:10 PM UTC
- identified May 08, 2026, 07:28 PM UTC
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.
- identified May 08, 2026, 07:28 PM UTC
We are continuing to work on a fix for this issue.
- identified May 08, 2026, 09:08 PM UTC
This incident has been resolved.
- resolved May 08, 2026, 09:10 PM UTC
This incident has been resolved.
Minor April 1, 2026 Access Graph is unavailable for Trials 5h 36m Cloud Service
Started Apr 01, 2026, 08:13 PM UTC· resolved Apr 02, 2026, 01:50 AM UTC
- investigating Apr 01, 2026, 08:13 PM UTC
We are currently investigating this issue.
- identified Apr 01, 2026, 11:21 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Apr 02, 2026, 01:42 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Apr 02, 2026, 01:50 AM UTC
This incident has been resolved.
Minor January 26, 2026 Teleport Cloud Slack Access Integration Issues 23d 21h Cloud Service
Started Jan 26, 2026, 06:03 PM UTC· resolved Feb 19, 2026, 03:37 PM UTC
- investigating Jan 26, 2026, 06:03 PM UTC
We are currently investigating issues with the Slack Access integration for Teleport Cloud.
- identified Jan 27, 2026, 02:25 AM UTC
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.
- identified Jan 30, 2026, 08:01 PM UTC
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.
- resolved Feb 19, 2026, 03:37 PM UTC
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
Major January 6, 2026 Teleport Cloud outage us-west-2 25m Cloud Service
Started Jan 06, 2026, 06:36 PM UTC· resolved Jan 06, 2026, 07:01 PM UTC
- investigating Jan 06, 2026, 06:36 PM UTC
We're currently investigating an increase in errors in us-west-2.
- monitoring Jan 06, 2026, 06:42 PM UTC
We've identified the cause and have remediated the issue. We're monitoring the system for full recovery.
- resolved Jan 06, 2026, 07:01 PM UTC
The platform has recovered and is fully operational.
- postmortem Jan 12, 2026, 04:56 PM UTC
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.
Minor November 18, 2025 Teleport website and documentation are unreachable. 6h 24m
Started Nov 18, 2025, 11:50 AM UTC· resolved Nov 18, 2025, 06:15 PM UTC
- identified Nov 18, 2025, 11:50 AM UTC
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/
- monitoring Nov 18, 2025, 02:01 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Nov 18, 2025, 06:15 PM UTC
This incident has been resolved.
Minor November 17, 2025 Windows Desktop access interruptions due to v18.3.1 rollout 13h 35m Cloud Service
Started Nov 17, 2025, 01:20 PM UTC· resolved Nov 18, 2025, 02:55 AM UTC
- identified Nov 17, 2025, 01:20 PM UTC
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.
- monitoring Nov 17, 2025, 05:26 PM UTC
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.
- resolved Nov 18, 2025, 02:55 AM UTC
This incident has been resolved.
Minor October 20, 2025 Teleport us-east-1 connectivity 6h 56m Cloud Service
Started Oct 20, 2025, 04:02 PM UTC· resolved Oct 20, 2025, 10:59 PM UTC
- monitoring Oct 20, 2025, 04:02 PM UTC
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
- resolved Oct 20, 2025, 10:59 PM UTC
This incident has been resolved.
- postmortem Oct 31, 2025, 05:11 PM UTC
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)
Major October 20, 2025 Teleport Cloud Outage 3m Cloud Service, Cloud Signups
Started Oct 20, 2025, 09:46 AM UTC· resolved Oct 20, 2025, 09:49 AM UTC
- investigating Oct 20, 2025, 09:46 AM UTC
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
- resolved Oct 20, 2025, 09:49 AM UTC
The issue has been resolved and all services have been restored.
- postmortem Oct 31, 2025, 05:09 PM UTC
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)
Major October 7, 2025 Teleport Cloud Signup Failures 31m Cloud Signups
Started Oct 07, 2025, 06:11 PM UTC· resolved Oct 07, 2025, 06:42 PM UTC
- investigating Oct 07, 2025, 06:11 PM UTC
We've identified an issue that is currently preventing new cloud signups. We are actively investigating.
- investigating Oct 07, 2025, 06:11 PM UTC
We are continuing to investigate this issue.
- monitoring Oct 07, 2025, 06:29 PM UTC
We've successfully onboarded deployments and are monitoring that the system is fully recovered.
- resolved Oct 07, 2025, 06:42 PM UTC
This incident has been resolved.
Major September 24, 2025 SSH access interruptions due to v18.2.1 rollout 1h 25m Cloud Service
Started Sep 24, 2025, 06:23 PM UTC· resolved Sep 24, 2025, 07:48 PM UTC
- investigating Sep 24, 2025, 06:23 PM UTC
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.
- identified Sep 24, 2025, 06:24 PM UTC
Rollsback to v18.2.0 is progressing.
- resolved Sep 24, 2025, 07:48 PM UTC
Cloud tenants previously running 18.2.1 or 18.2.2 have been rolled back to 18.2.0.
Minor May 14, 2025 Email Validation 2h 5m Cloud Service, Cloud Signups
Started May 14, 2025, 08:35 PM UTC· resolved May 14, 2025, 10:40 PM UTC
- identified May 14, 2025, 08:35 PM UTC
Teleport Cloud's email validation service provider is experiencing intermittent API errors. This impacts cloud trial signups and managing contacts in Teleport clusters.
- resolved May 14, 2025, 10:40 PM UTC
This incident has been resolved.
Minor March 25, 2025 Intermittent Teleport Web UI loading failures –
Started Mar 25, 2025, 01:00 PM UTC· resolved Mar 25, 2025, 01:00 PM UTC
- resolved Mar 26, 2025, 12:58 PM UTC
Between 13:00 and 13:15 a subset of customers might have experienced intermittent failures while loading Teleport Web UI.
- postmortem Mar 31, 2025, 06:42 PM UTC
On March 25th, 2025, Teleport Cloud experienced a brief service interruption that led to an undetermined period of time where some customers’ were unable to load the Teleport web UI. The root cause was the combination of an internal service/load balancer configuration and a missing timeout within the Teleport web UI. The teleport web UI queries an internal API when a user logs in to ensure that an onboarding questionnaire has been completed. This internal API relies on the on AWS load balancer controller to manage ingress and was configured to use an NLB with an instance-based target group. At 12:56 UTC on March 25th, the cluster autoscaler in one of our production EKS clusters began the routine process of removing an under utilized instance from service. The removal of this instance in combination with the instance-based target group caused TCP connections to be dropped\([kubernetes/autoscaler#5532](https://github.com/kubernetes/autoscaler/issues/5532)\). Due to the missing timeout within the teleport web UI, web browsers with a previously established connection to this instance would hang on this dropped connection for an undetermined amount of time, likely until the OS or browser keep-alive logic determined the connection was dead. This outage identified two key improvement Teleport can make to ensure this doesn’t happen again moving forward: 1. Migrate the internal API to IP based target groups - IP based target groups allow for pods to be deregistered with the NLB before being terminated, ensuring time for graceful termination of TCP connections. 2. Removal of the internal API dependency within the Teleport UI - The Teleport team is working on removing this internal API dependency from the web UI initialization flow to ensure similar issues don’t happen again in the future.
Major February 20, 2025 Degraded Connectivity 5h 59m Cloud Service, Cloud Signups
Started Feb 20, 2025, 08:14 PM UTC· resolved Feb 21, 2025, 02:14 AM UTC
- investigating Feb 20, 2025, 08:14 PM UTC
We are currently investigating connectivity degradation on our infrastructure.
- identified Feb 20, 2025, 08:34 PM UTC
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.
- monitoring Feb 21, 2025, 01:06 AM UTC
Services have been restored in all regions.
- resolved Feb 21, 2025, 02:14 AM UTC
This incident has been resolved.
- postmortem Mar 03, 2025, 09:58 PM UTC
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.