Observed topology

AS8431 AS8431 Sofia, Bulgaria

Unclassified RIPE

Upstreams 16 carry this network

Downstreams 0 this network carries

Adjacent (IPv4) 16

Adjacent (IPv6) 0

Upstream graph Who carries AS8431, and who carries them, drawn as a map up to the transit-free core. 2 exchanges Where AS8431 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 16

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

AS	Network	Type	Families	Paths seen
AS20911	Net-Surf.net Ltd.	Residential	IPv4	245
AS34224	Neterra Ltd.	Unclassified	IPv4	121
AS6939	Hurricane Electric LLC	Transit	IPv4	64
AS57463	NetIX Communications JSC	Unclassified	IPv4	31
AS8262	Evolink EAD	Unclassified	IPv4	26
AS34549	meerfarbig GmbH & Co. KG	Hosting	IPv4	8
AS8218	Zayo Infrastructure France SA	Unclassified	IPv4	5
AS8280	SYNAPSECOM S.A. Provider of Telecommunications and Internet Services	Hosting	IPv4	4
AS20764	CJSC RASCOM	Unclassified	IPv4	4
AS24482	SG.GS	Hosting	IPv4	4

All 16 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 16

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

AS	Network	Type	Families	Paths seen
AS20911	Net-Surf.net Ltd.	Residential	IPv4	245
AS34224	Neterra Ltd.	Unclassified	IPv4	121
AS6939	Hurricane Electric LLC	Transit	IPv4	64
AS57463	NetIX Communications JSC	Unclassified	IPv4	31
AS8262	Evolink EAD	Unclassified	IPv4	26
AS34549	meerfarbig GmbH & Co. KG	Hosting	IPv4	8
AS8218	Zayo Infrastructure France SA	Unclassified	IPv4	5
AS8280	SYNAPSECOM S.A. Provider of Telecommunications and Internet Services	Hosting	IPv4	4
AS20764	CJSC RASCOM	Unclassified	IPv4	4
AS24482	SG.GS	Hosting	IPv4	4

All 16 adjacent →

Provenance

Where this comes from

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