asn.dev

Observed topology

AS202619 DOVECOM

Unclassified APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS202619: 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
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv6550
AS201776Miranda-Media LtdUnclassifiedIPv4 IPv6169
AS20485Joint Stock Company TransTeleComUnclassifiedIPv477
AS6939Hurricane Electric LLCTransitIPv454
AS199961Multitelesystems LLCUnclassifiedIPv4 IPv622
AS24482SG.GSHostingIPv4 IPv617
AS9002RETN LimitedUnclassifiedIPv4 IPv613
AS37721Virtual Technologies & SolutionsResidentialIPv412
AS34927iFog GmbHHostingIPv49

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS214081Koshelnik Sergey ValentinovichUnclassifiedIPv461

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv6590
AS201776Miranda-Media LtdUnclassifiedIPv4 IPv6169
AS20485Joint Stock Company TransTeleComUnclassifiedIPv485
AS6939Hurricane Electric LLCTransitIPv463
AS214081Koshelnik Sergey ValentinovichUnclassifiedIPv461
AS199961Multitelesystems LLCUnclassifiedIPv4 IPv622
AS24482SG.GSHostingIPv4 IPv618
AS9002RETN LimitedUnclassifiedIPv4 IPv614
AS37721Virtual Technologies & SolutionsResidentialIPv413
AS34927iFog GmbHHostingIPv410

Provenance

Where this comes from

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