Home ci 31. edge-network: regions

31. edge-network: regions

Last updated on Aug 05, 2025

title: "Epycbyte Edge Network Regions"

Epycbyte Edge Network Regions

Epycbyte's Edge Network is a globally distributed platform designed to optimize performance and reliability. This article outlines the regions supported by Epycbyte's Edge Network, its infrastructure, caching strategy, and other relevant information.

Global Infrastructure

Epycbyte's Edge Network is built on a sophisticated global infrastructure optimized for performance and reliability:

  • Points of Presence (PoPs): Over 100 PoPs distributed across the globe serve as the first point of contact for incoming requests, ensuring low-latency access.
  • Edge Regions: 18 compute-capable regions where your code can run close to your data.
  • Private Network: Traffic flows from PoPs to the nearest Edge region through private, low-latency connections.

Caching Strategy

Epycbyte's caching strategy focuses on maximizing efficiency and performance:

  • Fewer, denser regions increase cache hit probability for popular content.
  • Extensive PoP network ensures quick access to regional caches, minimizing latency.
  • Higher cache hit ratios reduce the need for requests to go back to the origin server.

Region List

Below is a list of supported regions:

  1. arn1 - Stockholm, Sweden
  2. bom1 - Mumbai, India
  3. cdg1 - Paris, France
  4. cle1 - Cleveland, USA
  5. cpt1 - Cape Town, South Africa
  6. dub1 - Dublin, Ireland
  7. fra1 - Frankfurt, Germany
  8. gru1 - Moscow, Russia
  9. hkg1 - Hong Kong
  10. hnd1 - Tokyo, Japan
  11. iad1 - Washington D.C., USA
  12. kix1 - Seoul, South Korea
  13. lhr1 - London, UK
  14. pdx1 - San Francisco, USA
  15. sfo1 - San Francisco, USA
  16. sin1 - Singapore
  17. syd1 - Sydney, Australia
  18. cpt1 - Cape Town, South Africa

Points of Presence (PoPs) Functions

  • Serve as entry points for traffic.
  • Handle intelligent routing and regional failover.

Local Development Regions

  • Developers can test applications in local regions before deployment.
  • Region-specific configurations are supported.

Compute Defaults

  • Default compute region is iad1 (Washington D.C., USA).
  • Enterprise customers can configure specific regions.

Outage Resiliency

Epycbyte's multi-layered resiliency approach includes:

  • Intelligent routing through PoPs.
  • Regional failover capabilities for Serverless Functions.
  • Priority order for traffic rerouting during outages: iad1, cle1, sfo1, dub1, pdx1, lhr1, cdg1, fra1, arn1, gru1, hnd1, kix1, icn1, bom1, hkg1, syd1, sin1, cpt1.

FAQ

  • Q: What is the default compute region?

    • A: iad1 (Washington D.C., USA).

  • Q: How does traffic reroute during outages?

    • A: Traffic reroutes to the next closest region in this priority order: iad1, cle1, sfo1, dub1, pdx1, lhr1, cdg1, fra1, arn1, gru1, hnd1, kix1, icn1, bom1, hkg1, syd1, sin1, cpt1.

  • Q: Can Serverless Functions failover to another region?

    • A: Yes, for Enterprise customers, Serverless Functions can automatically failover if their region becomes unavailable.