asn.dev

Observed topology

AS50763 MCKAYCOM

Unclassified RIPE

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

Transit

Upstream networks

All 27

Networks observed carrying traffic for AS50763: 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, LLCHostingIPv4 IPv6184
AS25369Hydra Communications LtdHostingIPv4 IPv6104
AS34927iFog GmbHHostingIPv4 IPv6104
AS6939Hurricane Electric LLCTransitIPv4 IPv6102
AS198057Flooyd Telecom LTDAResidentialIPv460
AS6204INTERKVM HOST SRLUnclassifiedIPv4 IPv658
AS33387Nocix, LLCHostingIPv410
AS24482SG.GSHostingIPv4 IPv69
AS48185team.blue NVUnclassifiedIPv4 IPv68
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv68

All 27 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS33309Heliacal NetworksUnclassifiedIPv4 IPv699

Adjacency

Adjacent networks

All 30

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

ASNetworkTypeFamiliesPaths seen
AS20473The Constant Company, LLCHostingIPv4 IPv6191
AS6939Hurricane Electric LLCTransitIPv4 IPv6135
AS34927iFog GmbHHostingIPv4 IPv6127
AS25369Hydra Communications LtdHostingIPv4 IPv6107
AS33309Heliacal NetworksUnclassifiedIPv4 IPv699
AS6204INTERKVM HOST SRLUnclassifiedIPv4 IPv673
AS198057Flooyd Telecom LTDAResidentialIPv460
AS24482SG.GSHostingIPv4 IPv611
AS33387Nocix, LLCHostingIPv410
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv610

All 30 adjacent →

Provenance

Where this comes from

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