asn.dev

Observed topology

AS39288 VTELECOM VIRTUAL TELECOM SP. Z O.O.

Unclassified AFRINIC Cable/DSL/ISP

Upstreams 3 carry this network
Downstreams 4 this network carries
Adjacent (IPv4) 8
Adjacent (IPv6) 4
Upstream graph Who carries AS39288, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS39288 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS39288: 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.

ASNetworkTypeFamiliesPaths seen
AS62081Stowarzyszenie e-PoludnieUnclassifiedIPv4 IPv6415
AS24482SG.GSHostingIPv4 IPv67
AS201054Stowarzyszenie e-PoludnieUnclassifiedIPv46

Transit

Downstream networks

inferred

Networks for which AS39288 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS12346Maria Curie-Sklodowska UniversityUnclassifiedIPv4725
AS43962INTEN Sp. z o. o.UnclassifiedIPv4 IPv699
AS197910LUBGIP Sp. z o.o.UnclassifiedIPv466
AS42520Gmina LublinUnclassifiedIPv453

Adjacency

Adjacent networks

observed

Every AS seen directly next to AS39288 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS62081Stowarzyszenie e-PoludnieUnclassifiedIPv4 IPv61,363
AS12346Maria Curie-Sklodowska UniversityUnclassifiedIPv4758
AS43962INTEN Sp. z o. o.UnclassifiedIPv4 IPv699
AS197910LUBGIP Sp. z o.o.UnclassifiedIPv466
AS42520Gmina LublinUnclassifiedIPv453
AS24482SG.GSHostingIPv4 IPv621
AS201054Stowarzyszenie e-PoludnieUnclassifiedIPv418
AS20473The Constant Company, LLCHostingIPv61
AS56391VIRTUAL TELECOM SP. Z O.O.UnclassifiedIPv41

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-13 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.40M 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.