bgpreport

Network · data from 2026-11-12

AS22511 PRESIDIONS - Presidio Networked Solutions LLC

Registry name: PRESIDIONS - Presidio Networked Solutions LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS22511, 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.0.156.0/24 No ROA Other origin only 671 100% 67
8.30.84.0/24 No ROA Other IRR onlyRADB 672 100% 67
206.128.133.0/24 No ROA Other IRR onlyRADB 672 100% 67
207.30.28.0/24 No ROA Other IRR onlyRADB 672 100% 67
207.30.29.0/24 No ROA Other IRR onlyRADB 672 100% 67
74.114.131.0/24 No ROA RIR databaseARIN, RADB 672 100% 67
74.114.128.0/24 No ROA RIR databaseARIN, RADB 671 100% 67
74.114.129.0/24 No ROA RIR databaseARIN, RADB 671 100% 67
74.114.130.0/24 No ROA RIR databaseARIN, RADB 671 100% 67

AS-SET

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

  • ROA: none9
  • Route object: none1
  • Route object: RIR4
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none216.0.156.0/24No ROA covers it. Add a ROA for AS22511, maxLength 24.671 of 673
Route object: none216.0.156.0/24Route objects for it name AS198949. Add a route object with origin AS22511 in the RIR database for the space.671 of 673
ROA: none8.30.84.0/24No ROA covers it. Add a ROA for AS22511, maxLength 24.672 of 673
Route object: RIR8.30.84.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none206.128.133.0/24No ROA covers it. Add a ROA for AS22511, maxLength 24.672 of 673
Route object: RIR206.128.133.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none207.30.28.0/24No ROA covers it. Add a ROA for AS22511, maxLength 24.672 of 673
Route object: RIR207.30.28.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none207.30.29.0/24No ROA covers it. Add a ROA for AS22511, maxLength 24.672 of 673
Route object: RIR207.30.29.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none74.114.131.0/24No ROA covers it. Add a ROA for AS22511, maxLength 24.672 of 673
ROA: none74.114.128.0/24No ROA covers it. Add a ROA for AS22511, maxLength 24.671 of 673
ROA: none74.114.129.0/24No ROA covers it. Add a ROA for AS22511, maxLength 24.671 of 673
ROA: none74.114.130.0/24No ROA covers it. Add a ROA for AS22511, maxLength 24.671 of 673

Route objects not announced

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

8.36.68.0/24ARINNo ROA
64.191.3.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.