asn.dev

Observed topology

AS35100 PatrikWeb-Core Patrik Lagerman

Unclassified APNIC Cable/DSL/ISP

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

Transit

Upstream networks

All 17

Networks observed carrying traffic for AS35100: 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
AS8473Bahnhof ABResidentialIPv4 IPv6531
AS8849Melbikomas UABHostingIPv4 IPv6130
AS34872Sarah Rossius trading as Servperso SystemsHostingIPv4 IPv686
AS35706Net at Once Sweden ABUnclassifiedIPv4 IPv682
AS63023GTHostHostingIPv4 IPv669
AS6939Hurricane Electric LLCTransitIPv4 IPv660
AS52025ParadoxNetworks LimitedUnclassifiedIPv4 IPv630
AS37989DCS1 Pte. Ltd.HostingIPv4 IPv65
AS401753BIXCE IncUnclassifiedIPv4 IPv64
AS24482SG.GSHostingIPv4 IPv63

All 17 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS218889Per BjornUnclassifiedIPv45
AS206208Pusic JuraiUnclassifiedIPv42

Adjacency

Adjacent networks

All 19

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

ASNetworkTypeFamiliesPaths seen
AS8473Bahnhof ABResidentialIPv4 IPv6536
AS8849Melbikomas UABHostingIPv4 IPv6130
AS34872Sarah Rossius trading as Servperso SystemsHostingIPv4 IPv686
AS35706Net at Once Sweden ABUnclassifiedIPv4 IPv684
AS63023GTHostHostingIPv4 IPv669
AS6939Hurricane Electric LLCTransitIPv4 IPv660
AS52025ParadoxNetworks LimitedUnclassifiedIPv4 IPv630
AS37989DCS1 Pte. Ltd.HostingIPv4 IPv65
AS218889Per BjornUnclassifiedIPv45
AS401753BIXCE IncUnclassifiedIPv4 IPv64

All 19 adjacent →

Provenance

Where this comes from

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