bgpreport

Network · data from 2026-11-12

AS62571 IMPERVA-INC-US-SJ-COLO - IMPERVA INC

Registry name: IMPERVA-INC-US-SJ-COLO - IMPERVA INC, US · not in PeeringDB

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

Announced routes

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

198.51.94.0/24 No ROA Other IRR onlyRADB 670 100% 67
2a03:10e0::/48 No ROA Other IRR onlyRADB 636 100% 67
2a03:10e0:1::/48 No ROA Other IRR onlyRADB 636 100% 67
45.223.186.0/24 Valid None 670 100% 66
2a02:e982:1e::/48 Valid Other origin only 636 100% 67
2a02:e982:31::/48 Valid None 636 100% 67
2a02:e980:1e::/48 Valid Other origin only 166 26% 37
2a02:e980:25::/48 Valid Other origin only 3 0%low visibility 3
192.230.75.0/24 Valid Other IRR onlyRADB 672 100% 66
192.230.76.0/24 Valid Other IRR onlyRADB 672 100% 66
198.143.36.0/24 Valid Other IRR onlyRADB 672 100% 66
185.64.8.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
185.64.9.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
45.223.42.0/24 Valid RIR databaseARIN 670 100% 66
185.64.10.0/24 Valid RIR databaseRADB, RIPE 670 100% 67

AS-SET

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

  • ROA: none3
  • Route object: none5
  • Route object: RIR6
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none198.51.94.0/24No ROA covers it. Add a ROA for AS62571, maxLength 24.670 of 673
Route object: RIR198.51.94.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none2a03:10e0::/48No ROA covers it. Add a ROA for AS62571, maxLength 48.636 of 636
Route object: RIR2a03:10e0::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none2a03:10e0:1::/48No ROA covers it. Add a ROA for AS62571, maxLength 48.636 of 636
Route object: RIR2a03:10e0:1::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: none45.223.186.0/24No route object for it. Add a route object with origin AS62571 in the RIR database for the space.670 of 673
Route object: none2a02:e982:1e::/48Route objects for it name AS19551. Add a route object with origin AS62571 in the RIR database for the space.636 of 636
Route object: none2a02:e982:31::/48No route object for it. Add a route object with origin AS62571 in the RIR database for the space.636 of 636
Route object: none2a02:e980:1e::/48Route objects for it name AS19551. Add a route object with origin AS62571 in the RIR database for the space.166 of 636
Route object: none2a02:e980:25::/48Route objects for it name AS19551. Add a route object with origin AS62571 in the RIR database for the space.3 of 636
Route object: RIR192.230.75.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR192.230.76.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR198.143.36.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

185.64.8.0/22RIPENo ROA
185.64.11.0/24RIPENo ROA
2a03:10e0::/120RIPENo ROA
2a03:10e0:2::/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.