asn.dev

Observed topology

AS203489 WIMORE

Residential APNIC Cable/DSL/ISP

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

Transit

Upstream networks

All 28

Networks observed carrying traffic for AS203489: 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
AS1299Arelion Sweden ABTransitIPv4 IPv6115
AS9002RETN LimitedUnclassifiedIPv4 IPv676
AS6939Hurricane Electric LLCTransitIPv4 IPv646
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv619
AS34549meerfarbig GmbH & Co. KGHostingIPv418
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv67
AS24482SG.GSHostingIPv4 IPv67
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv67
AS48185team.blue NVUnclassifiedIPv4 IPv67
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv67

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS214169Cloudfire s.r.l.UnclassifiedIPv430

Adjacency

Adjacent networks

All 29

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv6127
AS9002RETN LimitedUnclassifiedIPv4 IPv685
AS6939Hurricane Electric LLCTransitIPv4 IPv646
AS214169Cloudfire s.r.l.UnclassifiedIPv430
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv619
AS34549meerfarbig GmbH & Co. KGHostingIPv418
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv610
AS59919Brainbox S.r.l.ResidentialIPv49
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv67
AS24482SG.GSHostingIPv4 IPv67

Provenance

Where this comes from

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