Network · data from 2026-11-12
AS44285 SEFROYEKPARDAZENG-AS Sefroyek Pardaz Engineering PJSC
Registry name: SEFROYEKPARDAZENG-AS Sefroyek Pardaz Engineering PJSC, IR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS44285, 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.
| 185.182.248.0/23 | Invalid: origin | RIR databaseRIPE | 2 0%low visibility |
| 185.182.250.0/23 | Invalid: origin | RIR databaseRIPE | 2 0%low visibility |
| 45.87.4.0/23 | Valid | None | 671 100% |
| 46.28.78.0/23 | Valid | Other origin onlycovered by 46.28.72.0/21 | 671 100% |
| 84.47.230.0/23 | Valid | Nonecovered by 84.47.228.0/22 | 671 100% |
| 85.198.24.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 85.198.27.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.121.130.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 5.1.43.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 37.32.32.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 37.75.243.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 37.75.244.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 37.75.245.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 37.75.246.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 37.75.247.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 45.140.224.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 84.47.224.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 84.47.225.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 84.47.226.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 84.47.227.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 84.47.228.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 84.47.229.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 84.47.230.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 84.47.231.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.198.24.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.198.25.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.198.26.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.121.128.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.121.129.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.121.131.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.171.54.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 185.171.55.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 217.172.120.0/21 | Valid | RIR databaseRIPE | 671 100% |
| 45.9.252.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 45.9.253.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 45.9.254.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 46.28.72.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 46.28.73.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 46.28.74.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 46.28.75.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 46.28.76.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 46.28.77.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 2a02:828::/48 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
AS44285 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 37 are in fix.csv.
- ROA: origin2
- Route object: none3
- Route object: not announced32
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 185.182.248.0/23 | ROAs covering it name AS48715, not AS44285. If AS44285 should announce it, add a ROA for AS44285. |
| ROA: origin | 185.182.250.0/23 | ROAs covering it name AS48715, not AS44285. If AS44285 should announce it, add a ROA for AS44285. |
| Route object: none | 45.87.4.0/23 | No route object for it. Add a route object with origin AS44285 in the RIR database for the space. |
| Route object: none | 46.28.78.0/23 | Route objects for it name AS58053. A route object for 46.28.72.0/21 with origin AS44285 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44285 in the RIR database for the space. |
| Route object: none | 84.47.230.0/23 | No route object for it. A route object for 84.47.228.0/22 with origin AS44285 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44285 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS44285 whose prefix no peer sees AS44285 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 37.32.32.0/21 | RIPE | No ROA |
| 37.75.244.0/22 | RIPE | Valid |
| 45.9.252.0/22 | RIPE | Valid |
| 45.9.252.0/23 | RIPE | Valid |
| 45.9.254.0/23 | RIPE | Valid |
| 45.156.180.0/22 | RIPE | Valid |
| 46.28.72.0/21 | RIPE | Valid |
| 80.249.114.0/24 | RIPE | Valid |
| 84.47.224.0/21 | RIPE | Valid |
| 84.47.224.0/22 | RADB, RIPE | Valid |
| 84.47.228.0/22 | RIPE | Valid |
| 185.121.128.0/22 | RIPE | Valid |
| 185.121.130.0/23 | RIPE | Valid |
| 185.182.250.0/24 | RIPE | Invalid: origin |
| 185.182.251.0/24 | RIPE | Invalid: origin |
| 188.209.152.0/23 | RIPE | Valid |
| 195.110.38.0/24 | RIPE | Valid |
| 195.110.39.0/24 | RIPE | Valid |
| 217.172.120.0/24 | RIPE | Valid |
| 217.172.124.0/23 | RIPE | Valid |
| 217.172.126.0/23 | RIPE | Valid |
| 2a02:828::/29 | RIPE | Valid |
| 2a02:828::/32 | RIPE | Valid |
| 2a02:828::/64 | RIPE | Valid |
| 2a02:828:1::/48 | RIPE | Valid |
| 2a02:829::/32 | RIPE | Valid |
| 2a02:82a::/32 | RIPE | Valid |
| 2a02:82b::/32 | RIPE | Valid |
| 2a02:82c::/32 | RIPE | Valid |
| 2a02:82d::/32 | RIPE | Valid |
| 2a02:82e::/32 | RIPE | Valid |
| 2a02:82f::/32 | 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.