Observed topology
AS8896 XFIBER-AS
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS8896: 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 |
|---|---|---|---|---|
| AS12552 | GlobalConnect AB | Unclassified | IPv4 IPv6 | 597 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 588 |
| AS6453 | TATA COMMUNICATIONS (AMERICA) INC | Transit | IPv4 | 27 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 25 |
| AS34927 | iFog GmbH | Hosting | IPv4 IPv6 | 25 |
| AS57381 | Daniel Husand | Unclassified | IPv4 IPv6 | 25 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 | 19 |
| AS49788 | Nexthop AS | Unclassified | IPv4 | 12 |
| AS2116 | GLOBALCONNECT AS | Residential | IPv6 | 1 |
Transit
Downstream networks
Networks for which AS8896 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS50229 | Rignet AS | Unclassified | IPv4 | 118 |
| AS212642 | Runnane Jon Tungland | Unclassified | IPv4 IPv6 | 99 |
| AS201888 | Cegal AS | Unclassified | IPv4 IPv6 | 91 |
| AS4913 | Speedcast Communications, Inc | Unclassified | IPv4 | 76 |
| AS22717 | Halliburton Company | Unclassified | IPv4 | 59 |
| AS205238 | TIMEIT AS | Unclassified | IPv4 | 59 |
| AS213148 | Harbour Energy Norge AS | Unclassified | IPv4 | 59 |
| AS202174 | FLOW RETAIL AS | Unclassified | IPv4 | 58 |
| AS197519 | ADVANIA NORGE AS | Unclassified | IPv4 IPv6 | 55 |
| AS28824 | EMP SECURE AS | Hosting | IPv4 IPv6 | 27 |
Adjacency
Adjacent networks
Every AS seen directly next to AS8896 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS12552 | GlobalConnect AB | Unclassified | IPv4 IPv6 | 974 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 886 |
| AS50229 | Rignet AS | Unclassified | IPv4 | 118 |
| AS212642 | Runnane Jon Tungland | Unclassified | IPv4 IPv6 | 99 |
| AS201888 | Cegal AS | Unclassified | IPv4 IPv6 | 91 |
| AS4913 | Speedcast Communications, Inc | Unclassified | IPv4 | 76 |
| AS22717 | Halliburton Company | Unclassified | IPv4 | 59 |
| AS205238 | TIMEIT AS | Unclassified | IPv4 | 59 |
| AS213148 | Harbour Energy Norge AS | Unclassified | IPv4 | 59 |
| AS202174 | FLOW RETAIL AS | Unclassified | IPv4 | 58 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-16 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.23M 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.