Network · data from 2026-11-12
AS59444 AMSNET Andrzej Szreter
Registry name: ASAMSNET Andrzej Szreter AMSNET, PL · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS59444, 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.
| 176.121.86.0/24 | Valid | Other origin onlycovered by 176.121.80.0/21 | 671 100% |
| 176.121.80.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 176.121.84.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 176.121.85.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 176.121.87.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 195.64.174.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 195.64.175.0/24 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
AS59444'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 3 are in fix.csv.
- Route object: none1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 176.121.86.0/24 | Route objects for it name AS41142. A route object for 176.121.80.0/21 with origin AS59444 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59444 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS59444 whose prefix no peer sees AS59444 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 176.121.80.0/21 | RIPE | No ROA |
| 2a10:f781:10:65ce::/64 | 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.