Observed topology
AS44655 METROLINE-AS
Residential RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS44655: 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 |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 89 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 66 |
| AS50898 | MetroLine Sp. z o.o. | Unclassified | IPv4 | 20 |
| AS5617 | Orange Polska Spolka Akcyjna | Mobile | IPv4 IPv6 | 14 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 3 |
| AS24748 | Atman Sp. z o.o. | Hosting | IPv6 | 2 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 2 |
| AS201054 | Stowarzyszenie e-Poludnie | Unclassified | IPv6 | 2 |
Transit
Downstream networks
Networks for which AS44655 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS43674 | AlterTEL Sp. z o.o. | Unclassified | IPv4 | 116 |
| AS50366 | AlterTEL Sp. z o.o. | Unclassified | IPv4 | 60 |
| AS51203 | BM5 Bartosz Malinowski | Unclassified | IPv4 | 58 |
| AS203356 | ebox.pl Sp. z o.o. | Unclassified | IPv4 | 57 |
| AS51146 | Asean Telecom Sp. z o.o. | Unclassified | IPv4 | 47 |
| AS61171 | HEXA OPERATOR SP. Z O.O. | Unclassified | IPv4 | 36 |
| AS57897 | Mobitex Telecom Sp z o.o. | Unclassified | IPv4 | 9 |
| AS198467 | CENTRUM WSPARCIA BIZNESU NOT Sp. z o.o. | Unclassified | IPv4 | 2 |
Adjacency
Adjacent networks
Every AS seen directly next to AS44655 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 243 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 215 |
| AS43674 | AlterTEL Sp. z o.o. | Unclassified | IPv4 | 116 |
| AS50366 | AlterTEL Sp. z o.o. | Unclassified | IPv4 | 60 |
| AS5617 | Orange Polska Spolka Akcyjna | Mobile | IPv4 IPv6 | 58 |
| AS51203 | BM5 Bartosz Malinowski | Unclassified | IPv4 | 58 |
| AS203356 | ebox.pl Sp. z o.o. | Unclassified | IPv4 | 57 |
| AS51146 | Asean Telecom Sp. z o.o. | Unclassified | IPv4 | 47 |
| AS61171 | HEXA OPERATOR SP. Z O.O. | Unclassified | IPv4 | 36 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 28 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-20 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.16M 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.