asn.dev

Observed topology

AS25557 PKE-AS TAURON WYTWARZANIE SPOLKA AKCYJNA

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS25557: 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
AS15694Atman Sp. z o.o.ResidentialIPv4104
AS20804Exatel S.A.UnclassifiedIPv414

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS31306TAURON Obsluga Klienta Sp. z o.o.UnclassifiedIPv4420
AS51772TAURON Dystrybucja S.A.UnclassifiedIPv460
AS29254TAURON Dystrybucja S.A.UnclassifiedIPv459
AS34637TAURON Dystrybucja S.A.UnclassifiedIPv459
AS34902TAURON Dystrybucja S.A.UnclassifiedIPv459
AS41137TAURON Dystrybucja S.A.UnclassifiedIPv459
AS30730TAURON Dystrybucja S.A.UnclassifiedIPv41

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS20804Exatel S.A.UnclassifiedIPv4432
AS31306TAURON Obsluga Klienta Sp. z o.o.UnclassifiedIPv4420
AS15694Atman Sp. z o.o.ResidentialIPv4294
AS30730TAURON Dystrybucja S.A.UnclassifiedIPv483
AS51772TAURON Dystrybucja S.A.UnclassifiedIPv460
AS29254TAURON Dystrybucja S.A.UnclassifiedIPv459
AS34637TAURON Dystrybucja S.A.UnclassifiedIPv459
AS34902TAURON Dystrybucja S.A.UnclassifiedIPv459
AS41137TAURON Dystrybucja S.A.UnclassifiedIPv459
AS6939Hurricane Electric LLCTransitIPv425

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.