asn.dev

Observed topology

AS12857 TDS

Unclassified RIPE

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

Transit

Upstream networks

All 13

Networks observed carrying traffic for AS12857: 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
AS21473PFALZKOM GmbHUnclassifiedIPv4 IPv643
AS34309Link11 GmbHUnclassifiedIPv4 IPv630
AS6939Hurricane Electric LLCTransitIPv48
AS34549meerfarbig GmbH & Co. KGHostingIPv43
AS6797GlobalConnect ABUnclassifiedIPv41
AS12779IT.Gate S.p.A.UnclassifiedIPv41
AS20485Joint Stock Company TransTeleComUnclassifiedIPv41
AS24482SG.GSHostingIPv41
AS34019Hivane AssociationUnclassifiedIPv41
AS37100SEACOM LimitedUnclassifiedIPv41

All 13 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS49097Manage Now GmbHHostingIPv4531

Adjacency

Adjacent networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS49097Manage Now GmbHHostingIPv4531
AS34309Link11 GmbHUnclassifiedIPv4 IPv6259
AS21473PFALZKOM GmbHUnclassifiedIPv4 IPv6175
AS6939Hurricane Electric LLCTransitIPv471
AS34549meerfarbig GmbH & Co. KGHostingIPv430
AS12779IT.Gate S.p.A.UnclassifiedIPv410
AS20485Joint Stock Company TransTeleComUnclassifiedIPv410
AS24482SG.GSHostingIPv410
AS34019Hivane AssociationUnclassifiedIPv410
AS37100SEACOM LimitedUnclassifiedIPv410

All 15 adjacent →

Provenance

Where this comes from

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