asn.dev

Observed topology

AS201838 ASN-COMMUNITYFIBRE Community Fibre Limited

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

All 21

Networks observed carrying traffic for AS201838: 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
AS3356Level 3 Parent, LLCTransitIPv4 IPv61,670
AS2914NTT America, Inc.TransitIPv4 IPv61,387
AS6939Hurricane Electric LLCTransitIPv4 IPv6836
AS34549meerfarbig GmbH & Co. KGHostingIPv4303
AS33891Core-Backbone GmbHHostingIPv4202
AS50304Blix Solutions ASUnclassifiedIPv4202
AS24482SG.GSHostingIPv4 IPv6103
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv6103
AS48185team.blue NVUnclassifiedIPv4 IPv6103
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv6103

All 21 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS210874Box Broadband LimitedResidentialIPv4 IPv6261

Adjacency

Adjacent networks

All 22

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv61,670
AS2914NTT America, Inc.TransitIPv4 IPv61,535
AS6939Hurricane Electric LLCTransitIPv4 IPv6868
AS34549meerfarbig GmbH & Co. KGHostingIPv4315
AS210874Box Broadband LimitedResidentialIPv4 IPv6261
AS33891Core-Backbone GmbHHostingIPv4210
AS50304Blix Solutions ASUnclassifiedIPv4210
AS24482SG.GSHostingIPv4 IPv6108
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv6108
AS48185team.blue NVUnclassifiedIPv4 IPv6108

All 22 adjacent →

Provenance

Where this comes from

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