惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

F
Fox-IT International blog
Security Latest
Security Latest
S
Security @ Cisco Blogs
L
LINUX DO - 热门话题
T
Threatpost
W
WeLiveSecurity
cs.CL updates on arXiv.org
cs.CL updates on arXiv.org
腾讯CDC
雷峰网
雷峰网
Cyberwarzone
Cyberwarzone
V
V2EX - 技术
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
P
Proofpoint News Feed
T
Tailwind CSS Blog
Cisco Talos Blog
Cisco Talos Blog
人人都是产品经理
人人都是产品经理
罗磊的独立博客
P
Privacy International News Feed
The Register - Security
The Register - Security
T
Threat Research - Cisco Blogs
IT之家
IT之家
T
True Tiger Recordings
SecWiki News
SecWiki News
V
Vulnerabilities – Threatpost
博客园_首页
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
博客园 - 司徒正美
月光博客
月光博客
P
Privacy & Cybersecurity Law Blog
N
News | PayPal Newsroom
Google DeepMind News
Google DeepMind News
The Cloudflare Blog
美团技术团队
Simon Willison's Weblog
Simon Willison's Weblog
博客园 - Franky
V
Visual Studio Blog
E
Exploit-DB.com RSS Feed
酷 壳 – CoolShell
酷 壳 – CoolShell
F
Future of Privacy Forum
J
Java Code Geeks
Microsoft Azure Blog
Microsoft Azure Blog
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
Recent Commits to openclaw:main
Recent Commits to openclaw:main
C
Cisco Blogs
AWS News Blog
AWS News Blog
cs.AI updates on arXiv.org
cs.AI updates on arXiv.org
Scott Helme
Scott Helme
D
Darknet – Hacking Tools, Hacker News & Cyber Security
I
InfoQ
U
Unit 42

Megaport Blog

Early Warning Signs Your Network Needs a Refresh Introducing Megaport DDoS Protection A Guide to 400G Connectivity A Guide to NAT Gateway A Guide to Cloud Storage How the Data Center Is Evolving in 2026 What to Expect When Attending Your First Network Operator Group (NOG) Nine Ways to Connect to Cloud Using Private Connectivity Migrate Your On-premises to the Cloud: A Step-by-Step Guide How to Lower Your Egress Fees in 2026 How to Achieve Data Sovereignty in Europe Redefining the Edge with Cisco and Megaport How to Reduce Latency in Your Multicloud Environment Introducing Megaport High-Speed Cross-Cloud Encryption Are Businesses Leaving the Cloud? Using Meraki and Megaport Virtual Edge for Multicloud Networking Equinix Metal® is Going Away: Here’s What You Can Do Introducing Megaport On-ramp as a Service Megaport’s Full Solution Portfolio Is Coming to India New Bare-metal GPU Instance Now Available with NVIDIA RTX Pro 6000 A Look Back at 2025: Megaport's Biggest Updates Megaport Expands Into India With Extreme IX Your 2026 Predictions From AWS re:Invent 2025 Top NaaS Trends for 2026 What is IPsec? When to Move From Public Internet to Private Connectivity Megaport and Latitude.sh: Bringing Compute and Connectivity Together Improve Your Microsoft ExpressRoute Resilience with Megaport Comparing Ways to Connect to AWS What is API-First Networking? The Hidden Cost of Running Cloud-Hosted SD-WAN for IaaS Overcoming NaaS Integration Challenges Introducing SCION with Anapaya and Megaport How to Use Network as a Service to Future-Proof Your Network Introducing 400G Ports All the As-a-services, Compared Introducing Megaport IPsec Tunnels High Score: Megaport Hits 1,000 Locations A Guide to Colocation Data Centers Maximizing Peering Through Flow Analysis Build Resilient Networks for AI Production Workloads Introducing Packet Filtering on Megaport Cloud Router Building Resilient Government IT: Strategies for Secure, Compliant, and Scalable Connectivity Future-Proofing Government IT Telstra Programmable Network Is Being Discontinued. Here’s How to Migrate The Future of WAN Design Depends on Network as a Service (NaaS) Cisco Webex Edge Connect Launches on Megaport Voice and Video Exchange How to Prepare for APRA CPS 230 Comparing the SD-WAN Licensing Needs of Major Vendors A Guide to Improving Network Performance How Latitude.sh, Wasabi, and Megaport Unlock Cost-Effective Multicloud Four Ways to Connect Your Clouds SD-WAN and MPLS: Weighing the Similarities, Differences, and Benefits A Guide to Network as a Service (NaaS) How to Arrange Bilateral Peering Sessions Comparing Major SD-WAN Vendors Software Defined Networking in Healthcare Deploying A Global Network in Minutes With Megaport AWS Direct Connect Gateway (DGW) Data Transfer Outbound Rules Bilateral and Multilateral Peering: What’s the Difference? Multi-Region SD-WAN: Why Megaport SDCI is the Right Choice Microsoft Azure is Going Secure by Default. Are You Ready? How Megaport and Vultr Are Solving the Enterprise AI Challenge Introducing Megaport NAT Gateway A Guide to AWS Security Tools How to Deploy Amazon Bedrock Using AWS Direct Connect and Megaport Azure Private Link, Explained Introducing 100G MCRs Simplifying Hybrid and Multicloud Network Connectivity How to Fix Poor AWS Latency A Look Back at 2024: Megaport’s Biggest Updates Your 2025 Predictions From AWS re:Invent 2024 Six Ways to Get a More Resilient Network in 2025 Multicloud Security: Challenges and Solutions The Real Cost of High Network Latency Why Brazil is Your Key to Unlocking Business Growth in Latin America Why You Need Integrated Network Security Six Key Differences Between Major Cloud Providers How to Automate Your Megaport Infrastructure With APIs Why Italy is Europe’s Next Cloud Expansion Hotspot How to Lower Your Cloud Costs Introducing Megaport AI Exchange Two Scenarios for Hybrid Multicloud Deployment With IBM Cloud and Microsoft Azure How to Connect Equinix and Digital Realty Megaport Enables Microsoft Azure ExpressRoute Metro for More Resilient Network Connectivity Executives, Here’s What Your Network Team Wants You to Know Easy Ways to Interconnect Your Network The Role of the Data Center in Your Network 100G VXC Expansion: Now Available From 597 Data Centers Worldwide Top 10 How-To Guides To Improve Your Network Comparing Encryption in Transit Options Comparing Generative AI Offerings From Major Cloud Providers A Sustainable Business Strategy Starts With Your Network Solutions to Common API Issues With Megaport Transforming Financial Connectivity: Introducing Megaport Financial Services Exchange (FSX) Megaport Enhancing Connectivity in Adelaide Megaport’s Latest Portal Features and Functionalities Automate Your Network Deployments With The New Megaport Terraform Provider A Recap of the Megaport World Tour 2024 Top 5 Cloud and Networking Announcements From Cisco Live 2024
Peering: How Local Is Local?
2024-10-02 · via Megaport Blog

