Observed topology
AS48314 IP-PROJECTS
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS48314: 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 |
|---|---|---|---|---|
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 1,633 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 IPv6 | 1,475 |
| AS6453 | TATA COMMUNICATIONS (AMERICA) INC | Transit | IPv4 | 844 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 786 |
| AS5405 | Inter.link GmbH | Unclassified | IPv4 IPv6 | 656 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 438 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 415 |
| AS62403 | PletX GmbH | Unclassified | IPv4 | 236 |
| AS5511 | Orange S.A. | Transit | IPv4 | 188 |
| AS3320 | Deutsche Telekom AG | Mobile | IPv4 IPv6 | 76 |
Transit
Downstream networks
Networks for which AS48314 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS216188 | Bieber IT GmbH | Unclassified | IPv4 IPv6 | 669 |
| AS149440 | Evoxt Sdn. Bhd. | Unclassified | IPv4 IPv6 | 454 |
| AS199959 | GWY IT PTY LTD | Unclassified | IPv4 IPv6 | 394 |
| AS402931 | AdaptGroup | Unclassified | IPv4 IPv6 | 274 |
| AS60150 | area-7 IT-Services GmbH | Unclassified | IPv4 IPv6 | 254 |
| AS213386 | Jonathan Broering | Unclassified | IPv6 | 136 |
| AS200303 | LUMASERV GmbH | Unclassified | IPv4 IPv6 | 130 |
| AS215767 | Mizban Pardazesh Pouyan LLC | Unclassified | IPv4 IPv6 | 95 |
| AS211525 | innoVee GmbH | Unclassified | IPv4 IPv6 | 94 |
| AS216063 | 24fire GmbH | Unclassified | IPv4 IPv6 | 81 |
Adjacency
Adjacent networks
Every AS seen directly next to AS48314 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 IPv6 | 2,348 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 2,282 |
| AS6453 | TATA COMMUNICATIONS (AMERICA) INC | Transit | IPv4 IPv6 | 1,056 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 1,021 |
| AS5405 | Inter.link GmbH | Unclassified | IPv4 IPv6 | 914 |
| AS216188 | Bieber IT GmbH | Unclassified | IPv4 IPv6 | 669 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 632 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 555 |
| AS149440 | Evoxt Sdn. Bhd. | Unclassified | IPv4 IPv6 | 454 |
| AS199959 | GWY IT PTY LTD | Unclassified | IPv4 IPv6 | 394 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-14 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.25M 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.