Network · data from 2026-11-12
AS31357 TOMICA-AS Limited Company Information and Consulting Agency
Registry name: TOMICA-AS Limited Company Information and Consulting Agency, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS31357, 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.
| 46.166.216.0/24 | Valid | Nonecovered by 46.166.192.0/18 | 673 100% |
| 78.140.0.0/18 | Valid | RIR databaseRIPE | 673 100% |
| 95.170.96.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 95.170.120.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 2a04:3800:2::/48 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
AS31357 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 7 are in fix.csv.
- Route object: none1
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 46.166.216.0/24 | No route object for it. A route object for 46.166.192.0/18 with origin AS31357 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31357 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS31357 whose prefix no peer sees AS31357 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 46.166.192.0/18 | RIPE | No ROA |
| 78.140.0.0/19 | RIPE | Valid |
| 78.140.48.0/20 | RIPE | Valid |
| 95.170.96.0/19 | RIPE | Valid |
| 95.170.104.0/21 | RIPE | Valid |
| 212.107.224.0/19 | 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.