By Rob Parker, Interconnection Director

Optimize network performance by ensuring both you and your peers are locally connected.

When it comes to Internet Exchanges (IXs), there are two types of peering: local peering and remote peering. And depending on your network setup and goals, the type you use can have a significant impact on your network performance.

While remote peering has valuable use cases, we often see customers using it in scenarios where it is actually doing more harm than good to their network performance. Below, we compare local peering and remote peering so you can choose the right method for your business.

Choosing an IX

Typically, when selecting an IX, your priorities might include:

  • which IX has the most networks
  • the highest volume of traffic
  • identifying specific networks to reduce transit use.

Whatever metric you use to make your decision, the ultimate goal is to increase performance, which requires each present network to operate equipment that is physically located in the same metro area as the IX. This is a common assumption to make, but is it always the case?

About local peering

The mantra of “keep traffic local” is often touted as a key reason to join an IX, and for good reason.

One of the most valuable reasons to peer at an Internet Exchange (IX) is to improve performance by reducing latency and ensuring traffic is exchanged between your networks as expeditiously as possible. Peering at an IX achieves this by ensuring all participants have access to each other within a local fabric, available across a number of data centers within a metro area.

To achieve these performance improvements, the coverage of an IX remains within a single metro area – perhaps a single city (such as Frankfurt or Sydney) or small group of cities in close proximity with each other (such as New York and New Jersey, or the San Francisco Bay Area). With this sort of geographic coverage, participants would typically be within approximately 50-100 miles (80-160km) of each other at most, and at the speed of light, fractions of a millisecond apart.

The low-latency interconnection of a single-metro IX enables higher throughput, faster response times, and less dependence on a transit provider and the wider internet – so less potential for problems like packet loss or routing issues. To end users, of course, this manifests as valuable improvements like faster website loading times, seamless content streaming, and more responsive online gaming.

About remote peering

The alternative to local peering is remote peering: when a network connects to an IX in a different metro area to their equipment, perhaps using some form of third-party provider to reach the IX. Sometimes the IX itself may offer a remote peering product.

There are many valid reasons a network might choose to remotely connect to an IX, for example:

  • they are present in an adjacent city with no IX
  • they have valuable traffic to exchange with a specific peer
  • they wish to increase geographic reach to pick up new customers
  • they wish to connect in another geography to avoid expensive local transit providers.

This of course poses no issue for the IX, or the network that is remotely connected, since they are fully aware of the latency between their equipment and the IX. But what impact does this have on other peers at the IX who may not be aware that this new peer is actually located some distance away?

The most immediate effect of this setup will be impaired throughput and latency. But remote connectivity to an IX may also introduce single points of failure that are completely invisible to all connected networks until a problem occurs, making one of the main benefits of peering at an IX redundant. This is the major reason Megaport encourages peering at more than one IX per metro area.

Digital cyberspace

How to peer for optimal performance

When joining an IX, it is important to identify which networks are essential to you—that is, which ones you’ll exchange the highest volume or most valuable traffic with—and where their equipment is in relation to yours.

You can often determine this information using tools like PeeringDB or bgp.tools, or a looking glass with ping capabilities such as that provided by Hurricane Electric or RIPE. Some IXs may also make this information easily accessible in their looking glass, too.

Identifying the latency or distance between your network and the peer you’re interested in exchanging traffic with is essential, as this will directly influence the throughput (and potentially the quality) of interconnection.

In summary, when selecting your next IX, we suggest following this simple process:

  1. Identify your most important flows and volumes, and find IXs where they are present.
  2. Use publicly available tools to determine latency between the IX and the networks that are most important to you.
  3. If you’re still unsure which participants are local and which are remote, ask the IX operator or remote network for more information.
  4. If the traffic exchanged via an IX is business-critical and you’re able to connect to more than one IX, it’s a great idea to do so.
  5. If you require a remote connection to an IX, talk to your remote peering provider and ask them about single points of failure and network resilience.

Get personalized guidance on your peering setup and discover how MegaIX can help. Book a chat with our friendly team.

Learn more about MegaIX