bgpreport

Network · data from 2026-11-12

AS26008 AKAMAI-NOMINUM-ASN - Akamai Technologies, Inc.

Registry name: AKAMAI-NOMINUM-ASN - Akamai Technologies, Inc., US · not in PeeringDB

9IPv4 routes 100.0% RPKI valid · 100.0% with a route object
8IPv6 routes 25.0% RPKI valid · 75.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
6No ROA 2 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
3Route objects not announced registered with origin AS26008, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS26008, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
2620:104:a000::/44 No ROA None 634 100% 68
2620:104:a001::/48 No ROA None 634 100% 68
2620:104:a003::/48 No ROA Other IRR onlyRADB 636 100% 67
2620:104:a004::/48 No ROA Other IRR onlyRADB 636 100% 67
2620:104:a00a::/48 No ROA Other IRR onlyRADB 629 99% 68
2620:104:a00b::/48 No ROA Other IRR onlyRADB 629 99% 68
72.200.254.0/24 Valid Other IRR onlyRADB 672 100% 67
72.200.255.0/24 Valid Other IRR onlyRADB 672 100% 67
2001:57a:102::/48 Valid Other IRR onlyRADB 635 100% 68
2001:57a:103::/48 Valid Other IRR onlyRADB 635 100% 68
74.121.124.0/22 Valid RIR databaseARIN 673 100% 67
199.101.28.0/22 Valid RIR databaseARIN 673 100% 67
81.200.66.0/24 Valid RIR databaseRIPE 672 100% 67
81.200.67.0/24 Valid RIR databaseRIPE 672 100% 67
81.200.69.0/24 Valid RIR databaseRIPE 672 100% 67
74.121.124.0/24 Valid RIR databaseARIN 666 99% 67
74.121.125.0/24 Valid RIR databaseARIN 666 99% 67

AS-SET

AS26008 isn't in PeeringDB, where networks name their AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 19 are in fix.csv.

  • ROA: none6
  • Route object: none2
  • Route object: RIR8
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none2620:104:a000::/44No ROA covers it. Add a ROA for AS26008, maxLength 44.634 of 636
Route object: none2620:104:a000::/44No route object for it. Add a route object with origin AS26008 in the RIR database for the space.634 of 636
ROA: none2620:104:a001::/48No ROA covers it. Add a ROA for AS26008, maxLength 48.634 of 636
Route object: none2620:104:a001::/48No route object for it. Add a route object with origin AS26008 in the RIR database for the space.634 of 636
ROA: none2620:104:a003::/48No ROA covers it. Add a ROA for AS26008, maxLength 48.636 of 636
Route object: RIR2620:104:a003::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none2620:104:a004::/48No ROA covers it. Add a ROA for AS26008, maxLength 48.636 of 636
Route object: RIR2620:104:a004::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none2620:104:a00a::/48No ROA covers it. Add a ROA for AS26008, maxLength 48.629 of 636
Route object: RIR2620:104:a00a::/48Route object only in RADB. Add it in the RIR database for the space.629 of 636
ROA: none2620:104:a00b::/48No ROA covers it. Add a ROA for AS26008, maxLength 48.629 of 636
Route object: RIR2620:104:a00b::/48Route object only in RADB. Add it in the RIR database for the space.629 of 636
Route object: RIR72.200.254.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR72.200.255.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR2001:57a:102::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2001:57a:103::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

Route objects with origin AS26008 whose prefix no peer sees AS26008 announce. Many are kept on purpose (backup routes, space announced only in some places).

74.121.127.0/24ARINValid
199.101.30.0/24ARINValid
2620:104:a00c::/48RADBNo ROA

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.