Network · data from 2026-11-12
AS51596 RUSTEKO Ltd.
Registry name: RUSTEKO-AS RUSTEKO Ltd., RU · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS51596, 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.124.150.0/23 | No ROA | RIR databaseRIPE | 671 100% |
| 176.124.152.0/21 | No ROA | RIR databaseRIPE | 671 100% |
| 178.213.144.0/21 | No ROA | RIR databaseRIPE | 671 100% |
AS-SET
PeeringDB's irr_as_set for AS51596: AS51596. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS51596 isn't in the set, or no route object for AS51596 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS51596 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS51596 | A single AS number, not a set: AS51596 (this network), 3 route objects. | |||||
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.
- ROA: none3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 176.124.150.0/23 | No ROA covers it. Add a ROA for AS51596, maxLength 23. |
| ROA: none | 176.124.152.0/21 | No ROA covers it. Add a ROA for AS51596, maxLength 21. |
| ROA: none | 178.213.144.0/21 | No ROA covers it. Add a ROA for AS51596, maxLength 21. |
Route objects not announced
Every route object with origin AS51596 is announced.
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.