bgpreport

Network · data from 2026-11-12

AS21860 FL-GRIP - FOLEY & LARDNER LLP

Registry name: FL-GRIP - FOLEY & LARDNER LLP, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS21860, 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.
204.87.60.0/24 No ROA Nonecovered by 204.87.32.0/19 673 100% 67
204.87.40.0/24 No ROA Other origin onlycovered by 204.87.32.0/19 671 100% 67
204.87.50.0/24 No ROA Other origin onlycovered by 204.87.32.0/19 671 100% 67

AS-SET

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

  • ROA: none3
  • Route object: none3
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none204.87.60.0/24No ROA covers it. Add a ROA for AS21860, maxLength 24.673 of 673
Route object: none204.87.60.0/24No route object for it. A route object for 204.87.32.0/19 with origin AS21860 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21860 in the RIR database for the space.673 of 673
ROA: none204.87.40.0/24No ROA covers it. Add a ROA for AS21860, maxLength 24.671 of 673
Route object: none204.87.40.0/24Route objects for it name AS40107. A route object for 204.87.32.0/19 with origin AS21860 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21860 in the RIR database for the space.671 of 673
ROA: none204.87.50.0/24No ROA covers it. Add a ROA for AS21860, maxLength 24.671 of 673
Route object: none204.87.50.0/24Route objects for it name AS40107. A route object for 204.87.32.0/19 with origin AS21860 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21860 in the RIR database for the space.671 of 673

Route objects not announced

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

204.87.32.0/19RADBNo 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.