asn.dev

Observed topology

AS49814 TOMGATE-AS TomGate LLC

Unclassified RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS49814: 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 RostelecomResidentialIPv4 IPv6279
AS3216PJSC "Vimpelcom"MobileIPv499
AS8359MTS PJSCMobileIPv4 IPv631
AS48858JSC "ER-Telecom Holding"UnclassifiedIPv4 IPv622
AS24482SG.GSHostingIPv4 IPv68
AS37721Virtual Technologies & SolutionsResidentialIPv47
AS49673Truenetwork LLCUnclassifiedIPv47
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv47
AS50673Serverius Holding B.V.UnclassifiedIPv46
AS56655Gigahost ASUnclassifiedIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS214325OOO "T TELECOM"UnclassifiedIPv4123

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv4 IPv6353
AS3216PJSC "Vimpelcom"MobileIPv4131
AS214325OOO "T TELECOM"UnclassifiedIPv4123
AS8359MTS PJSCMobileIPv4 IPv635
AS48858JSC "ER-Telecom Holding"UnclassifiedIPv4 IPv623
AS24482SG.GSHostingIPv4 IPv610
AS50673Serverius Holding B.V.UnclassifiedIPv410
AS37721Virtual Technologies & SolutionsResidentialIPv49
AS49673Truenetwork LLCUnclassifiedIPv49
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv49

All 11 adjacent →

Provenance

Where this comes from

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