asn.dev

Observed topology

AS6910 DIGIBORDER

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS6910: 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 IPv644
AS3356Level 3 Parent, LLCTransitIPv4 IPv630
AS174Cogent Communications, LLCTransitIPv4 IPv616

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS8708DIGI ROMANIA S.A.MobileIPv4 IPv68,155
AS20879DIGI ROMANIA S.A.UnclassifiedIPv4 IPv6488
AS25311DIGI ROMANIA S.A.UnclassifiedIPv4 IPv6400
AS57269DIGI SPAIN TELECOM S.AUnclassifiedIPv4 IPv6203
AS61079Digi Italy S.R.L.UnclassifiedIPv4 IPv6201

Adjacency

Adjacent networks

All 38

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

ASNetworkTypeFamiliesPaths seen
AS8708DIGI ROMANIA S.A.MobileIPv4 IPv629,649
AS1299Arelion Sweden ABTransitIPv4 IPv611,525
AS3356Level 3 Parent, LLCTransitIPv4 IPv69,697
AS20879DIGI ROMANIA S.A.UnclassifiedIPv4 IPv67,254
AS6939Hurricane Electric LLCTransitIPv4 IPv64,677
AS174Cogent Communications, LLCTransitIPv4 IPv64,200
AS3741Dimension DataUnclassifiedIPv41,053
AS33891Core-Backbone GmbHHostingIPv4 IPv6906
AS24482SG.GSHostingIPv4 IPv6707
AS6797GlobalConnect ABUnclassifiedIPv4690

All 38 adjacent →

Provenance

Where this comes from

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