Network · data from 2026-11-12
AS51277 Ostrowski-as Ostrowski Sp. z o.o.
Registry name: Ostrowski-as Ostrowski Sp. z o.o., PL · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS51277, 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.
| 62.182.208.0/21 | No ROA | RIR databaseRIPE | 671 100% |
| 78.133.153.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 78.133.170.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 94.42.132.0/24 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
AS51277 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 2 are in fix.csv.
- ROA: none1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 62.182.208.0/21 | No ROA covers it. Add a ROA for AS51277, maxLength 21. |
Route objects not announced
Route objects with origin AS51277 whose prefix no peer sees AS51277 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a10:f781:10:6764::/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.