bgpreport

Network · data from 2026-11-12

AS399768 VER-CT-ASN-01 - Verition Group LLC

Registry name: VER-CT-ASN-01 - Verition Group LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS399768, 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.
216.245.156.0/23 No ROA Other IRR onlyRADB 673 100% 67
216.245.156.0/24 No ROA Other IRR onlyRADB 673 100% 67
216.245.157.0/24 No ROA Other IRR onlyRADB 673 100% 67
198.62.197.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
92.51.224.0/22 Valid Other IRR onlyRADB 673 100% 67
92.51.224.0/24 Valid Other IRR onlyRADB 673 100% 67
92.51.225.0/24 Valid Other IRR onlyRADB 673 100% 67
92.51.226.0/24 Valid Other IRR onlyRADB 673 100% 67
203.77.161.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
203.77.160.0/23 Valid RIR databaseAPNIC, RADB 672 100% 66
203.77.160.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67

AS-SET

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

  • ROA: none4
  • Route object: RIR8
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none216.245.156.0/23No ROA covers it. Add a ROA for AS399768, maxLength 23.673 of 673
Route object: RIR216.245.156.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none216.245.156.0/24No ROA covers it. Add a ROA for AS399768, maxLength 24.673 of 673
Route object: RIR216.245.156.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none216.245.157.0/24No ROA covers it. Add a ROA for AS399768, maxLength 24.673 of 673
Route object: RIR216.245.157.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none198.62.197.0/24No ROA covers it. Add a ROA for AS399768, maxLength 24.2 of 673
Route object: RIR198.62.197.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR92.51.224.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR92.51.224.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR92.51.225.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR92.51.226.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

92.51.224.0/21RADB, RIPENo ROA
160.72.146.0/24ARINNo 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.