asn.dev

Observed topology

AS61228 64b22a8bb6ab181373c78aa1d1d42cd07844d95e

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS61228: 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
AS63473HostHatch, LLCUnclassifiedIPv6104
AS26042FiberState, LLCHostingIPv4 IPv6102
AS3204xTom OUHostingIPv676
AS56655Gigahost ASUnclassifiedIPv639
AS32595Liberally Network, LLCResidentialIPv637
AS398465Rackdog, LLCResidentialIPv637
AS153371BACK WAVES LIMITEDResidentialIPv635
AS152918Liberally Network LLCUnclassifiedIPv631

Transit

Downstream networks

inferred

Networks for which AS61228 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

observed

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

ASNetworkTypeFamiliesPaths seen
AS63473HostHatch, LLCUnclassifiedIPv6104
AS26042FiberState, LLCHostingIPv4 IPv6102
AS3204xTom OUHostingIPv676
AS56655Gigahost ASUnclassifiedIPv639
AS32595Liberally Network, LLCResidentialIPv637
AS398465Rackdog, LLCResidentialIPv637
AS153371BACK WAVES LIMITEDResidentialIPv635
AS152918Liberally Network LLCUnclassifiedIPv631

Provenance

Where this comes from

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