asn.dev

Observed topology

AS42013 TOGETHER-COMMUNICATION-LTD

Unclassified RIPE NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS42013: 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
AS8551Bezeq International Ltd.UnclassifiedIPv4 IPv6457
AS1680Cellcom Fixed Line Communication L.PMobileIPv4 IPv6368

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS8551Bezeq International Ltd.UnclassifiedIPv4444
AS47546Asad Tom trading as AsadNetUnclassifiedIPv4126
AS12754Coolnet New Communication ProviderUnclassifiedIPv442
AS12975Palestine Telecommunications Company (PALTEL)UnclassifiedIPv428
AS48966Wataniya Palestine Mobile Telecommunication Company PLCUnclassifiedIPv46
AS51407Mada Al-Arab General Services CompanyResidentialIPv42
AS1680Cellcom Fixed Line Communication L.PMobileIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS8551Bezeq International Ltd.UnclassifiedIPv4 IPv61,074,358
AS1680Cellcom Fixed Line Communication L.PMobileIPv4 IPv632,064
AS12975Palestine Telecommunications Company (PALTEL)UnclassifiedIPv4141
AS47546Asad Tom trading as AsadNetUnclassifiedIPv4126
AS12754Coolnet New Communication ProviderUnclassifiedIPv442
AS48966Wataniya Palestine Mobile Telecommunication Company PLCUnclassifiedIPv46
AS51407Mada Al-Arab General Services CompanyResidentialIPv42

Provenance

Where this comes from

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