Observed topology
AS42013 TOGETHER-COMMUNICATION-LTD
Unclassified RIPE NSP
Transit
Upstream networks
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.
Transit
Downstream networks
Networks for which AS42013 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS8551 | Bezeq International Ltd. | Unclassified | IPv4 | 444 |
| AS47546 | Asad Tom trading as AsadNet | Unclassified | IPv4 | 126 |
| AS12754 | Coolnet New Communication Provider | Unclassified | IPv4 | 42 |
| AS12975 | Palestine Telecommunications Company (PALTEL) | Unclassified | IPv4 | 28 |
| AS48966 | Wataniya Palestine Mobile Telecommunication Company PLC | Unclassified | IPv4 | 6 |
| AS51407 | Mada Al-Arab General Services Company | Residential | IPv4 | 2 |
| AS1680 | Cellcom Fixed Line Communication L.P | Mobile | IPv4 | 1 |
Adjacency
Adjacent networks
Every AS seen directly next to AS42013 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS8551 | Bezeq International Ltd. | Unclassified | IPv4 IPv6 | 1,074,358 |
| AS1680 | Cellcom Fixed Line Communication L.P | Mobile | IPv4 IPv6 | 32,064 |
| AS12975 | Palestine Telecommunications Company (PALTEL) | Unclassified | IPv4 | 141 |
| AS47546 | Asad Tom trading as AsadNet | Unclassified | IPv4 | 126 |
| AS12754 | Coolnet New Communication Provider | Unclassified | IPv4 | 42 |
| AS48966 | Wataniya Palestine Mobile Telecommunication Company PLC | Unclassified | IPv4 | 6 |
| AS51407 | Mada Al-Arab General Services Company | Residential | IPv4 | 2 |
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.