bgpreport

Network · data from 2026-11-12

AS49148 ADPDIGITAL-AS Atieh Dadeh Pardaz PJSC

Registry name: ADPDIGITAL-AS Atieh Dadeh Pardaz PJSC, IR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS49148, 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.
95.130.247.0/24 Valid Nonecovered by 95.130.240.0/21 671 100% 67
95.130.245.0/24 Valid Nonecovered by 95.130.240.0/21 670 100% 66
185.160.176.0/24 Valid RIR databaseRIPE 671 100% 67
185.160.177.0/24 Valid RIR databaseRIPE 671 100% 67
185.160.178.0/24 Valid RIR databaseRIPE 671 100% 67
185.160.179.0/24 Valid RIR databaseRIPE 671 100% 67
95.130.240.0/24 Valid RIR databaseRIPE 670 100% 66
95.130.241.0/24 Valid RIR databaseRIPE 670 100% 66
95.130.242.0/24 Valid RIR databaseRIPE 670 100% 66
95.130.243.0/24 Valid RIR databaseRIPE 670 100% 66
95.130.244.0/24 Valid RIR databaseRIPE 670 100% 66
2a00:b140::/32 Valid RIR databaseRIPE 634 100% 68

AS-SET

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

  • Route object: none2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none95.130.247.0/24No route object for it. A route object for 95.130.240.0/21 with origin AS49148 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49148 in the RIR database for the space.671 of 673
Route object: none95.130.245.0/24No route object for it. A route object for 95.130.240.0/21 with origin AS49148 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49148 in the RIR database for the space.670 of 673

Route objects not announced

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

95.130.240.0/21RIPEValid
185.160.176.0/22RIPEValid

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.