asn.dev

Observed topology

AS53850 GORILLASERVERS - GorillaServers, Inc.

Unclassified ARIN

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

Transit

Upstream networks

All 17

Networks observed carrying traffic for AS53850: 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 IPv63,076
AS1299Arelion Sweden ABTransitIPv4 IPv61,452
AS174Cogent Communications, LLCTransitIPv4 IPv6636
AS3257GTT Communications Inc.TransitIPv4 IPv6532
AS7922Comcast Cable Communications, LLCResidentialIPv4147
AS18450WebNX, Inc.HostingIPv4132
AS2914NTT America, Inc.TransitIPv4 IPv638
AS22652Videotron LteeResidentialIPv4 IPv613
AS3491PCCW Global (HK) Ltd.TransitIPv412
AS24482SG.GSHostingIPv4 IPv67

All 17 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS213549SATISFYHOST LTDUnclassifiedIPv4 IPv6132

Adjacency

Adjacent networks

All 18

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv63,166
AS1299Arelion Sweden ABTransitIPv4 IPv61,477
AS174Cogent Communications, LLCTransitIPv4 IPv6643
AS3257GTT Communications Inc.TransitIPv4 IPv6540
AS7922Comcast Cable Communications, LLCResidentialIPv4149
AS18450WebNX, Inc.HostingIPv4132
AS213549SATISFYHOST LTDUnclassifiedIPv4 IPv6132
AS2914NTT America, Inc.TransitIPv4 IPv638
AS22652Videotron LteeResidentialIPv4 IPv613
AS3491PCCW Global (HK) Ltd.TransitIPv412

All 18 adjacent →

Provenance

Where this comes from

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