Network · data from 2026-11-12
AS48715 SEFROYEKPARDAZENG-AS Sefroyek Pardaz Engineering PJSC
Registry name: SEFROYEKPARDAZENG-AS Sefroyek Pardaz Engineering PJSC, IR · not in PeeringDB
71IPv4 routes
97.2% RPKI valid · 87.3% with a route object
1IPv6 routes
100.0% RPKI valid · 100.0% with a route object
2RPKI invalid
2 origin · 0 maxLength
0No ROA
9 with no route object for this origin
3Low visibility
seen by under 10% of full-table peers
9Route objects not announced
registered with origin AS48715, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS48715, 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.
| 212.16.71.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 212.80.31.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 78.110.120.0/24 | Valid | Nonecovered by 78.110.120.0/22 | 671 100% |
| 78.110.122.0/24 | Valid | Nonecovered by 78.110.120.0/22 | 671 100% |
| 78.110.123.0/24 | Valid | Nonecovered by 78.110.120.0/22 | 671 100% |
| 185.58.241.0/24 | Valid | Nonecovered by 185.58.240.0/22 | 670 100% |
| 185.58.242.0/24 | Valid | Nonecovered by 185.58.240.0/22 | 670 100% |
| 185.58.243.0/24 | Valid | Nonecovered by 185.58.240.0/22 | 670 100% |
| 78.110.121.0/24 | Valid | Nonecovered by 78.110.120.0/22 | 668 99% |
| 88.135.36.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 88.135.36.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 88.135.37.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 88.135.38.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 88.135.39.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 91.236.168.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 91.236.168.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 91.236.169.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.18.212.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 185.18.213.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.36.228.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.51.200.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 185.51.200.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.51.201.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.51.202.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.51.203.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.58.240.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 185.112.149.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.112.150.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 185.112.150.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.112.151.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.128.136.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 185.128.136.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.128.137.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.128.138.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.141.104.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 185.141.104.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.141.105.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.141.106.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.141.132.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 185.141.132.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.141.133.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.141.134.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.141.135.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.170.8.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.173.129.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.173.130.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.234.14.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.235.245.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 188.209.152.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 195.110.38.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 195.211.44.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 195.211.44.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 195.211.45.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 195.211.46.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 195.211.47.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.140.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 85.133.239.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 91.247.171.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.18.214.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.18.215.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.58.240.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.128.139.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.141.107.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.206.231.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.213.195.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.252.200.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 188.209.153.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 80.71.149.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 185.18.212.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 188.209.152.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 2a0a:5e80::/48 | Valid | RIR databaseRIPE | 635 100% |
| 80.249.114.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
AS-SET
AS48715 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 20 are in fix.csv.
- ROA: origin2
- Route object: none9
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 212.16.71.0/24 | ROAs covering it name AS34837, AS44889, not AS48715. If AS48715 should announce it, add a ROA for AS48715. |
| Route object: none | 212.16.71.0/24 | Route objects for it name AS44889. Add a route object with origin AS48715 in the RIR database for the space. |
| ROA: origin | 212.80.31.0/24 | ROAs covering it name AS34837, AS44889, not AS48715. If AS48715 should announce it, add a ROA for AS48715. |
| Route object: none | 212.80.31.0/24 | Route objects for it name AS44889. Add a route object with origin AS48715 in the RIR database for the space. |
| Route object: none | 78.110.120.0/24 | No route object for it. A route object for 78.110.120.0/22 with origin AS48715 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48715 in the RIR database for the space. |
| Route object: none | 78.110.122.0/24 | No route object for it. A route object for 78.110.120.0/22 with origin AS48715 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48715 in the RIR database for the space. |
| Route object: none | 78.110.123.0/24 | No route object for it. A route object for 78.110.120.0/22 with origin AS48715 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48715 in the RIR database for the space. |
| Route object: none | 185.58.241.0/24 | No route object for it. A route object for 185.58.240.0/22 with origin AS48715 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48715 in the RIR database for the space. |
| Route object: none | 185.58.242.0/24 | No route object for it. A route object for 185.58.240.0/22 with origin AS48715 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48715 in the RIR database for the space. |
| Route object: none | 185.58.243.0/24 | No route object for it. A route object for 185.58.240.0/22 with origin AS48715 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48715 in the RIR database for the space. |
| Route object: none | 78.110.121.0/24 | No route object for it. A route object for 78.110.120.0/22 with origin AS48715 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48715 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS48715 whose prefix no peer sees AS48715 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 78.110.120.0/22 | RIPE | Valid |
| 152.89.44.0/22 | RIPE | Valid |
| 152.89.45.0/24 | RIPE | Valid |
| 152.89.47.0/24 | RIPE | Valid |
| 185.182.248.0/22 | RIPE | Valid |
| 195.110.38.0/24 | RIPE | Invalid: maxLength |
| 195.110.39.0/24 | RIPE | Invalid: maxLength |
| 2a0a:5e80::/29 | RIPE | Valid |
| 2a0a:5e80::/64 | RIPE | Valid |
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.