asn.dev

Observed topology

AS2818 BBC BBC Internet Services, UK

Hosting RIPE

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

Transit

Upstream networks

All 25

Networks observed carrying traffic for AS2818: 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 IPv677
AS1299Arelion Sweden ABTransitIPv4 IPv665
AS6939Hurricane Electric LLCTransitIPv4 IPv665
AS9002RETN LimitedUnclassifiedIPv4 IPv621
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv614
AS33891Core-Backbone GmbHHostingIPv48
AS24482SG.GSHostingIPv4 IPv67
AS29169GANDI SASHostingIPv4 IPv67
AS42708Glesys ABUnclassifiedIPv4 IPv67
AS48185team.blue NVUnclassifiedIPv4 IPv67

All 25 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 25

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv677
AS1299Arelion Sweden ABTransitIPv4 IPv665
AS6939Hurricane Electric LLCTransitIPv4 IPv665
AS9002RETN LimitedUnclassifiedIPv4 IPv621
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv614
AS33891Core-Backbone GmbHHostingIPv48
AS24482SG.GSHostingIPv4 IPv67
AS29169GANDI SASHostingIPv4 IPv67
AS42708Glesys ABUnclassifiedIPv4 IPv67
AS48185team.blue NVUnclassifiedIPv4 IPv67

All 25 adjacent →

Provenance

Where this comes from

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