Skip to content

Update geographic-traffic-routing.mdx #24965

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: production
Choose a base branch
from
Open

Update geographic-traffic-routing.mdx #24965

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions .../support/troubleshooting/general-troubleshooting/geographic-traffic-routing.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,6 @@ pcx_content_type: troubleshooting
title: Cloudflare traffic not being sent to the geographically closest data center
---

Due to the way routing on [Cloudflare's Anycast network](https://www.cloudflare.com/learning/cdn/glossary/anycast-network/) works, requests may be sent to data center locations that are not necessarily the closest geographically. For example, if Cloudflare does not have a peering relationship with your network provider or if that cache location is receiving increased traffic or errors, Cloudflare may manually route users on Free, Pro, or Business plans to other data centers. You can check the [Cloudflare System Status](https://www.cloudflarestatus.com/) to see if any maintenance or incidents are occurring.
Due to the way routing on [Cloudflare's Anycast network](https://www.cloudflare.com/learning/cdn/glossary/anycast-network/) works, requests may be sent to data center locations that are not necessarily the closest geographically. We are continuously adding capacity to our global network and enhancing our automated traffic engineering systems to intelligently manage congestion and other network events. While we always strive to provide the best possible performance by serving traffic from the closest location, our top priority is reliability.

Most requests are sent to the physically closest cache location, but some requests are sent to other data centers that are able to handle requests without errors. For customers who require their zone to always be served by the closest geographic data center with the highest priority of traffic, contact the Sales team to upgrade to an [Enterprise plan](https://www.cloudflare.com/plans/enterprise/contact/).
In instances where performance and reliability are in conflict, our systems are designed to prioritize a stable connection over a local one. We sincerely apologize for any reroutes that may have impacted your services and are working hard to minimize these events, especially for our most important customers, as we continue to make our network as resilient as possible.