Observed topology
AS51088 A2B A2B IP B.V.
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS51088: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS8455 | atom86 BV | Hosting | IPv4 IPv6 | 1,870 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 1,329 |
| AS6939 | Hurricane Electric LLC | Transit | IPv6 | 209 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 129 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 | 113 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 113 |
| AS1103 | SURF B.V. | Unclassified | IPv4 IPv6 | 74 |
| AS42708 | Glesys Sweden AB | Unclassified | IPv4 | 58 |
| AS24482 | SG.GS | Hosting | IPv6 | 19 |
| AS401753 | BIXCE Inc | Unclassified | IPv6 | 19 |
Transit
Downstream networks
Networks for which AS51088 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS202656 | Ivanov Vitaliy Sergeevich | Unclassified | IPv4 IPv6 | 2,633 |
| AS973 | Revive IT Solutions LLC | Unclassified | IPv4 | 542 |
| AS52102 | Tribion B.V. | Hosting | IPv4 IPv6 | 313 |
| AS60131 | High5! B.V. | Unclassified | IPv4 IPv6 | 272 |
| AS15562 | Job Snijders | Unclassified | IPv4 IPv6 | 255 |
| AS203919 | LUMADOCK LTD | Unclassified | IPv4 | 240 |
| AS210449 | SkyRENT B.V. | Unclassified | IPv4 IPv6 | 182 |
| AS35027 | SEVENP B.V. | Unclassified | IPv4 | 180 |
| AS12902 | Ekco B.V. | Unclassified | IPv4 IPv6 | 143 |
| AS24642 | Caveo Internet BV | Hosting | IPv4 IPv6 | 109 |
Adjacency
Adjacent networks
Every AS seen directly next to AS51088 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS8455 | atom86 BV | Hosting | IPv4 IPv6 | 5,471 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 3,020 |
| AS202656 | Ivanov Vitaliy Sergeevich | Unclassified | IPv4 IPv6 | 2,633 |
| AS973 | Revive IT Solutions LLC | Unclassified | IPv4 | 542 |
| AS52102 | Tribion B.V. | Hosting | IPv4 IPv6 | 313 |
| AS6939 | Hurricane Electric LLC | Transit | IPv6 | 304 |
| AS60131 | High5! B.V. | Unclassified | IPv4 IPv6 | 281 |
| AS15562 | Job Snijders | Unclassified | IPv4 IPv6 | 255 |
| AS203919 | LUMADOCK LTD | Unclassified | IPv4 | 240 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 IPv6 | 229 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-13 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.40M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.
Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.
Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.