bgpreport

Network · data from 2026-11-12

AS33058 PEGASYSTEMS

Registry name: PEGASYSTEMS - Pegasystems Inc., US · PeeringDB

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

Announced routes

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

2620:12a:1001::/48 No ROA None 635 100% 67
149.97.231.144/28 No ROA None 1 0%low visibility 1
131.226.28.0/24 No ROA RIR databaseARIN, RADB 673 100% 67
131.226.30.0/24 No ROA RIR databaseARIN, RADB 673 100% 67
198.22.153.0/24 No ROA RIR databaseARIN 673 100% 67
199.233.87.0/24 No ROA RIR databaseARIN, RADB 673 100% 67
207.189.166.0/24 No ROA RIR databaseARIN 673 100% 67
92.119.47.0/24 Valid None 672 100% 67

AS-SET

AS33058's PeeringDB record names no 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 13 are in fix.csv.

  • ROA: none7
  • Route object: none3
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none2620:12a:1001::/48No ROA covers it. Add a ROA for AS33058, maxLength 48.635 of 636
Route object: none2620:12a:1001::/48No route object for it. Add a route object with origin AS33058 in the RIR database for the space.635 of 636
ROA: none149.97.231.144/28No ROA covers it. Add a ROA for AS33058, maxLength 28.1 of 673
Route object: none149.97.231.144/28No route object for it. Add a route object with origin AS33058 in the RIR database for the space.1 of 673
ROA: none131.226.28.0/24No ROA covers it. Add a ROA for AS33058, maxLength 24.673 of 673
ROA: none131.226.30.0/24No ROA covers it. Add a ROA for AS33058, maxLength 24.673 of 673
ROA: none198.22.153.0/24No ROA covers it. Add a ROA for AS33058, maxLength 24.673 of 673
ROA: none199.233.87.0/24No ROA covers it. Add a ROA for AS33058, maxLength 24.673 of 673
ROA: none207.189.166.0/24No ROA covers it. Add a ROA for AS33058, maxLength 24.673 of 673
Route object: none92.119.47.0/24No route object for it. Add a route object with origin AS33058 in the RIR database for the space.672 of 673

Route objects not announced

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

38.111.236.0/24RADBNo ROA
192.233.87.0/24RADBNo ROA
204.86.198.0/23RADBNo 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.