bgpreport

Network · data from 2026-11-12

AS197992 DEFSOLUTION-LLC DEFSOLUTION LLC

Registry name: DEFSOLUTION-LLC DEFSOLUTION LLC, US · not in PeeringDB

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

Announced routes

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

2a0d:a9c0::/29 No ROA Other IRR onlyRADB 635 100% 67
2a11:f040::/29 No ROA Other IRR onlyRADB 635 100% 67
2a10:3040::/29 No ROA Other IRR onlyRADB 632 99% 68
2a10:6300::/29 No ROA Other IRR onlyRADB 632 99% 67
2a10:6900::/29 No ROA Other IRR onlyRADB 632 99% 67
2a13:2f40::/29 No ROA Other IRR onlyRADB 632 99% 68
2a13:9100::/29 No ROA Other IRR onlyRADB 632 99% 67
2a13:c700::/29 No ROA Other IRR onlyRADB 632 99% 67
2a13:8340::/29 Valid Other IRR onlyRADB 633 100% 68
2a13:4f00::/29 Valid Other IRR onlyRADB 632 99% 67
2a11:1880::/29 Valid RIR databaseRADB, RIPE 632 99% 67
2a11:90c0::/29 Valid RIR databaseRIPE 632 99% 67
2a11:9340::/29 Valid RIR databaseRIPE 632 99% 67
2a11:9e00::/29 Valid RIR databaseRIPE 632 99% 67
2a11:b740::/29 Valid RIR databaseRIPE 632 99% 67

AS-SET

AS197992 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: none8
  • Route object: RIR10
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2a0d:a9c0::/29No ROA covers it. Add a ROA for AS197992, maxLength 29.635 of 636
Route object: RIR2a0d:a9c0::/29Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2a11:f040::/29No ROA covers it. Add a ROA for AS197992, maxLength 29.635 of 636
Route object: RIR2a11:f040::/29Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2a10:3040::/29No ROA covers it. Add a ROA for AS197992, maxLength 29.632 of 636
Route object: RIR2a10:3040::/29Route object only in RADB. Add it in the RIR database for the space.632 of 636
ROA: none2a10:6300::/29No ROA covers it. Add a ROA for AS197992, maxLength 29.632 of 636
Route object: RIR2a10:6300::/29Route object only in RADB. Add it in the RIR database for the space.632 of 636
ROA: none2a10:6900::/29No ROA covers it. Add a ROA for AS197992, maxLength 29.632 of 636
Route object: RIR2a10:6900::/29Route object only in RADB. Add it in the RIR database for the space.632 of 636
ROA: none2a13:2f40::/29No ROA covers it. Add a ROA for AS197992, maxLength 29.632 of 636
Route object: RIR2a13:2f40::/29Route object only in RADB. Add it in the RIR database for the space.632 of 636
ROA: none2a13:9100::/29No ROA covers it. Add a ROA for AS197992, maxLength 29.632 of 636
Route object: RIR2a13:9100::/29Route object only in RADB. Add it in the RIR database for the space.632 of 636
ROA: none2a13:c700::/29No ROA covers it. Add a ROA for AS197992, maxLength 29.632 of 636
Route object: RIR2a13:c700::/29Route object only in RADB. Add it in the RIR database for the space.632 of 636
Route object: RIR2a13:8340::/29Route object only in RADB. Add it in the RIR database for the space.633 of 636
Route object: RIR2a13:4f00::/29Route object only in RADB. Add it in the RIR database for the space.632 of 636

Route objects not announced

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

2a10:9c0::/29RADBNo 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.