bgpreport

Network · data from 2026-11-12

AS30641 STATEOFDE - STATE OF DELAWARE

Registry name: STATEOFDE - STATE OF DELAWARE, US · not in PeeringDB

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

Announced routes

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

167.21.0.0/17 No ROA Other IRR onlyRADB 671 100% 67
167.21.128.0/17 No ROA Other IRR onlyRADB 671 100% 67
2620:17c::/36 No ROA Other IRR onlyRADB 634 100% 68

AS-SET

AS30641 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 47 are in fix.csv.

  • ROA: none3
  • Route object: RIR3
  • Route object: not announced41
ChangePrefix or setDetailFull-table peers
ROA: none167.21.0.0/17No ROA covers it. Add a ROA for AS30641, maxLength 17.671 of 673
Route object: RIR167.21.0.0/17Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none167.21.128.0/17No ROA covers it. Add a ROA for AS30641, maxLength 17.671 of 673
Route object: RIR167.21.128.0/17Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2620:17c::/36No ROA covers it. Add a ROA for AS30641, maxLength 36.634 of 636
Route object: RIR2620:17c::/36Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

38.66.79.0/24RADBNo ROA
38.115.62.0/24RADBNo ROA
167.21.0.0/16RADBNo ROA
167.21.1.0/24RADBNo ROA
167.21.2.0/24RADBNo ROA
167.21.3.0/24RADBNo ROA
167.21.4.0/24RADBNo ROA
167.21.10.0/24RADBNo ROA
167.21.14.0/24RADBNo ROA
167.21.15.0/24RADBNo ROA
167.21.44.0/24RADBNo ROA
167.21.48.0/28RADBNo ROA
167.21.50.0/24RADBNo ROA
167.21.51.0/24RADBNo ROA
167.21.180.0/22RADBNo ROA
167.21.180.0/24RADBNo ROA
167.21.181.0/24RADBNo ROA
167.21.182.0/24RADBNo ROA
167.21.183.0/24RADBNo ROA
167.21.184.0/22RADBNo ROA
167.21.184.0/24RADBNo ROA
167.21.185.0/24RADBNo ROA
167.21.186.0/24RADBNo ROA
167.21.195.0/24RADBNo ROA
167.21.196.0/24RADBNo ROA
167.21.198.0/24RADBNo ROA
167.21.199.0/24RADBNo ROA
167.21.200.0/21RADBNo ROA
167.21.208.0/24RADBNo ROA
167.21.209.0/24RADBNo ROA
167.21.210.0/24RADBNo ROA
167.21.211.0/24RADBNo ROA
167.21.212.0/24RADBNo ROA
167.21.213.0/24RADBNo ROA
167.21.224.0/21RADBNo ROA
167.21.232.0/24RADBNo ROA
167.21.249.0/24RADBNo ROA
167.21.250.0/24RADBNo ROA
167.21.251.0/24RADBNo ROA
167.21.254.0/24RADBNo ROA
209.160.239.0/24RADBNo 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.