bgpreport

Network · data from 2026-11-12

AS30060 VERISIGN-ILG1 - VeriSign Infrastructure & Operations

Registry name: VERISIGN-ILG1 - VeriSign Infrastructure & Operations, US · not in PeeringDB

48IPv4 routes 87.5% RPKI valid · 100.0% with a route object
10IPv6 routes 90.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
7No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
22Route objects not announced registered with origin AS30060, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS30060, 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.

69.58.176.0/20 No ROA RIR databaseARIN, RADB 673 100% 67
69.58.183.0/24 No ROA RIR databaseARIN, RADB 673 100% 67
209.131.158.0/24 No ROA RIR databaseARIN, RADB 673 100% 67
209.131.159.0/24 No ROA RIR databaseARIN, RADB 673 100% 67
72.13.40.0/24 No ROA RIR databaseARIN, RADB 672 100% 67
72.13.41.0/24 No ROA RIR databaseARIN, RADB 672 100% 67
2620:74:7::/48 No ROA RIR databaseARIN, RADB 634 100% 68
64.6.90.0/24 Valid RIR databaseARIN, RADB 673 100% 67
64.6.91.0/24 Valid RIR databaseARIN, RADB 673 100% 67
69.36.150.0/24 Valid RIR databaseARIN, RADB 673 100% 67
69.36.152.0/24 Valid RIR databaseARIN, RADB 673 100% 67
69.36.154.0/24 Valid RIR databaseARIN, RADB 673 100% 67
69.58.176.0/24 Valid RIR databaseARIN, RADB 673 100% 67
69.58.177.0/24 Valid RIR databaseARIN, RADB 673 100% 67
69.58.180.0/24 Valid RIR databaseARIN, RADB 673 100% 67
69.58.184.0/24 Valid RIR databaseARIN, RADB 673 100% 67
69.58.185.0/24 Valid RIR databaseARIN, RADB 673 100% 67
199.16.85.0/24 Valid RIR databaseARIN, RADB 673 100% 67
199.16.87.0/24 Valid RIR databaseARIN, RADB 673 100% 67
199.16.88.0/24 Valid RIR databaseARIN, RADB 673 100% 67
199.16.89.0/24 Valid RIR databaseARIN, RADB 673 100% 67
199.16.94.0/24 Valid RIR databaseARIN, RADB 673 100% 67
209.112.112.0/24 Valid RIR databaseARIN, RADB 673 100% 67
209.112.124.0/24 Valid RIR databaseARIN, RADB 673 100% 67
209.131.182.0/24 Valid RIR databaseARIN, RADB 673 100% 67
209.131.183.0/24 Valid RIR databaseARIN, RADB 673 100% 67
209.131.191.0/24 Valid RIR databaseARIN, RADB 673 100% 67
216.87.128.0/24 Valid RIR databaseARIN, RADB 673 100% 67
216.87.129.0/24 Valid RIR databaseARIN, RADB 673 100% 67
216.87.130.0/24 Valid RIR databaseARIN, RADB 673 100% 67
216.87.131.0/24 Valid RIR databaseARIN, RADB 673 100% 67
216.87.132.0/24 Valid RIR databaseARIN, RADB 673 100% 67
216.87.134.0/24 Valid RIR databaseARIN, RADB 673 100% 67
216.87.135.0/24 Valid RIR databaseARIN, RADB 673 100% 67
216.87.138.0/24 Valid RIR databaseARIN, RADB 673 100% 67
216.87.141.0/24 Valid RIR databaseARIN, RADB 673 100% 67
216.87.144.0/24 Valid RIR databaseARIN, RADB 673 100% 67
216.87.150.0/24 Valid RIR databaseARIN, RADB 673 100% 67
216.87.153.0/24 Valid RIR databaseARIN, RADB 673 100% 67
216.87.156.0/24 Valid RIR databaseARIN, RADB 673 100% 67
216.87.157.0/24 Valid RIR databaseARIN, RADB 673 100% 67
216.168.226.0/24 Valid RIR databaseARIN, RADB 673 100% 67
216.168.227.0/24 Valid RIR databaseARIN, RADB 673 100% 67
216.168.235.0/24 Valid RIR databaseARIN, RADB 673 100% 67
216.168.236.0/24 Valid RIR databaseARIN, RADB 673 100% 67
69.58.187.0/24 Valid RIR databaseARIN, RADB 672 100% 67
72.13.50.0/24 Valid RIR databaseARIN, RADB 672 100% 67
72.13.62.0/24 Valid RIR databaseARIN, RADB 671 100% 67
2402:79c0:f008::/48 Valid RIR databaseAPNIC, RADB 634 100% 68
2402:79c0:f00a::/48 Valid RIR databaseAPNIC, RADB 634 100% 68
2402:79c0:f00b::/48 Valid RIR databaseAPNIC, RADB 634 100% 68
2620:74:8::/48 Valid RIR databaseARIN, RADB 634 100% 68
2620:74:14::/48 Valid RIR databaseARIN, RADB 634 100% 68
2620:74:78::/48 Valid RIR databaseARIN, RADB 634 100% 68
2620:74:81::/48 Valid RIR databaseARIN, RADB 634 100% 68
2620:74:a0::/48 Valid RIR databaseARIN, RADB 634 100% 68
216.87.136.0/24 Valid RIR databaseARIN, RADB 212 32% 51
2402:79c0:f0f9::/48 Valid RIR databaseAPNIC, RADB 141 22% 42

AS-SET

AS30060 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 29 are in fix.csv.

  • ROA: none7
  • Route object: not announced22
ChangePrefix or setDetailFull-table peers
ROA: none69.58.176.0/20No ROA covers it. Add a ROA for AS30060, maxLength 20.673 of 673
ROA: none69.58.183.0/24No ROA covers it. Add a ROA for AS30060, maxLength 24.673 of 673
ROA: none209.131.158.0/24No ROA covers it. Add a ROA for AS30060, maxLength 24.673 of 673
ROA: none209.131.159.0/24No ROA covers it. Add a ROA for AS30060, maxLength 24.673 of 673
ROA: none72.13.40.0/24No ROA covers it. Add a ROA for AS30060, maxLength 24.672 of 673
ROA: none72.13.41.0/24No ROA covers it. Add a ROA for AS30060, maxLength 24.672 of 673
ROA: none2620:74:7::/48No ROA covers it. Add a ROA for AS30060, maxLength 48.634 of 636

Route objects not announced

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

64.6.82.0/24RADBNo ROA
64.6.95.0/24ARIN, RADBNo ROA
69.36.151.0/24ARIN, RADBNo ROA
69.36.156.0/24ARIN, RADBNo ROA
69.36.159.0/24ARIN, RADBNo ROA
69.58.182.0/24ARIN, RADBNo ROA
69.58.190.0/24ARIN, RADBNo ROA
199.7.54.0/24ARIN, RADBNo ROA
199.16.95.0/24ARIN, RADBNo ROA
209.112.112.0/20RADBNo ROA
209.112.117.0/24ARIN, RADBNo ROA
209.112.119.0/24ARIN, RADBNo ROA
216.87.152.0/24ARIN, RADBNo ROA
216.168.225.0/24ARIN, RADBNo ROA
2620:74::/48RADBNo ROA
2620:74:1::/48RADBNo ROA
2620:74:3::/48RADBNo ROA
2620:74:9::/48ARIN, RADBNo ROA
2620:74:76::/48ARIN, RADBNo ROA
2620:74:8b::/48ARIN, RADBNo ROA
2620:74:90::/48ARIN, RADBNo ROA
2620:74:ea::/48ARIN, RADBValid

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.