asn.dev

Observed topology

AS26431 HAPPYPEERING

Hosting ARIN

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

Transit

Upstream networks

All 12

Networks observed carrying traffic for AS26431: 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 IPv646
AS42000Futruy s.r.o.UnclassifiedIPv441
AS34872Sarah Rossius trading as Servperso SystemsHostingIPv636
AS24482SG.GSHostingIPv4 IPv63
AS29504Freenet Liberec, z.s.UnclassifiedIPv4 IPv62
AS1764Next Layer Telekommunikationsdienstleistungs- und Beratungs GmbHUnclassifiedIPv41
AS8218Zayo Infrastructure France SAUnclassifiedIPv41
AS20562Broadband Hosting B.V.HostingIPv41
AS33891Core-Backbone GmbHHostingIPv41
AS37721Virtual Technologies & SolutionsResidentialIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS50833FIBER TELECOM s.r.o.ResidentialIPv4 IPv6188

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS42000Futruy s.r.o.UnclassifiedIPv4 IPv6191
AS50833FIBER TELECOM s.r.o.ResidentialIPv4 IPv6188
AS6939Hurricane Electric LLCTransitIPv4 IPv666
AS34872Sarah Rossius trading as Servperso SystemsHostingIPv636
AS24482SG.GSHostingIPv4 IPv67
AS29504Freenet Liberec, z.s.UnclassifiedIPv4 IPv66
AS1764Next Layer Telekommunikationsdienstleistungs- und Beratungs GmbHUnclassifiedIPv43
AS8218Zayo Infrastructure France SAUnclassifiedIPv43
AS20562Broadband Hosting B.V.HostingIPv43
AS33891Core-Backbone GmbHHostingIPv43

Provenance

Where this comes from

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