Page Kurdistan
BGP inherited
Cluster stats
| Netblocks | 5 |
| Registered in | France (3) · United Kingdom (1) |
| Cluster ID | 213312878 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 11 shared RIR contact/maintainer handles |
| Registry names | 4 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (5)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 31.3.212.0/28 | Page White Farrer | RIPE | ASSIGNED PA | ● high |
| 135.125.198.176/28 | Page Kurdistan | RIPE | ASSIGNED PA | ● high |
| 84.96.9.196/30 | PAGE-UP | RIPE | ASSIGNED PA | ● low |
| 217.112.234.16/28 | PAGE-UP | RIPE | ASSIGNED PA | ● low |
| 2a00:2381:3441::/48 | PAGE-AND | RIPE | AGGREGATED-BY-LIR | ● low |
Network trust
what's this?
RPKI hygiene: B
how networks compare →
80.0%
of checked blocks have valid RPKI ROA coverage
(4 of 5)
Possible discrepancies (1)
These blocks are registered to Page Kurdistan 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.
| 2a00:2381:3441::/48 /48 | authorized for AS2856 — British Telecommunications Limited |
NIC Handles
BTNET-MNT
C4L-MNT
DUMY-RIPE
DUMY-RIPE
FMCF-MNT
IDEGROUP-MNT
LDCOM-MNT
LDCOM-PRO-MNT
ORG-PK110-RIPE
ORG-PWF1-RIPE
OVH-MNT