Akamai Prolexic DDoS Mitigation
BGP inherited
Cluster stats
| Netblocks | 119 |
| Registered in | United States (15) · Australia (7) · India (4) · Japan (3) · United Kingdom (3) · Germany (3) |
| Cluster ID | 208801814 |
| Registry | PEERINGDB |
| Customers | find 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 | |
Footprint over time
5 weekly snapshots · JSON
119
0 netblocks since 2026-07-05
2026-07-05
peak 119
2026-07-19
IP Ranges (119)
showing 50 of 119 — see all — ⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 5.57.81.220/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 27.111.228.157/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 36.255.56.140/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 37.49.237.164/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 43.243.21.122/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 43.243.22.19/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 45.68.83.38/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 45.120.251.95/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 45.127.172.107/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 80.81.193.70/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 80.249.213.92/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 91.206.52.187/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 91.210.16.200/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 101.203.88.86/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 103.16.103.12/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 103.26.69.53/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 103.26.71.157/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 103.27.170.52/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 103.77.109.140/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 103.156.182.184/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 123.255.91.26/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 149.112.69.35/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 185.1.8.122/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 185.1.15.13/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 185.1.126.12/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 185.1.192.120/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 185.1.215.89/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 187.16.222.2/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 193.149.1.189/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 193.188.137.78/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 193.203.0.236/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 194.68.123.70/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 194.68.128.70/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 195.42.145.167/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 195.66.224.31/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 195.66.236.31/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 198.32.160.74/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 198.32.176.228/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 198.32.243.207/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 198.179.18.133/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 200.23.206.223/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 202.77.88.132/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 202.77.90.64/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 206.41.108.27/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 206.41.110.100/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 206.53.202.157/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 206.72.211.137/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 206.82.104.90/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 206.108.35.201/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 206.126.236.219/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
Customer-delegated space
how is this classified?
Operator infrastructure (named)
119 (100.0%)
Network trust
what's this?
RPKI hygiene: C
how networks compare →
69.7%
of checked blocks have valid RPKI ROA coverage
(83 of 119)
No discrepancies found among checked blocks.
NIC Handles
AS32787