asn.dev

Observed topology

AS62386 BTG-AS Bulgarian Telecommunication Group EOOD

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS62386: 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
AS31287IPACCT CABLE LtdUnclassifiedIPv4360
AS8717A1 Bulgaria EADResidentialIPv4 IPv656
AS41313"NOVATEL" EOODUnclassifiedIPv4 IPv632
AS6939Hurricane Electric LLCTransitIPv410
AS8280SYNAPSECOM S.A. Provider of Telecommunications and Internet ServicesHostingIPv4 IPv64
AS8218Zayo Infrastructure France SAUnclassifiedIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS44525Niko Net Com Ltd.UnclassifiedIPv4295
AS38924Trakia Kabel OODUnclassifiedIPv4 IPv696

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS31287IPACCT CABLE LtdUnclassifiedIPv4360
AS44525Niko Net Com Ltd.UnclassifiedIPv4295
AS8717A1 Bulgaria EADResidentialIPv4 IPv6221
AS41313"NOVATEL" EOODUnclassifiedIPv4 IPv6187
AS38924Trakia Kabel OODUnclassifiedIPv4 IPv696
AS6939Hurricane Electric LLCTransitIPv468
AS8280SYNAPSECOM S.A. Provider of Telecommunications and Internet ServicesHostingIPv4 IPv611
AS8218Zayo Infrastructure France SAUnclassifiedIPv47

Provenance

Where this comes from

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