asn.dev

Observed topology

AS60447 I_NET_BULGARIA I NET BULGARIA

Unclassified RIPE NSP

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

Transit

Upstream networks

All 15

Networks observed carrying traffic for AS60447: 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
AS59900Balkan Internet Exchange LtdUnclassifiedIPv4 IPv6164
AS1299Arelion Sweden ABTransitIPv4 IPv6155
AS9002RETN LimitedUnclassifiedIPv4123
AS6939Hurricane Electric LLCTransitIPv4 IPv6107
AS174Cogent Communications, LLCTransitIPv479
AS3491PCCW Global (HK) Ltd.TransitIPv4 IPv667
AS3356Level 3 Parent, LLCTransitIPv464
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv446
AS1273IDDQD-ASBusinessIPv445
AS3257GTT Communications Inc.TransitIPv4 IPv633

All 15 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS49072Novatech EOODUnclassifiedIPv4300
AS44077AM NET Ltd.UnclassifiedIPv4180

Adjacency

Adjacent networks

All 17

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

ASNetworkTypeFamiliesPaths seen
AS49072Novatech EOODUnclassifiedIPv4300
AS1299Arelion Sweden ABTransitIPv4 IPv6261
AS9002RETN LimitedUnclassifiedIPv4195
AS44077AM NET Ltd.UnclassifiedIPv4180
AS6939Hurricane Electric LLCTransitIPv4 IPv6171
AS59900Balkan Internet Exchange LtdUnclassifiedIPv4 IPv6164
AS174Cogent Communications, LLCTransitIPv4127
AS3356Level 3 Parent, LLCTransitIPv4108
AS3491PCCW Global (HK) Ltd.TransitIPv4 IPv697
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv482

All 17 adjacent →

Provenance

Where this comes from

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