bgpreport

Network · data from 2026-11-12

AS16463 DPSINET - Data Processing Solutions, Inc.

Registry name: DPSINET - Data Processing Solutions, Inc., 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
11Route objects not announced registered with origin AS16463, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS16463, 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.83.192.0/21 No ROA Nonecovered by 216.83.192.0/20 673 100% 67
216.83.200.0/22 No ROA Nonecovered by 216.83.192.0/20 673 100% 67
216.83.204.0/23 No ROA Nonecovered by 216.83.192.0/20 673 100% 67

AS-SET

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

  • ROA: none3
  • Route object: none3
  • Route object: not announced11
ChangePrefix or setDetailFull-table peers
ROA: none216.83.192.0/21No ROA covers it. Add a ROA for AS16463, maxLength 21.673 of 673
Route object: none216.83.192.0/21No route object for it. A route object for 216.83.192.0/20 with origin AS16463 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16463 in the RIR database for the space.673 of 673
ROA: none216.83.200.0/22No ROA covers it. Add a ROA for AS16463, maxLength 22.673 of 673
Route object: none216.83.200.0/22No route object for it. A route object for 216.83.192.0/20 with origin AS16463 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16463 in the RIR database for the space.673 of 673
ROA: none216.83.204.0/23No ROA covers it. Add a ROA for AS16463, maxLength 23.673 of 673
Route object: none216.83.204.0/23No route object for it. A route object for 216.83.192.0/20 with origin AS16463 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16463 in the RIR database for the space.673 of 673

Route objects not announced

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

216.83.192.0/20RADBNo ROA
216.83.206.0/24RADBNo ROA
216.83.207.0/24RADBNo ROA
2607:3e80::/32RADBNo ROA
2607:3e80::/64RADBNo ROA
2607:3e80:0:1::/64RADBNo ROA
2607:3e80:0:2::/64RADBNo ROA
2607:3e80:0:3::/64RADBNo ROA
2607:3e80:0:4::/64RADBNo ROA
2607:3e80:0:5::/64RADBNo ROA
2607:3e80:0:6::/64RADBNo 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.