--- title: Why didn't ngrok go down in last week's AWS outage? description: Ngrok explains why its service stayed up during the October 20 AWS us-east-1 outage caused by a cascading DNS issue. The company deliberately avoids hosting in... canonical: https://daily.dev/posts/why-didn-t-ngrok-go-down-in-last-week-s-aws-outage--uoocyikvr twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Why didn't ngrok go down in last week's AWS outage? | daily.dev og:description: Ngrok explains why its service stayed up during the October 20 AWS us-east-1 outage caused by a cascading DNS issue. The company deliberately avoids hosting in... og:url: https://daily.dev/posts/why-didn-t-ngrok-go-down-in-last-week-s-aws-outage--uoocyikvr og:image: https://api.daily.dev/og/posts/uooCyikVR.png og:image:alt: Why didn't ngrok go down in last week's AWS outage? og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Why didn't ngrok go down in last week's AWS outage? **[ngrok Blog](https://daily.dev/sources/ngrok)** · 4 min read · 0 upvotes · 0 comments ## Summary Ngrok explains why its service stayed up during the October 20 AWS us-east-1 outage caused by a cascading DNS issue. The company deliberately avoids hosting in us-east-1, choosing us-east-2 instead, because the region's outsized traffic volume makes it a frequent single point of failure across the internet. Ngrok's architecture separates a control plane (dashboard, API) from a data plane of regional points of presence with full feature parity, and uses DNS-based load balancing to automatically reroute traffic away from any degraded PoP to the next-nearest healthy one. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Why did some services stay online during the AWS us-east-1 outage on October 20 while others went down? Services built primarily in us-east-1 were more exposed because it is AWS's highest-volume region and a cascading DNS issue there caused widespread failures. Ngrok stayed available because it runs primarily in us-east-2 instead, and uses DNS-based load balancing to automatically remove any affected point of presence from DNS resolution and reroute traffic to the next-nearest healthy region. _Teams designing around region-specific outage risk can follow AWS infrastructure coverage on daily.dev._ ### How does ngrok route around a regional outage without breaking traffic policies or increasing latency? Ngrok's data plane consists of regional points of presence (PoPs) that each have full feature parity, including Traffic Policy actions, so every PoP can process traffic in-region without forwarding it to an external service. When a PoP is affected, it is removed from DNS resolution and traffic fails over to the next-nearest PoP running the same routing and transformation logic. _Developers architecting multi-region failover can track infrastructure design patterns like this on daily.dev._ ## Similar posts on daily.dev - [More Than DNS: The 14 hour AWS us-east-1 outage](https://daily.dev/posts/more-than-dns-the-14-hour-aws-us-east-1-outage-m4b0fv6uu) · Lobsters · 1 upvotes · 0 comments - [How when AWS was down, we were not](https://daily.dev/posts/how-when-aws-was-down-we-were-not-2z7ljw5ij) · Hacker News · 1 upvotes · 0 comments --- Tags: [#cloud](https://daily.dev/tags/cloud), [#aws](https://daily.dev/tags/aws), [#devtools](https://daily.dev/tags/devtools), [#dns](https://daily.dev/tags/dns) [View this post on daily.dev](https://daily.dev/posts/why-didn-t-ngrok-go-down-in-last-week-s-aws-outage--uoocyikvr) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Why didn't ngrok go down in last week's AWS outage?","url":"https://daily.dev/posts/why-didn-t-ngrok-go-down-in-last-week-s-aws-outage--uoocyikvr","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/why-didn-t-ngrok-go-down-in-last-week-s-aws-outage--uoocyikvr"},"datePublished":"2026-08-23T07:21:27.642Z","dateModified":"2026-08-23T07:28:35.637Z","description":"Ngrok explains why its service stayed up during the October 20 AWS us-east-1 outage caused by a cascading DNS issue. The company deliberately avoids hosting in...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/074a05e81958d5832924ef46b21bc545?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/074a05e81958d5832924ef46b21bc545?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"ngrok Blog","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"ngrok Blog","logo":"https://media.daily.dev/image/upload/s--718XXxvE--/f_auto,q_auto/v1787469610/logos/ngrok?_a=BAMAMicg0","url":"https://daily.dev/sources/ngrok"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/why-didn-t-ngrok-go-down-in-last-week-s-aws-outage--uoocyikvr","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"cloud,aws,devtools,dns","timeRequired":"PT4M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"ngrok Blog","item":"https://daily.dev/sources/ngrok"},{"@type":"ListItem","position":3,"name":"Why didn't ngrok go down in last week's AWS outage?"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/why-didn-t-ngrok-go-down-in-last-week-s-aws-outage--uoocyikvr#faq","mainEntity":[{"@type":"Question","name":"Why did some services stay online during the AWS us-east-1 outage on October 20 while others went down?","acceptedAnswer":{"@type":"Answer","text":"Services built primarily in us-east-1 were more exposed because it is AWS's highest-volume region and a cascading DNS issue there caused widespread failures. Ngrok stayed available because it runs primarily in us-east-2 instead, and uses DNS-based load balancing to automatically remove any affected point of presence from DNS resolution and reroute traffic to the next-nearest healthy region. Teams designing around region-specific outage risk can follow AWS infrastructure coverage on daily.dev."}},{"@type":"Question","name":"How does ngrok route around a regional outage without breaking traffic policies or increasing latency?","acceptedAnswer":{"@type":"Answer","text":"Ngrok's data plane consists of regional points of presence (PoPs) that each have full feature parity, including Traffic Policy actions, so every PoP can process traffic in-region without forwarding it to an external service. When a PoP is affected, it is removed from DNS resolution and traffic fails over to the next-nearest PoP running the same routing and transformation logic. Developers architecting multi-region failover can track infrastructure design patterns like this on daily.dev."}}]} ```