Akamai Prolexic DDoS Mitigation
Data as of 2026-09-20
BGP inherited
This organisation
| Netblocks | 123 |
| IPv6 | 61 prefixes (largest 2001:12f8:0:2::55:38/128) |
| Registered in | United States (15) · Australia (7) · India (4) · Japan (3) · United Kingdom (3) · Germany (3) |
| Record ID | 242138456 |
| Registry | PEERINGDB |
| Customers | see who runs inside 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 · report an issue | |
IP Ranges (123)
⬇ 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 |
| 119.11.187.136/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 123.108.12.46/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 |
| 206.126.239.112/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 206.223.116.136/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 206.223.118.209/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 206.223.123.233/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 208.115.136.35/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 210.171.224.197/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 210.173.176.122/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 217.29.67.168/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 218.100.52.155/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 218.100.78.120/32 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:504:0:1:0:3:2787:1/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:504:0:2:0:3:2787:1/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:504:0:2:0:3:2787:3/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:504:0:3:0:3:2787:1/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:504:0:4:0:3:2787:1/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:504:0:5:0:3:2787:1/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:504:0:6:0:3:2787:1/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:504:1::a503:2787:1/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:504:d::3:2787:1/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:504:13::211:137/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:504:1a::35:201/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:504:2d::18:133/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:504:36::8013:0:1/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:504:40:69::1:35/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:504:40:108::1:27/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:504:41:110::100/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:504:61::8013:0:1/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8::8013:0:1/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:1::a503:2787:1/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:4::8013:1/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:4:1::8013:1/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:b:100:1d1:a5d3:2787:168/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:d:fe::70/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:d:ff::70/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:f::189/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:14::2f:2/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:17::8013:1/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:24::bb/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:30:0:2:1:3:2787/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:35::3:2787:1/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:43::3:2787:1/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:54::1:164/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:73::8013:0:1/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:7a::3:2787:1/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:a0::8013:0:2/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:d1::8013:1/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:117::3:2787:1/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:7fa:0:1::ca28:a11a/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:7fa:2:5::43c/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:7fa:7:1:0:3:2787:1/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:7fa:11:1:0:8013:0:1/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:7fa:11:4:0:8013:0:1/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:7fa:11:6:0:8013:0:1/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:de8:1:1::197/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:de8:4::3:2787:1/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:de8:6::3:2787:1/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:de8:7::3:2787:1/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:de8:8::3:2787:1/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:de8:c::3:2787:1/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:de8:12:100::103:12/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:dea:0:10::135/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:dea:0:30::9d/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:dea:0:40::13/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:df0:680:5::4c/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:df0:680:6::40/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:df2:1900:2::1140/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:df2:1900:3::95/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2001:12f8:0:2::55:38/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2401:7500:fff6::150/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2404:c8:0:a:0:3:2787:1/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
| 2803:3440:9025::3:2787:1/128 | Akamai Prolexic DDoS Mitigation | PEERINGDB | ASSIGNED | ● high |
IPv6 ranges (61)
Footprint over time
13 weekly snapshots · JSON
123
+4 netblocks since 2026-07-05
2026-07-05
peak 123
2026-09-20
Customer-delegated space
how is this classified?
Operator infrastructure (named)
123 (100.0%)
Network trust
what's this?
RPKI hygiene: C
how networks compare →
69.9%
of checked blocks have valid RPKI ROA coverage
(86 of 123)
No discrepancies found among checked blocks.
NIC Handles
AS32787