Network · data from 2026-11-12
AS212112 Vladislav Novitskii
Registry name: datagio-as Vladislav Novitskii, FI · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS212112, 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.
| 13.143.130.0/23 | Invalid: origin | None | 2 0%low visibility |
| 91.92.21.0/24 | Invalid: origin | None | 2 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS212112: RIPE::AS212112:AS-NOVITSKIY. 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 (AS212112 isn't in the set, or no route object for AS212112 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 | AS212112 in it | Not covered | |
|---|---|---|---|---|---|---|
| RIPE::AS212112:AS-NOVITSKIY | In no IRR database read today. | |||||
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 11 are in fix.csv.
- ROA: origin2
- Route object: none2
- AS-SET: not found1
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 13.143.130.0/23 | ROAs covering it name AS215590, not AS212112. If AS212112 should announce it, add a ROA for AS212112. |
| Route object: none | 13.143.130.0/23 | No route object for it. Add a route object with origin AS212112 in the RIR database for the space. |
| ROA: origin | 91.92.21.0/24 | An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS212112 should announce it, add a ROA for AS212112. |
| Route object: none | 91.92.21.0/24 | No route object for it. Add a route object with origin AS212112 in the RIR database for the space. |
| AS-SET: not found | RIPE::AS212112:AS-NOVITSKIY | PeeringDB names RIPE::AS212112:AS-NOVITSKIY; no IRR database read has it. |
Route objects not announced
Route objects with origin AS212112 whose prefix no peer sees AS212112 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 191.44.118.0/24 | RIPE | Valid |
| 2a01:ecc0:600::/42 | RIPE | Valid |
| 2a0d:d940:10b::/48 | RIPE | Valid |
| 2a10:ab80:3e3::/48 | RIPE | Valid |
| 2a10:ab80:3e8::/48 | RIPE | Valid |
| 2a10:ab80:3fd::/48 | 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.