asn.dev

Observed topology

AS213642 CORETTECH Cust:MENA

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS213642: 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
AS6204INTERKVM HOST SRLUnclassifiedIPv475
AS5405Inter.link GmbHUnclassifiedIPv445

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS210021DIL Technology LimitedResidentialIPv4243
AS329263Libyan Spider for IT LTD.UnclassifiedIPv4115

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6204INTERKVM HOST SRLUnclassifiedIPv4519
AS210021DIL Technology LimitedResidentialIPv4425
AS5405Inter.link GmbHUnclassifiedIPv4307
AS212088Al-Tair Al-Watani Company for General Trading, Agricultural Investments, Production and Distribution, Technical Services, Internet Services, Public Services, Information Technology and Software LtdUnclassifiedIPv4166
AS329263Libyan Spider for IT LTD.UnclassifiedIPv4115

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-18 10: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.