Observed topology
AS48399 AS-LINXDATACENTER
Unclassified RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS48399: 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 |
|---|---|---|---|---|
| AS3327 | CITIC Telecom CPC Netherlands B.V. | Unclassified | IPv4 IPv6 | 576 |
| AS9049 | JSC "ER-Telecom Holding" | Unclassified | IPv4 IPv6 | 236 |
| AS6939 | Hurricane Electric LLC | Transit | IPv6 | 16 |
| AS20764 | CJSC RASCOM | Unclassified | IPv6 | 13 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv6 | 2 |
| AS24482 | SG.GS | Hosting | IPv6 | 2 |
| AS34019 | Hivane Association | Unclassified | IPv6 | 2 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv6 | 2 |
| AS48185 | team.blue NV | Unclassified | IPv6 | 2 |
| AS48362 | Stadtwerke Feldkirch | Residential | IPv6 | 2 |
Transit
Downstream networks
Networks for which AS48399 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS199136 | DELTA LLC | Unclassified | IPv4 | 77 |
| AS198117 | KORUS Consulting Group LLC | Unclassified | IPv4 | 61 |
| AS198712 | JSC Intervale | Unclassified | IPv4 | 61 |
| AS205221 | SBERKORUS LLC | Unclassified | IPv4 | 61 |
| AS203714 | LLC Flex | Unclassified | IPv4 | 40 |
| AS50523 | LLC NPP "Itelma" | Unclassified | IPv4 | 14 |
| AS58194 | LLC Avtokonneks | Unclassified | IPv4 | 14 |
| AS214540 | LTD "Payment service provider" | Unclassified | IPv4 | 14 |
| AS210491 | OOO Quantek | Unclassified | IPv4 | 12 |
| AS51981 | PJSC Finstar Bank | Unclassified | IPv4 | 11 |
Adjacency
Adjacent networks
Every AS seen directly next to AS48399 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3327 | CITIC Telecom CPC Netherlands B.V. | Unclassified | IPv4 IPv6 | 765 |
| AS9049 | JSC "ER-Telecom Holding" | Unclassified | IPv4 IPv6 | 287 |
| AS199136 | DELTA LLC | Unclassified | IPv4 | 93 |
| AS198117 | KORUS Consulting Group LLC | Unclassified | IPv4 | 61 |
| AS198712 | JSC Intervale | Unclassified | IPv4 | 61 |
| AS205221 | SBERKORUS LLC | Unclassified | IPv4 | 61 |
| AS201706 | SERVICEPIPE LLC | Unclassified | IPv4 | 58 |
| AS59796 | StormWall s.r.o. | Unclassified | IPv4 | 51 |
| AS43298 | Storm Networks LLC | Unclassified | IPv4 | 42 |
| AS203714 | LLC Flex | Unclassified | IPv4 | 40 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-29 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.36M 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.