Wholesale AS 53292 transit, fully BGP
Single or dual-homed eBGP transit with route filtering, communities, blackhole tagging, and BFD. 30+ network partnerships globally, with direct peering at the exchanges we sit on.
A peer relationship with our network, not a port
IP Transit on AS 53292 is a full eBGP session with our network. You announce your prefixes, we carry them to the rest of the internet through 30+ network partnerships and the exchanges we sit on. We announce a full table, a partial table, or default-only back, whichever your edge router is comfortable carrying.
What separates this from a port off a cheap backbone is the routing policy and the operational practice. A documented community set for traffic engineering. RTBH for incidents. BFD where it is supported. MD5 on every session. Filtering against IRR records or an explicit prefix list you maintain. The same engineering team running it has been operating BGP networks for over twenty years.
Single-homed or dual-homed against a second port on a different fault zone. IPv4 and IPv6 from the day the session comes up.
The routing policy behind the session
Three pieces shape what the transit feels like in production.
Our autonomous system. Full eBGP, partial-table, or default-only sessions. MD5, BFD, max-prefix, and IRR filtering on every peering by default.
Network partnerships globally. A mix of direct peering at the exchanges we sit on, private interconnects to large content networks, and selective wholesale relationships.
Dual-stack from the day the session comes up. v6 is a first-class peer, not an afterthought bolted on later.
Three quick questions
The ones we get on the first call. If yours is not here, the answer is on the other end of the phone.
What does your peering footprint actually look like?
30+ network partnerships globally. A mix of direct peering at the major exchanges where we have a presence, private interconnects to large content and cloud networks, and selective wholesale relationships with backbones whose routes converge better than the cheapest path. The full list goes out under NDA when a specific build calls for it. The public portion is visible on the AS 53292 IRR record.
How do you handle BGP hygiene?
MD5 session authentication on every BGP session by default. BFD with vendor-supported timers for sub-second convergence where the platform supports it. Inbound and outbound prefix filtering against IRR records or an explicit list you maintain. Max-prefix limits with reasonable reset thresholds. AS-path filtering on transit. Source-address validation per BCP38. ASN, MD5 keys, BFD timers, and max-prefix get exchanged in writing before turn-up. RPKI ROV posture is shared on request.
Do you support community-based traffic engineering and blackholing?
Yes. A documented community set lets you signal preferences on a per-prefix basis: prepending toward specific upstreams, no-export to particular peers, geographic scoping. A blackhole community is available for source or destination RTBH when an attack is in progress. The community list is in the peering doc you receive before turn-up.
Tell us your ASN, we will quote the session
ASN, prefix list, expected v4 and v6 volumes, single or dual-homed, where you want to land. We will send the peering doc with community list and policy details.
Get in Touch