Interconnection notes

Peering, BGP, edge infrastructure and network security — written by the people building Peer1IX.

Many regional networks wait too long to start peering. These seven signals tell you when an exchange port will pay for itself.

Interconnect capacity for cloud security services must handle normal traffic and attack scenarios. How to size it.

When a tunnel will not come up or traffic stalls, these are the usual suspects.

Moving firewall functions to a service is a significant change. A phased approach reduces risk.

The worst time to plan a DDoS response is during an attack. What to put in your runbook so the team knows exactly what to do.

Some connections are only needed for weeks. Virtual cross connects make short-term private links practical.

Moving from a 10G to a 100G port is routine — if you plan it. A step-by-step approach that keeps traffic flowing.

NAT capacity is not just bandwidth. Sessions, ports per subscriber and address pools all need planning.

Bringing your own licence to a virtual edge platform keeps your tooling and policies consistent. What to check before you deploy.

A virtual router can be more resilient than a physical one — if the design uses redundancy at every layer. What to configure.

Overlapping address space is one of the most common problems when connecting clouds. How to prevent it, and what to do when it happens.

Banks, insurers and fintechs adopting cloud need connectivity that satisfies risk teams as well as engineers. Key considerations.