asn.dev

Observed topology

AS198057 FLOOYD

Residential RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS198057: 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
AS20473The Constant Company, LLCHostingIPv6303
AS214762Sebastian Stefanek trading as MatHost.euHostingIPv4 IPv6222
AS11967Hop179 OUUnclassifiedIPv678
AS28186ITS TELECOMUNICACOES LTDAUnclassifiedIPv461
AS835GoCodeIT IncUnclassifiedIPv627
AS214331TESKE VIRTUAL SYSTEM LTDAUnclassifiedIPv4 IPv621
AS58057Securebit AGUnclassifiedIPv620
AS37989DCS1 Pte. Ltd.HostingIPv610
AS205794JINZE YANGUnclassifiedIPv63
AS267564FIBER TELECOM - TELECOMUNICACAO DE DADOSUnclassifiedIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS50763Robert McKayUnclassifiedIPv459

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS20473The Constant Company, LLCHostingIPv6307
AS214762Sebastian Stefanek trading as MatHost.euHostingIPv4 IPv6222
AS214331TESKE VIRTUAL SYSTEM LTDAUnclassifiedIPv4 IPv680
AS11967Hop179 OUUnclassifiedIPv678
AS28186ITS TELECOMUNICACOES LTDAUnclassifiedIPv461
AS50763Robert McKayUnclassifiedIPv459
AS835GoCodeIT IncUnclassifiedIPv627
AS58057Securebit AGUnclassifiedIPv622
AS37989DCS1 Pte. Ltd.HostingIPv612
AS205794JINZE YANGUnclassifiedIPv63

All 11 adjacent →

Provenance

Where this comes from

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