asn.dev

Observed topology

AS12502 NEPUSTILNET-AS01 Rathausstr. 3

Residential RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS12502: 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
AS5405Inter.link GmbHUnclassifiedIPv4 IPv6240
AS1299Arelion Sweden ABTransitIPv4 IPv6188
AS33891Core-Backbone GmbHHostingIPv46

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS203132SySS GmbHUnclassifiedIPv4 IPv6222
AS49499Industrie und Handelskammer ReutlingenUnclassifiedIPv470
AS43910Intra2net AGUnclassifiedIPv453
AS198818ISP Service eGUnclassifiedIPv4 IPv642
AS206394CeGaT GmbHUnclassifiedIPv4 IPv642
AS209846SWP Stadtwerke Pforzheim GmbH & Co. KGUnclassifiedIPv414

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS5405Inter.link GmbHUnclassifiedIPv4 IPv6663
AS203132SySS GmbHUnclassifiedIPv4 IPv6222
AS1299Arelion Sweden ABTransitIPv4 IPv6188
AS49499Industrie und Handelskammer ReutlingenUnclassifiedIPv470
AS43910Intra2net AGUnclassifiedIPv453
AS198818ISP Service eGUnclassifiedIPv4 IPv642
AS206394CeGaT GmbHUnclassifiedIPv4 IPv642
AS33843Dr.-Ing. Nepustil & Co. GmbH Internet Service Center Ingenieurgesellschaft fuer Systemsoftware und KommunikationstechnikUnclassifiedIPv4 IPv619
AS209846SWP Stadtwerke Pforzheim GmbH & Co. KGUnclassifiedIPv414
AS33891Core-Backbone GmbHHostingIPv47

Provenance

Where this comes from

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