asn.dev

Observed topology

AS43561 NET1-AS Vivacom Bulgaria EAD

Unclassified RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS43561: 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
AS8866Vivacom Bulgaria EADResidentialIPv4 IPv6220

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS39683Netpoint Services Ltd.UnclassifiedIPv4181
AS28820Eastern Telecommunication Company EADUnclassifiedIPv4120
AS35011Prosveta Sofia PLCUnclassifiedIPv454
AS200033Megalan EOODUnclassifiedIPv432
AS198202PEB "Texim" JSCUnclassifiedIPv425
AS204469SanevianUnclassifiedIPv415
AS44564Technical Solution LtdUnclassifiedIPv413
AS199132CALDERRA Ltd.UnclassifiedIPv413
AS196801Chimimport PlcUnclassifiedIPv410

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS8866Vivacom Bulgaria EADResidentialIPv4 IPv6683
AS39683Netpoint Services Ltd.UnclassifiedIPv4181
AS28820Eastern Telecommunication Company EADUnclassifiedIPv4120
AS35011Prosveta Sofia PLCUnclassifiedIPv454
AS200033Megalan EOODUnclassifiedIPv432
AS198202PEB "Texim" JSCUnclassifiedIPv425
AS204469SanevianUnclassifiedIPv415
AS44564Technical Solution LtdUnclassifiedIPv413
AS199132CALDERRA Ltd.UnclassifiedIPv413
AS196801Chimimport PlcUnclassifiedIPv410

Provenance

Where this comes from

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