Ray Network
RayNetwork
Registry
Cluster stats
| Netblocks | 4 |
| Cluster ID | 207730788 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | Registry record |
| 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 | |
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 2001:ded:c000::34/128 | RayNetwork | PEERINGDB | ASSIGNED | ● high |
| 2602:f613::2148:41:1/128 | RayNetwork | PEERINGDB | ASSIGNED | ● high |
| 2a0e:8f01:1000:16::11f/128 | RayNetwork | PEERINGDB | ASSIGNED | ● high |
| 2a0f:85c1:363:1:21:4841:0:1/128 | RayNetwork | PEERINGDB | ASSIGNED | ● high |
Possibly related to this organisation
what's this?Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own
naming convention, not a direct registration.
- SPRAYNETWORKS-NET via Telia Finland Oyj sub-allocation
- XRAYNETWORKS-NET via Emirates Integrated Telecommunications Company PJSC sub-allocation
- NSUK-TRESCRAYNETWORKCOMMS-LL via Claranet Limited sub-allocation
Network trust
what's this?
RPKI hygiene: C
how networks compare →
50.0%
of checked blocks have valid RPKI ROA coverage
(2 of 4)
No discrepancies found among checked blocks.
NIC Handles
AS214841