Observed topology
AS25091 IP-Max IP-Max SA
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS25091: 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 |
|---|---|---|---|---|
| AS2914 | NTT America, Inc. | Transit | IPv4 | 161 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 147 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 | 132 |
| AS55002 | F5, Inc. | Unclassified | IPv4 | 125 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 105 |
| AS6453 | TATA COMMUNICATIONS (AMERICA) INC | Transit | IPv4 | 66 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 IPv6 | 52 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 48 |
| AS22652 | Videotron Ltee | Residential | IPv4 IPv6 | 48 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 48 |
Transit
Downstream networks
Networks for which AS25091 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS32098 | Transtelco Inc | Unclassified | IPv6 | 2,143 |
| AS197922 | Techcrea Solutions SAS | Unclassified | IPv4 IPv6 | 1,075 |
| AS21449 | Etat de Geneve | Unclassified | IPv4 IPv6 | 1,040 |
| AS56798 | HIDORA SA | Unclassified | IPv4 IPv6 | 814 |
| AS199758 | SAS Nexylan | Unclassified | IPv4 IPv6 | 607 |
| AS4134 | No.31,Jin-rong Street | Residential | IPv6 | 606 |
| AS51559 | Netinternet Bilisim Teknolojileri AS | Hosting | IPv6 | 526 |
| AS21217 | Infrastructure Switzerland Colo Sarl | Hosting | IPv4 IPv6 | 521 |
| AS61970 | Syselcom Mutuelle Informatique SA | Unclassified | IPv4 | 516 |
| AS513 | European Organization for Nuclear Research | Unclassified | IPv4 IPv6 | 504 |
Adjacency
Adjacent networks
Every AS seen directly next to AS25091 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS56662 | Marcin Gondek | Unclassified | IPv6 | 38,032 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 7,902 |
| AS4134 | No.31,Jin-rong Street | Residential | IPv6 | 5,717 |
| AS6453 | TATA COMMUNICATIONS (AMERICA) INC | Transit | IPv4 IPv6 | 5,385 |
| AS6762 | TELECOM ITALIA SPARKLE S.p.A. | Transit | IPv4 IPv6 | 4,345 |
| AS32098 | Transtelco Inc | Unclassified | IPv6 | 3,765 |
| AS34019 | Hivane Association | Unclassified | IPv4 IPv6 | 2,056 |
| AS55002 | F5, Inc. | Unclassified | IPv4 | 1,882 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 1,558 |
| AS58717 | Summit Communications Ltd | Unclassified | IPv6 | 1,436 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-11 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 73.24M 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.