asn.dev

Observed topology

AS202759 FairyHosting RJ Network OU

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS202759: 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
AS9002RETN LimitedUnclassifiedIPv4 IPv61,699
AS3249Telia Eesti ASResidentialIPv4 IPv6436

Transit

Downstream networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS218731Andris JakovlevsUnclassifiedIPv4393
AS219095Paul SagovUnclassifiedIPv4360
AS199304Mikaia Iraklii GuramovichUnclassifiedIPv4299
AS219443Ints DanebergsUnclassifiedIPv4 IPv6185
AS197574ExpressHost LtdUnclassifiedIPv4 IPv6152
AS212743ETERNITY NETWORKS LLCUnclassifiedIPv4120
AS219302SEALLY LTDUnclassifiedIPv4 IPv693
AS219436Juri UitUnclassifiedIPv4 IPv693
AS197622NEXTTRANSLATE LTDUnclassifiedIPv460
AS202147VPSUS LTDUnclassifiedIPv460

All 12 downstreams →

Adjacency

Adjacent networks

All 14

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

ASNetworkTypeFamiliesPaths seen
AS9002RETN LimitedUnclassifiedIPv4 IPv63,566
AS3249Telia Eesti ASResidentialIPv4 IPv6495
AS218731Andris JakovlevsUnclassifiedIPv4393
AS219095Paul SagovUnclassifiedIPv4360
AS199304Mikaia Iraklii GuramovichUnclassifiedIPv4299
AS219443Ints DanebergsUnclassifiedIPv4 IPv6185
AS197574ExpressHost LtdUnclassifiedIPv4 IPv6152
AS212743ETERNITY NETWORKS LLCUnclassifiedIPv4120
AS219302SEALLY LTDUnclassifiedIPv4 IPv693
AS219436Juri UitUnclassifiedIPv4 IPv693

All 14 adjacent →

Provenance

Where this comes from

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