Jordan Telecommunications

Data as of 2026-07-26
BGP inherited
Cluster stats
Netblocks8
IPv6 4 prefixes (largest 2001:1a40:10::a500:8697:1/128)
Registered in Germany (2) · BH (1) · Egypt (1)
All fragments 99 blocks across 2 clusters
Cluster ID214582424
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 1 shared RIR contact/maintainer handle
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works · report an issue

Footprint over time

6 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-26

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
77.69.248.111/32 Jordan Telecommunications PEERINGDB ASSIGNED ● high
80.81.196.44/32 Jordan Telecommunications PEERINGDB ASSIGNED ● high
185.1.8.20/32 Jordan Telecommunications PEERINGDB ASSIGNED ● high
196.60.86.238/32 Jordan Telecommunications PEERINGDB ASSIGNED ● high
2001:7f8::21f9:0:1/128 Jordan Telecommunications PEERINGDB ASSIGNED ● high
2001:7f8:73::21f9:0:1/128 Jordan Telecommunications PEERINGDB ASSIGNED ● high
2001:1a40:10::a500:8697:1/128 Jordan Telecommunications PEERINGDB ASSIGNED ● high
2001:43f8:41::a500:8697:1/128 Jordan Telecommunications PEERINGDB ASSIGNED ● high

IPv6 ranges (4)

Network trust

what's this?
RPKI hygiene: C how networks compare →
75.0% of checked blocks have valid RPKI ROA coverage (6 of 8)
No discrepancies found among checked blocks.

NIC Handles

AS8697