asn.dev

Observed topology

AS207713 GIR-AS GLOBAL INTERNET SOLUTIONS LLC

Hosting Spamhaus ASN-DROP RIPE Content

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS207713: 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
AS35598INETCOM CARRIER LLCUnclassifiedIPv4 IPv61,007
AS57494Adman LLCUnclassifiedIPv4671
AS203493Egor TimoshenkoHostingIPv4 IPv6450
AS49542ArtPlanet LLCUnclassifiedIPv4 IPv6101
AS62255BiMajLink d.o.o.UnclassifiedIPv624
AS63023GTHostHostingIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS149457Angel cloud LimitedUnclassifiedIPv4696

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS35598INETCOM CARRIER LLCUnclassifiedIPv4 IPv61,007
AS60798Servereasy SrlHostingIPv4696
AS149457Angel cloud LimitedUnclassifiedIPv4696
AS57494Adman LLCUnclassifiedIPv4671
AS203493Egor TimoshenkoHostingIPv4 IPv6450
AS49542ArtPlanet LLCUnclassifiedIPv4 IPv6101
AS62255BiMajLink d.o.o.UnclassifiedIPv624
AS63023GTHostHostingIPv62

Provenance

Where this comes from

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