--- title: Building a low latency access proxy at Teleport | daily.dev description: Teleport describes how it expanded its hosted access proxy platform to five global regions to fix severe latency issues (over 1 second keypress delay reported... canonical: https://daily.dev/posts/building-a-low-latency-access-proxy-at-teleport-ohqrhvzx8 twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Building a low latency access proxy at Teleport | daily.dev og:description: Teleport describes how it expanded its hosted access proxy platform to five global regions to fix severe latency issues (over 1 second keypress delay reported... og:url: https://daily.dev/posts/building-a-low-latency-access-proxy-at-teleport-ohqrhvzx8 og:image: https://api.daily.dev/og/posts/OhQrHVzX8.png og:image:alt: Building a low latency access proxy at Teleport 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. # Building a low latency access proxy at Teleport **[Teleport](https://daily.dev/sources/teleport)** · 5 min read · 0 upvotes · 0 comments ## Summary Teleport describes how it expanded its hosted access proxy platform to five global regions to fix severe latency issues (over 1 second keypress delay reported from distant regions when traffic routed through a single US West deployment). The team explains why they rejected per-region domains and split-horizon DNS in favor of Anycast routing via AWS Global Accelerator, and how they built a custom Kubernetes ingress controller to share load balancers across customers instead of provisioning one ELB per customer. Multi-region support launched as opt-in early access, with full rollout planned for early 2022. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How did Teleport reduce latency for its cloud access proxy across global regions? Teleport adopted Anycast routing via AWS Global Accelerator to route users to the nearest of five deployed regions, rather than using per-region domains or split-horizon DNS. They also built a custom Kubernetes ingress controller connecting global accelerators to nginx VMs, letting multiple customers share load balancers instead of provisioning one elastic load balancer per customer. _daily.dev surfaces engineering deep dives like this for teams tuning multi-region latency._ ### Why did Teleport reject split-horizon DNS for routing users to the nearest region? Split-horizon DNS, which returns different responses based on a client's location, was ruled out for not being as reliable as needed. Teleport also rejected using separate domains per region because it conflicted with the goal of offering a single simple endpoint for accessing all computing resources, ultimately choosing Anycast routing through AWS Global Accelerator instead. _Engineers weighing DNS versus Anycast routing strategies can find real-world tradeoffs like this through daily.dev._ ## Similar posts on daily.dev - [AWS Previews Route 53 Global Resolver to Decouple DNS from Regional Failures](https://daily.dev/posts/aws-previews-route-53-global-resolver-to-decouple-dns-from-regional-failures-i3aosgrjk) · InfoQ · 1 upvotes · 0 comments - [Improving Smart Tiered Cache for Public Cloud Regions](https://daily.dev/posts/improving-smart-tiered-cache-for-public-cloud-regions-hw6qxksqc) · Cloudflare · 7 upvotes · 2 comments - [Amazon Route 53 Global Resolver now lets you add and remove AWS Regions for anycast DNS resolution](https://daily.dev/posts/amazon-route-53-global-resolver-now-lets-you-add-and-remove-aws-regions-for-anycast-dns-resolution-mmgoawg6e) · AWS · 0 upvotes · 0 comments - [Inside Agoda’s Storefront: A Latency-Aware Reverse Proxy for Improving DNS Based Load Distribution](https://daily.dev/posts/inside-agoda-s-storefront-a-latency-aware-reverse-proxy-for-improving-dns-based-load-distribution-9rmwtf69t) · InfoQ · 0 upvotes · 0 comments --- Tags: [#kubernetes](https://daily.dev/tags/kubernetes) [View this post on daily.dev](https://daily.dev/posts/building-a-low-latency-access-proxy-at-teleport-ohqrhvzx8) ```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":"Building a low latency access proxy at Teleport","url":"https://daily.dev/posts/building-a-low-latency-access-proxy-at-teleport-ohqrhvzx8","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/building-a-low-latency-access-proxy-at-teleport-ohqrhvzx8"},"datePublished":"2026-08-23T12:22:48.201Z","dateModified":"2026-08-23T12:51:50.375Z","description":"Teleport describes how it expanded its hosted access proxy platform to five global regions to fix severe latency issues (over 1 second keypress delay reported...","image":"https://media.daily.dev/image/upload/s--P4t4XyoV--/f_auto/v1722860399/public/Placeholder%2001","thumbnailUrl":"https://media.daily.dev/image/upload/s--P4t4XyoV--/f_auto/v1722860399/public/Placeholder%2001","isAccessibleForFree":true,"articleSection":"Teleport","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":"Teleport","logo":"https://media.daily.dev/image/upload/s--Dw-Bbw6O--/c_limit,w_256/f_auto,q_auto/v1787487494/logos/teleport?_a=BAMAMicg0","url":"https://daily.dev/sources/teleport"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/building-a-low-latency-access-proxy-at-teleport-ohqrhvzx8","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"kubernetes","timeRequired":"PT5M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Teleport","item":"https://daily.dev/sources/teleport"},{"@type":"ListItem","position":3,"name":"Building a low latency access proxy at Teleport"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/building-a-low-latency-access-proxy-at-teleport-ohqrhvzx8#faq","mainEntity":[{"@type":"Question","name":"How did Teleport reduce latency for its cloud access proxy across global regions?","acceptedAnswer":{"@type":"Answer","text":"Teleport adopted Anycast routing via AWS Global Accelerator to route users to the nearest of five deployed regions, rather than using per-region domains or split-horizon DNS. They also built a custom Kubernetes ingress controller connecting global accelerators to nginx VMs, letting multiple customers share load balancers instead of provisioning one elastic load balancer per customer. daily.dev surfaces engineering deep dives like this for teams tuning multi-region latency."}},{"@type":"Question","name":"Why did Teleport reject split-horizon DNS for routing users to the nearest region?","acceptedAnswer":{"@type":"Answer","text":"Split-horizon DNS, which returns different responses based on a client's location, was ruled out for not being as reliable as needed. Teleport also rejected using separate domains per region because it conflicted with the goal of offering a single simple endpoint for accessing all computing resources, ultimately choosing Anycast routing through AWS Global Accelerator instead. Engineers weighing DNS versus Anycast routing strategies can find real-world tradeoffs like this through daily.dev."}}]} ```