Reia Network
Cluster stats
| Netblocks | 20 |
| Cluster ID | 191818580 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 4 shared RIR contact/maintainer handles |
| Registry names | 15 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (20)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 23.154.164.140/32 | Reia Network | PEERINGDB | ASSIGNED | ● high |
| 2602:f429:31::12/128 | Reia Network | PEERINGDB | ASSIGNED | ● high |
| 2602:f92a:1315:1::22/128 | Reia Network | PEERINGDB | ASSIGNED | ● high |
| 2602:f92a:1315:2::6f/128 | Reia Network | PEERINGDB | ASSIGNED | ● high |
| 2602:f92a:1315:2::70/128 | Reia Network | PEERINGDB | ASSIGNED | ● high |
| 2a0f:7803:fc60:aaaa::1986:81/128 | Reia Network | PEERINGDB | ASSIGNED | ● high |
| 2a0f:1cc5:3200::/48 | Reia-Network-AZKI | RIPE | ASSIGNED | ● low |
| 2a0f:1cc5:3201::/48 | Reia-Network-suisei | RIPE | ASSIGNED | ● low |
| 2a0f:1cc5:3202::/48 | Reia-Network-Marine | RIPE | ASSIGNED | ● low |
| 2a0f:1cc5:3203::/48 | Reia-Network-Pekora | RIPE | ASSIGNED | ● low |
| 2a0f:1cc5:3204::/48 | Reia-Network-NatsuiroMatsuri | RIPE | ASSIGNED | ● low |
| 2a0f:1cc5:3205::/48 | Reia-Network-ShirakamiFubuki | RIPE | ASSIGNED | ● low |
| 2a0f:1cc5:3206::/48 | Reia-Network-Akai | RIPE | ASSIGNED | ● low |
| 2a0f:1cc5:3207::/48 | Reia-Network-NakiriAyame | RIPE | ASSIGNED | ● low |
| 2a0f:1cc5:3208::/48 | Reia-Network-Koyori | RIPE | ASSIGNED | ● low |
| 2a0f:1cc5:3209::/48 | Reia-Network-KiryuCoco | RIPE | ASSIGNED | ● low |
| 2a0f:1cc5:3222::/48 | Reia-Network-Anycast | RIPE | ASSIGNED | ● low |
| 2a14:67c3:1100::/48 | Reia-Network-Aqua | RIPE | ASSIGNED | ● low |
| 2a14:67c3:1101::/48 | Reia-Network-Gura | RIPE | ASSIGNED | ● low |
| 2a14:7586:6400::/44 | Reia-Network-Tomori | RIPE | ALLOCATED-BY-LIR | ● low |
Network trust
what's this?
RPKI hygiene: B
how networks compare →
85.0%
of checked blocks have valid RPKI ROA coverage
(17 of 20)
Possible discrepancies (13)
These blocks are registered to Reia Network but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 2a0f:1cc5:3200::/48 /48 | authorized for AS198681 — Jinquan Zeng |
| 2a0f:1cc5:3201::/48 /48 | authorized for AS198681 — Jinquan Zeng |
| 2a14:67c3:1100::/48 /48 | authorized for AS198681 — Jinquan Zeng |
| 2a0f:1cc5:3202::/48 /48 | authorized for AS198681 — Jinquan Zeng |
| 2a14:67c3:1101::/48 /48 | authorized for AS198681 — Jinquan Zeng |
| 2a0f:1cc5:3203::/48 /48 | authorized for AS198681 — Jinquan Zeng |
| 2a0f:1cc5:3204::/48 /48 | authorized for AS198681 — Jinquan Zeng |
| 2a0f:1cc5:3205::/48 /48 | authorized for AS198681 — Jinquan Zeng |
| 2a0f:1cc5:3206::/48 /48 | authorized for AS198681 — Jinquan Zeng |
| 2a0f:1cc5:3222::/48 /48 | authorized for AS198681 — Jinquan Zeng |
| 2a0f:1cc5:3207::/48 /48 | authorized for AS198681 — Jinquan Zeng |
| 2a0f:1cc5:3208::/48 /48 | authorized for AS198681 — Jinquan Zeng |
| 2a0f:1cc5:3209::/48 /48 | authorized for AS198681 — Jinquan Zeng |
NIC Handles
AS198681
DUMY-RIPE
DUMY-RIPE
REIA-MNT