Observed topology

AS211057 PS-ASTRA

Unclassified RIPE Cable/DSL/ISP

Upstreams 5 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS211057: 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
AS12975	Palestine Telecommunications Company (PALTEL)	Unclassified	IPv4	364
AS12849	Hot-Net internet services Ltd.	Residential	IPv4	300
AS47962	SECURE ON SECURITY SYSTEMS LTD	Residential	IPv4	189
AS202940	ITC NG ltd	Unclassified	IPv4	122
AS212616	K.M.A ADVANCED TECHNOLOGIES LTD	Unclassified	IPv4	59

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS52145	ZONE Technologies Ltd	Residential	IPv4	60

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS12975	Palestine Telecommunications Company (PALTEL)	Unclassified	IPv4	424
AS12849	Hot-Net internet services Ltd.	Residential	IPv4	300
AS47962	SECURE ON SECURITY SYSTEMS LTD	Residential	IPv4	189
AS202940	ITC NG ltd	Unclassified	IPv4	122
AS52145	ZONE Technologies Ltd	Residential	IPv4	60
AS212616	K.M.A ADVANCED TECHNOLOGIES LTD	Unclassified	IPv4	59

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.