asn.dev

Observed topology

AS6881 NIXCZ NIX.CZ z.s.p.o.

Unclassified RIPE

Upstreams 7 carry this network
Downstreams 4 this network carries
Adjacent (IPv4) 11
Adjacent (IPv6) 8
Upstream graph Who carries AS6881, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS6881 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS6881: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv649
AS29208Quantcom, a.s.UnclassifiedIPv4 IPv643
AS15685CASABLANCA INT a.s.HostingIPv438
AS25512CD-Telematika a.s.UnclassifiedIPv418
AS29504Freenet Liberec, z.s.UnclassifiedIPv4 IPv66
AS24482SG.GSHostingIPv4 IPv63
AS8218Zayo Infrastructure France SAUnclassifiedIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS44358Kauno Technologijos UniversitetasUnclassifiedIPv4 IPv649
AS199670DNS-Belgium VZWUnclassifiedIPv4 IPv627
AS35052ACONETUnclassifiedIPv4 IPv64
AS211655PANSTWOWY INSTYTUT BADAWCZYUnclassifiedIPv4 IPv63

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6118
AS44358Kauno Technologijos UniversitetasUnclassifiedIPv4 IPv649
AS29208Quantcom, a.s.UnclassifiedIPv4 IPv645
AS15685CASABLANCA INT a.s.HostingIPv440
AS199670DNS-Belgium VZWUnclassifiedIPv4 IPv627
AS25512CD-Telematika a.s.UnclassifiedIPv418
AS29504Freenet Liberec, z.s.UnclassifiedIPv4 IPv616
AS35052ACONETUnclassifiedIPv4 IPv64
AS24482SG.GSHostingIPv4 IPv63
AS211655PANSTWOWY INSTYTUT BADAWCZYUnclassifiedIPv4 IPv63

All 11 adjacent →

Provenance

Where this comes from

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