New Trials Fail to Provision Certificates
Affected: Cloud Signups
Timeline · 2 updates
- 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.
Teleport Outage History
Teleport is up right nowTeleport had 16 outages in the last 2 years totaling 639h 28m of downtime — averaging 0.7 incidents per month.
There were 16 Teleport outages since July 21, 2025 totaling 639h 28m of downtime. Each is summarised below — incident details, duration, and resolution information.
App Access for Beams is Temporarily Disabled
Affected: Cloud Service
Timeline · 2 updates
- 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.
JIT connections failing for agents on versions below 18.7.6
Affected: Cloud Service
Timeline · 5 updates
- 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.
Some tenants experiencing backend failures
Affected: Cloud Service
Timeline · 2 updates
- 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.
Degraded connectivity for certain large tenants
Affected: Cloud Service
Timeline · 2 updates
- 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.
Teleport Cloud Signups - Failure to create new Cloud tenant
Affected: Cloud Signups
Timeline · 4 updates
- 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.
Access Graph is unavailable for Trials
Affected: Cloud Service
Timeline · 4 updates
- 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.
New Tenant Onboarding Failures
Affected: Cloud Signups
Timeline · 3 updates
- investigating Mar 10, 2026, 10:22 AM UTC
We're currently investigating an issue that prevents new tenants from onboarding.
- monitoring Mar 10, 2026, 11:36 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Mar 10, 2026, 04:16 PM UTC
This incident has been resolved.
Teleport Cloud Slack Access Integration Issues
Affected: Cloud Service
Timeline · 4 updates
- 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
Teleport Cloud outage us-west-2
Affected: Cloud Service
Timeline · 4 updates
- 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.
Teleport website and documentation are unreachable.
Timeline · 3 updates
- 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.
Windows Desktop access interruptions due to v18.3.1 rollout
Affected: Cloud Service
Timeline · 3 updates
- 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.
Teleport us-east-1 connectivity
Affected: Cloud Service
Timeline · 3 updates
- 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)
Teleport Cloud Outage
Affected: Cloud ServiceCloud Signups
Timeline · 3 updates
- 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)
Teleport Cloud Signup Failures
Affected: Cloud Signups
Timeline · 4 updates
- 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.
SSH access interruptions due to v18.2.1 rollout
Affected: Cloud Service
Timeline · 3 updates
- 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.