asn.dev

Observed topology

AS200360 FOLF-SYSTEMS-AS Cooper Greer

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS200360: 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
AS34927iFog GmbHHostingIPv6126
AS29632Netassist International EOODUnclassifiedIPv64
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv62
AS17639Converge ICT Solutions Inc.UnclassifiedIPv62
AS24482SG.GSHostingIPv62
AS48185team.blue NVUnclassifiedIPv62
AS204092Association GRIFONUnclassifiedIPv62
AS25091IP-Max SAUnclassifiedIPv61
AS205794JINZE YANGUnclassifiedIPv61

Transit

Downstream networks

inferred

Networks for which AS200360 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 AS200360 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS34927iFog GmbHHostingIPv6126
AS29632Netassist International EOODUnclassifiedIPv64
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv62
AS17639Converge ICT Solutions Inc.UnclassifiedIPv62
AS24482SG.GSHostingIPv62
AS48185team.blue NVUnclassifiedIPv62
AS204092Association GRIFONUnclassifiedIPv62
AS25091IP-Max SAUnclassifiedIPv61
AS205794JINZE YANGUnclassifiedIPv61

Provenance

Where this comes from

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