Observed topology

AS6700 BEOTEL-AS www.beotel.net

Residential RIPE NSP

Upstreams 1 carry this network

Downstreams 6 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 2

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS6700: 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
AS8400	TELEKOM SRBIJA a.d.	Residential	IPv4 IPv6	987

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS205007	Maxim Azarov trading as eServer	Unclassified	IPv4 IPv6	502
AS205354	ENERGOPROJEKT ENTEL a.d. BEOGRAD	Unclassified	IPv4	163
AS25337	ALL IP DOO	Unclassified	IPv4	61
AS49198	MAKSNET d.o.o. Beograd	Unclassified	IPv4	61
AS200276	ASP Co d.o.o	Unclassified	IPv4	61
AS206542	Signet CS doo Beograd	Unclassified	IPv4	61

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS8400	TELEKOM SRBIJA a.d.	Residential	IPv4 IPv6	1,896
AS205007	Maxim Azarov trading as eServer	Unclassified	IPv4 IPv6	502
AS205354	ENERGOPROJEKT ENTEL a.d. BEOGRAD	Unclassified	IPv4	163
AS25337	ALL IP DOO	Unclassified	IPv4	61
AS49198	MAKSNET d.o.o. Beograd	Unclassified	IPv4	61
AS200276	ASP Co d.o.o	Unclassified	IPv4	61
AS206542	Signet CS doo Beograd	Unclassified	IPv4	61

Provenance

Where this comes from

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