Observed topology
AS24875 NOVOSERVE-AS
Hosting RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS24875: 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 |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 69 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 66 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 64 |
| AS5405 | Inter.link GmbH | Unclassified | IPv4 | 60 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 | 31 |
| AS2914 | NTT America, Inc. | Transit | IPv4 | 30 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 | 28 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 IPv6 | 12 |
| AS34872 | Sarah Rossius trading as Servperso Systems | Hosting | IPv4 IPv6 | 10 |
| AS56655 | Gigahost AS | Unclassified | IPv4 IPv6 | 10 |
Transit
Downstream networks
Networks for which AS24875 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS204601 | NovoServe B.V. | Unclassified | IPv4 IPv6 | 8,010 |
| AS211381 | Podaon SIA | Unclassified | IPv4 IPv6 | 5,640 |
| AS215224 | NovoServe B.V. | Unclassified | IPv4 IPv6 | 3,083 |
| AS218539 | Lebanese For Advanced Information Technologies (LFAIT) SARL | Unclassified | IPv4 IPv6 | 984 |
| AS211484 | YSZ TRADING CO., LIMITED | Unclassified | IPv4 | 921 |
| AS216314 | iServerHost LLC | Unclassified | IPv4 | 899 |
| AS142019 | GZ REMITTANCE (CHINA) INDUSTRY LIMITED | Unclassified | IPv4 | 660 |
| AS203144 | Host9x Web Solutions Limited | Unclassified | IPv4 | 599 |
| AS198969 | NovoServe B.V. | Unclassified | IPv4 | 598 |
| AS205009 | HDM Solutions LTD | Unclassified | IPv4 | 537 |
Adjacency
Adjacent networks
Every AS seen directly next to AS24875 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS204601 | NovoServe B.V. | Unclassified | IPv4 IPv6 | 8,010 |
| AS211381 | Podaon SIA | Unclassified | IPv4 IPv6 | 5,640 |
| AS5405 | Inter.link GmbH | Unclassified | IPv4 | 3,626 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 3,203 |
| AS215224 | NovoServe B.V. | Unclassified | IPv4 IPv6 | 3,083 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 2,851 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 2,450 |
| AS2914 | NTT America, Inc. | Transit | IPv4 | 2,320 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 1,822 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 1,611 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-23 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.15M 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.