# Teleport: Teleport us-east-1 connectivity

- Impact (vendor’s label): minor
- Status: postmortem
- Started: 2025-10-20 16:02 UTC · Resolved: 2025-10-20 22:59 UTC · Duration: 6.9 h
- Updates: 3 · Affected components: Cloud Service
- [Vendor status page: https://stspg.io/q0bwmshyhd8r](https://stspg.io/q0bwmshyhd8r)
- [Company: Teleport](https://rewindex.com/company/teleport.md)

## Part of an outage event

- [AWS us-east-1 outage, Oct 20, 2025: 141 vendors, 181 incidents](https://rewindex.com/events/2025-10-20-aws-us-east-1)
- This incident blames AWS as the cause. (hop 1, posted +8 h 52 min vs AWS’s own post)
- Evidence: “…Teleport us-east-1 connectivity 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 ou…”

```mermaid
flowchart LR
  root["AWS us-east-1<br/>posted 07:11 UTC"]:::root
  before["Posted before AWS did<br/>5 vendors, 4 blamed AWS<br/>Salesforce, Descope, Ashby +2"]:::blames
  root --> before
  h1["Within an hour<br/>18 vendors, 17 blamed AWS<br/>Asana, Firebolt, Monday.com +15"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>30 vendors, 29 blamed AWS<br/>SingleStore, Loops, Buildkite +27"]:::blames
  root --> h4
  later["Later<br/>45 vendors, 44 blamed AWS<br/>RudderStack, Airbyte, Unbounce +42"]:::blames
  root --> later
  p0["Twilio<br/>posted +15 min"]:::blames
  root --> p0
  k0["BigCommerce<br/>+2 h 46 min"]:::hop2
  p0 -->|"blamed Twilio"| k0
  p1["Webflow<br/>posted +4 h 37 min, did not name AWS"]:::timing
  root -.-> p1
  k1["Rootly<br/>+10 h 23 min"]:::hop2
  p1 -->|"blamed Webflow"| k1
  p2["Baseten<br/>posted +4 min"]:::blames
  root --> p2
  k2["Zed<br/>+26 h 20 min"]:::hop2
  p2 -->|"blamed Baseten"| k2
  me["Teleport (this incident)<br/>posted +8 h 52 min"]:::me
  later --- me
```

_Detected automatically from incidents that started together and named the same provider; a link means one incident named another vendor, not a confirmed cause._

## Timeline of updates

- **monitoring** 2025-10-20 16:02 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** 2025-10-20 22:59 UTC: This incident has been resolved.
- **postmortem** 2025-10-31 17:11 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)


---
Canonical: https://rewindex.com/company/teleport/incidents/8pkmhwq9wm3r · Markdown: https://rewindex.com/company/teleport/incidents/8pkmhwq9wm3r.md · JSON: https://rewindex.com/api/v1/companies/teleport/incidents/8pkmhwq9wm3r · Generated 2026-10-19T21:15:31.013Z