bgpreport

Network · data from 2026-11-12

AS395213 RAPID7 - Rapid7 Inc

Registry name: RAPID7 - Rapid7 Inc, US · not in PeeringDB

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

Announced routes

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

161.38.59.0/24 No ROA Other IRR onlyALTDB, RADB 671 100% 67
199.201.125.0/24 No ROA Other IRR onlyALTDB, RADB 671 100% 67
38.242.21.0/24 No ROA Other IRR onlyALTDB, RIPE-NONAUTH 670 100% 67
2001:4830:c100::/48 Valid None 636 100% 67
208.118.237.0/24 Valid Other IRR onlyALTDB, RIPE-NONAUTH 671 100% 67

AS-SET

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

  • ROA: none3
  • Route object: none1
  • Route object: RIR4
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none161.38.59.0/24No ROA covers it. Add a ROA for AS395213, maxLength 24.671 of 673
Route object: RIR161.38.59.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
ROA: none199.201.125.0/24No ROA covers it. Add a ROA for AS395213, maxLength 24.671 of 673
Route object: RIR199.201.125.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
ROA: none38.242.21.0/24No ROA covers it. Add a ROA for AS395213, maxLength 24.670 of 673
Route object: RIR38.242.21.0/24Route object only in ALTDB, RIPE-NONAUTH. Add it in the RIR database for the space.670 of 673
Route object: none2001:4830:c100::/48No route object for it. Add a route object with origin AS395213 in the RIR database for the space.636 of 636
Route object: RIR208.118.237.0/24Route object only in ALTDB, RIPE-NONAUTH. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

27.0.224.0/22RADBValid
64.18.136.0/22ARINValid
161.38.56.0/24RADBValid
204.10.52.0/22RADBValid

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.