asn.dev

Observed topology

AS42498 GERKON-AS

Residential ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS42498: 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
AS12389PJSC RostelecomResidentialIPv41,620
AS56889TTC Radiotechnika LTDUnclassifiedIPv4715
AS57304JSC "RetnNet"UnclassifiedIPv4216
AS28917Fiord Networks, UABUnclassifiedIPv4198
AS24482SG.GSHostingIPv436
AS31133PJSC MegaFonMobileIPv436
AS37721Virtual Technologies & SolutionsResidentialIPv436
AS49673Truenetwork LLCUnclassifiedIPv436
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv436
AS9002RETN LimitedUnclassifiedIPv418

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS57874Eurocable LTDUnclassifiedIPv4180
AS56889TTC Radiotechnika LTDUnclassifiedIPv491

Adjacency

Adjacent networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv42,205
AS56889TTC Radiotechnika LTDUnclassifiedIPv41,521
AS57304JSC "RetnNet"UnclassifiedIPv4350
AS28917Fiord Networks, UABUnclassifiedIPv4266
AS57874Eurocable LTDUnclassifiedIPv4180
AS31133PJSC MegaFonMobileIPv482
AS24482SG.GSHostingIPv452
AS37721Virtual Technologies & SolutionsResidentialIPv452
AS49673Truenetwork LLCUnclassifiedIPv452
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv452

All 15 adjacent →

Provenance

Where this comes from

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