Network · data from 2026-11-12
AS59862 Professional Link
Registry name: PLINK-AS Professional Link S.r.l., IT · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS59862, 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.
| 156.67.20.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 157.97.160.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 157.97.162.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 212.48.188.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 84.247.36.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 85.8.172.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 85.204.172.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 93.119.20.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 93.119.22.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 153.92.176.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 176.223.88.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 185.63.88.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.195.4.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 188.215.20.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 2a03:a60::/32 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
AS59862'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 53 are in fix.csv.
- ROA: none4
- Route object: not announced49
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 156.67.20.0/22 | No ROA covers it. Add a ROA for AS59862, maxLength 22. |
| ROA: none | 157.97.160.0/23 | No ROA covers it. Add a ROA for AS59862, maxLength 23. |
| ROA: none | 157.97.162.0/24 | No ROA covers it. Add a ROA for AS59862, maxLength 24. |
| ROA: none | 212.48.188.0/22 | No ROA covers it. Add a ROA for AS59862, maxLength 22. |
Route objects not announced
Route objects with origin AS59862 whose prefix no peer sees AS59862 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 80.173.224.0/22 | RIPE | No ROA |
| 80.173.224.0/24 | RIPE | No ROA |
| 80.173.225.0/24 | RIPE | No ROA |
| 80.173.226.0/24 | RIPE | No ROA |
| 80.173.227.0/24 | RIPE | No ROA |
| 84.247.36.0/24 | RIPE | Invalid: maxLength |
| 84.247.37.0/24 | RIPE | Invalid: maxLength |
| 84.247.38.0/24 | RIPE | Invalid: maxLength |
| 84.247.39.0/24 | RIPE | Invalid: maxLength |
| 85.8.172.0/24 | RIPE | Invalid: maxLength |
| 85.8.173.0/24 | RIPE | Invalid: maxLength |
| 85.8.174.0/24 | RIPE | Invalid: maxLength |
| 85.8.175.0/24 | RIPE | Invalid: maxLength |
| 85.204.172.0/24 | RIPE | Valid |
| 85.204.173.0/24 | RIPE | Valid |
| 85.204.174.0/24 | RIPE | Valid |
| 85.204.175.0/24 | RIPE | Valid |
| 93.119.20.0/22 | RIPE | No ROA |
| 93.119.20.0/24 | RIPE | Valid |
| 93.119.21.0/24 | RIPE | Valid |
| 93.119.23.0/24 | RIPE | No ROA |
| 153.92.176.0/24 | RIPE | Valid |
| 153.92.177.0/24 | RIPE | Valid |
| 153.92.178.0/24 | RIPE | Valid |
| 153.92.179.0/24 | RIPE | Valid |
| 156.67.20.0/24 | RIPE | No ROA |
| 156.67.21.0/24 | RIPE | No ROA |
| 156.67.22.0/24 | RIPE | No ROA |
| 156.67.23.0/24 | RIPE | No ROA |
| 157.97.160.0/24 | RIPE | No ROA |
| 157.97.161.0/24 | RIPE | No ROA |
| 176.223.88.0/22 | RIPE | Valid |
| 176.223.92.0/22 | RIPE | Valid |
| 185.63.88.0/24 | RIPE | Valid |
| 185.63.89.0/24 | RIPE | Valid |
| 185.63.90.0/24 | RIPE | Valid |
| 185.63.91.0/24 | RIPE | Valid |
| 185.195.4.0/24 | RIPE | Invalid: maxLength |
| 185.195.5.0/24 | RIPE | Invalid: maxLength |
| 185.195.6.0/24 | RIPE | Invalid: maxLength |
| 185.195.7.0/24 | RIPE | Invalid: maxLength |
| 188.215.20.0/24 | RIPE | Valid |
| 188.215.21.0/24 | RIPE | Valid |
| 188.215.22.0/24 | RIPE | Valid |
| 188.215.23.0/24 | RIPE | Valid |
| 212.48.188.0/24 | RIPE | No ROA |
| 212.48.189.0/24 | RIPE | No ROA |
| 212.48.190.0/24 | RIPE | No ROA |
| 212.48.191.0/24 | RIPE | No 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.