RYD-5G
Data as of 2026-07-26
BGP inherited
Cluster stats
| Netblocks | 19 · 6,144 IPv4 addresses |
| IPv6 | 9 prefixes (largest 2a02:cb80:4214::/47) |
| All fragments | 23 blocks across 2 clusters |
| Cluster ID | 215823499 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 3 shared RIR contact/maintainer handles |
| 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
19
0 netblocks since 2026-07-05
2026-07-05
peak 19
2026-07-26
IP Ranges (19)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 77.223.240.0/22 | RYD-5G | RIPE | ASSIGNED PA | ● low |
| 77.223.244.0/22 | RYD-5G | RIPE | ASSIGNED PA | ● low |
| 82.197.32.0/23 | RYD-5G | RIPE | ASSIGNED PA | ● low |
| 82.197.34.0/23 | RYD-5G | RIPE | ASSIGNED PA | ● low |
| 82.197.38.0/23 | RYD-5G | RIPE | ASSIGNED PA | ● low |
| 82.197.40.0/23 | RYD-5G | RIPE | ASSIGNED PA | ● low |
| 82.197.42.0/23 | RYD-5G | RIPE | ASSIGNED PA | ● low |
| 82.197.44.0/23 | RYD-5G | RIPE | ASSIGNED PA | ● low |
| 82.197.48.0/23 | RYD-5G | RIPE | ASSIGNED PA | ● low |
| 82.197.50.0/23 | RYD-5G | RIPE | ASSIGNED PA | ● low |
| 2a02:cb80:4214::/47 | RYD-5G | RIPE | ASSIGNED | ● low |
| 2a02:cb80:4220::/47 | RYD-5G | RIPE | ASSIGNED | ● low |
| 2a02:cb80:4222::/47 | RYD-5G | RIPE | ASSIGNED | ● low |
| 2a02:cb80:4224::/47 | RYD-5G | RIPE | ASSIGNED | ● low |
| 2a02:cb80:4226::/47 | RYD-5G | RIPE | ASSIGNED | ● low |
| 2a02:cb80:4270::/48 | RYD-5G | RIPE | ASSIGNED | ● low |
| 2a02:cb80:4271::/48 | RYD-5G | RIPE | ASSIGNED | ● low |
| 2a02:cb80:4272::/48 | RYD-5G | RIPE | ASSIGNED | ● low |
| 2a02:cb80:4273::/48 | RYD-5G | RIPE | ASSIGNED | ● low |
IPv6 ranges (9)
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(19 of 19)
RPKI-inferred operator
Mobile Telecommunication Company Saudi Arabia Joint-Stock company
Nearly all of this network's RPKI-covered space is cryptographically authorized for this
single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.
NIC Handles
DUMY-RIPE
DUMY-RIPE
MTCKSA-MNT