Peering
Interconnect with Wirescope
We are a carrier-dense, deliberately small network: 3 core locations, full BGP control on every port, and DDoS mitigation applied inline rather than in a scrubbing centre somewhere else. Shorter paths for your users, and one fewer network between you and the traffic you care about.
Network details
| ASN | TBD |
|---|---|
| AS-SET | TBD |
| Peering policy | TBD |
| Max prefix (IPv4) | TBD |
| Max prefix (IPv6) | TBD |
| PeeringDB | TBD |
| Contacts |
Values shown in grey are being finalised ahead of launch. Email peering@wirescope.net and we will send the current details directly.
Where you can reach us
Cross-connects, private interconnects, and exchange ports in carrier-neutral facilities. Each location page lists the exact buildings and the transit carriers present.
What we ask of peers
A current PeeringDB record
It is how we size sessions, find your NOC, and confirm where you are present. Keep it accurate and we will do the same.
RPKI ROAs and IRR objects
Register your prefixes. We validate with RPKI and build filters from IRR data, so anything unregistered will not be accepted.
Announce only your own and your customers' routes
No default, no pointing static routes at us, and no transit through the peering session in either direction.
A NOC that answers
A monitored role address and an escalation path that works at 03:00, because that is usually when it matters.
What we do in return
We filter what we accept
Prefix filters built from IRR data, RPKI route origin validation, and max-prefix limits on every session. Invalids are rejected, not de-preferenced.
We announce a consistent set
Our own prefixes and those of our customers, with consistent origin and no leaks toward peers. MANRS-aligned practice on every port.
Route optimization is available to you
The BGP communities our customers use for prepending, regional steering, and blackholing are documented and supported, not internal-only.
Attack traffic is our problem, not yours
Hostile traffic destined for a protected customer is filtered at our edge. Peering with us should not turn your ports into somebody else's flood.
Set up a session
Send your ASN, the facilities or exchanges where you would like to connect, and your expected traffic profile. If you are looking for transit rather than settlement-free peering, our IP transit page covers ports, pricing, and BGP communities.