bgpreport

Network · data from 2026-11-12

AS48840 PP Perfect Presentation For Commercial Services Company, A Saudi Joint Stock Company

Registry name: PP Perfect Presentation For Commercial Services Company, A Saudi Joint Stock Company, SA · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS48840, 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.
37.99.191.232/29 Invalid: origin None 1 0%low visibility 4
2a05:e940:120::/48 Valid Nonecovered by 2a05:e940::/29 632 99% 67
95.129.8.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
95.129.9.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
95.129.12.0/24 Valid RIR databaseRADB, RIPE 670 100% 67
95.129.8.0/21 Valid RIR databaseRADB, RIPE 669 99% 68
95.129.13.0/24 Valid RIR databaseRADB, RIPE 669 99% 68
2a05:e940::/29 Valid RIR databaseRIPE 635 100% 69
2a05:e940::/48 Valid RIR databaseRIPE 635 100% 69

AS-SET

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

  • ROA: origin1
  • Route object: none2
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: origin37.99.191.232/29ROAs covering it name AS19905, AS47794, not AS48840. If AS48840 should announce it, add a ROA for AS48840.1 of 673
Route object: none37.99.191.232/29No route object for it. Add a route object with origin AS48840 in the RIR database for the space.1 of 673
Route object: none2a05:e940:120::/48No route object for it. A route object for 2a05:e940::/29 with origin AS48840 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48840 in the RIR database for the space.632 of 636

Route objects not announced

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

95.129.10.0/24RADB, RIPEValid
95.129.11.0/24RADB, RIPEValid
95.129.14.0/24RADB, RIPEValid
95.129.15.0/24RADB, RIPEValid

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.