asn.dev

Observed topology

AS59900 Balkan Internet Exchange Ltd

Unclassified RIPE Route Server

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS59900: 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.

No upstream observed. Typical for a tier-1 network that buys transit from nobody.

Transit

Downstream networks

All 16

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

ASNetworkTypeFamiliesPaths seen
AS200736MEDIANET INVEST AEResidentialIPv4 IPv6945
AS20657ATLANTIS BG Ltd.UnclassifiedIPv4181
AS60447I NET BULGARIA EOODUnclassifiedIPv4 IPv6164
AS59463VISION 2008 Ltd.ResidentialIPv4116
AS49188Three A Hub EOODUnclassifiedIPv472
AS200019ALEXHOST S.R.L.UnclassifiedIPv467
AS201789NETOPS B.V.UnclassifiedIPv4 IPv623
AS48115DGM EOODUnclassifiedIPv421
AS8866Vivacom Bulgaria EADResidentialIPv420
AS20911Net-Surf.net Ltd.ResidentialIPv413

All 16 downstreams →

Adjacency

Adjacent networks

All 43

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

ASNetworkTypeFamiliesPaths seen
AS200736MEDIANET INVEST AEResidentialIPv4 IPv6948
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv6397
AS50304Blix Solutions ASUnclassifiedIPv4 IPv6291
AS20657ATLANTIS BG Ltd.UnclassifiedIPv4209
AS206499LOCIX LIMITEDUnclassifiedIPv4206
AS60447I NET BULGARIA EOODUnclassifiedIPv4 IPv6164
AS401753BIXCE IncUnclassifiedIPv4 IPv6128
AS59463VISION 2008 Ltd.ResidentialIPv4116
AS34927iFog GmbHHostingIPv4109
AS201789NETOPS B.V.UnclassifiedIPv4 IPv690

All 43 adjacent →

Provenance

Where this comes from

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