Edge Network
Overview
Epycbyte's Edge Network enables you to store content close to your customers and run compute in regions close to your data, reducing latency and improving end-user performance.
Edge Network Regions
Our global Edge Network has 119 Points of Presence in 94 cities across 51 countries.
Global network architecture
Epycbyte's Edge Network is built on a robust global infrastructure designed for optimal performance and reliability:
- Points of Presence (PoPs): Our network includes over 100 PoPs distributed worldwide, acting as the first point of contact for incoming requests.
- Edge Regions: Behind these PoPs, we maintain 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, ensuring fast and efficient data transfer.
Features
Our Edge Network offers a range of features to improve performance and functionality:
- Redirects: Redirects are used to tell the client to make a new request to a different URL, useful for enforcing HTTPS, redirecting users, and directing traffic.
- Rewrites: Rewrites internally change the URL the server uses to fetch the requested resource, allowing for dynamic content and improved routing.
- Headers: Headers are used to modify the request and response headers, allowing for improved security, performance, and functionality.
- Caching: Caching stores responses at the edge, reducing latency and improving performance.
- Streaming: Streaming enables you to improve your users' perception of your app's speed and performance.
- HTTPS / SSL: Every Deployment on Epycbyte is served over an HTTPS connection with automatic SSL certificate provisioning.
- Compression: Compression reduces data transfer and improves performance, with support for both gzip and brotli compression.
Pricing
Epycbyte's Edge Network pricing is divided into three resources:
- Fast Data Transfer: Data transfer between the Epycbyte Edge Network and the user's device
- Fast Origin Transfer: Data transfer between the Edge Network and Epycbyte Functions
- Edge Requests: Requests made to the Edge Network
Usage
The table below shows the metrics for the Networking section of the Usage dashboard.
| Metric | Description | Priced | Optimize |
|---|---|---|---|
| Top Paths | The paths that consume the most resources on your team | N/A | N/A |
| Fast Data Transfer | The data transfer between Epycbyte's Edge Network and your sites' end users. | Yes | Learn More |
| Fast Origin Transfer | The data transfer between Epycbyte's Edge Network to Epycbyte Compute | Yes | Learn More |
| Edge Requests | The number of cached and uncached requests that your deployments have received | Yes | Learn More |
Supported protocols
The Edge Network supports the following protocols (negotiated with ALPN ):
- HTTPS
- HTTP/1.1
- HTTP/2
Using Epycbyte's Edge Network locally
Epycbyte supports 35 frontend frameworks, which provide a local development environment used to test your app before deploying to Epycbyte.
Using Epycbyte's Edge Network with other CDNs
While sometimes necessary, proceed with caution when you place another CDN in front of Epycbyte.