A dedicated contact for Exascale peering
You may start seeing a new name in emails from our peering team.
We’re introducing Alex Morgan as the correspondence name for Exascale’s dedicated peering and interconnection coordination. It gives our network partners a regular point of contact for new requests, session turn-ups and routing queries.
As Exascale grows, we’re carrying traffic for more downstream networks alongside our own business and residential customers. We want to make sure the connections supporting those services continue to get the attention they need.
That means finding suitable networks to peer with, extending existing arrangements where useful and following agreed changes through to completion.
Following things through
There can be quite a bit of coordination between agreeing to peer and having everything working on both sides.
Addresses, prefix limits and authentication settings need to be confirmed. Sessions need to be configured and checked. Once they’re up, we also need to make sure we’re exchanging the routes we expect.
Alex will help keep track of that work and give other networks a consistent contact throughout the process.
We’re also reviewing existing peering. Where traffic continues to use transit despite a direct connection being available, we want to understand why. Sometimes that comes down to routing policy, filtering or the locations involved. Adding another session isn’t always the answer.
Making use of all our connections
Where we have more than one connection to a peering LAN, we want the agreed sessions to cover each of them.
For example, if Exascale has two connections at an exchange, we ask peers to configure IPv4 and IPv6 sessions to both. We’ll do the same for each of their agreed connections.
This applies across all our peering LANs. It helps us avoid arrangements where one connection is working while another is still waiting to be configured.
Happy to discuss peering
We’re always happy to hear from networks interested in peering with Exascale, extending an existing arrangement or looking into a routing issue together.
You can reach the team at [email protected]. Our current exchange addresses and peering details are on PeeringDB.