asn.dev

Observed topology

AS61031 ESCOMTEL-AS ESCOMTEL BACKGROUND COMMUNICATION NETWORKS Ltd.

Residential RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS61031: 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
AS48858JSC "ER-Telecom Holding"UnclassifiedIPv4187
AS20764CJSC RASCOMUnclassifiedIPv4143
AS9049JSC "ER-Telecom Holding"UnclassifiedIPv441
AS25478iHome LLCUnclassifiedIPv44

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS49551Teleseti LtdUnclassifiedIPv4365
AS44834LLC "POZITIV TELEKOM"UnclassifiedIPv4189
AS206820Nice Telecom LLCUnclassifiedIPv4126
AS60245Sannikov Kirill VladimirovichUnclassifiedIPv491
AS214115Nikolai BorisovUnclassifiedIPv460
AS202136"A-Siti" Limited Liability CompanyUnclassifiedIPv42

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS9049JSC "ER-Telecom Holding"UnclassifiedIPv4687
AS20764CJSC RASCOMUnclassifiedIPv4371
AS49551Teleseti LtdUnclassifiedIPv4365
AS48858JSC "ER-Telecom Holding"UnclassifiedIPv4201
AS44834LLC "POZITIV TELEKOM"UnclassifiedIPv4189
AS206820Nice Telecom LLCUnclassifiedIPv4126
AS60245Sannikov Kirill VladimirovichUnclassifiedIPv491
AS25478iHome LLCUnclassifiedIPv461
AS214115Nikolai BorisovUnclassifiedIPv460
AS50384iHome LLCUnclassifiedIPv42

All 11 adjacent →

Provenance

Where this comes from

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