Network · data from 2026-11-12
AS15899 ERNIS-AS ERNIS SIA
Registry name: ERNIS-AS ERNIS SIA, LV · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS15899, 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.106.96.0/24 | Valid | Nonecovered by 176.106.96.0/22 | 673 100% |
| 176.106.97.0/24 | Valid | Nonecovered by 176.106.96.0/22 | 673 100% |
| 176.106.98.0/24 | Valid | Nonecovered by 176.106.96.0/22 | 673 100% |
| 176.106.99.0/24 | Valid | Nonecovered by 176.106.96.0/22 | 673 100% |
| 31.42.91.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 31.42.92.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 31.42.93.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 31.42.95.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.90.228.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.90.229.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.90.240.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.90.241.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.90.242.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.90.245.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 176.103.187.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.47.9.0/24 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS15899 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 8 are in fix.csv.
- Route object: none4
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 176.106.96.0/24 | No route object for it. A route object for 176.106.96.0/22 with origin AS15899 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15899 in the RIR database for the space. |
| Route object: none | 176.106.97.0/24 | No route object for it. A route object for 176.106.96.0/22 with origin AS15899 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15899 in the RIR database for the space. |
| Route object: none | 176.106.98.0/24 | No route object for it. A route object for 176.106.96.0/22 with origin AS15899 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15899 in the RIR database for the space. |
| Route object: none | 176.106.99.0/24 | No route object for it. A route object for 176.106.96.0/22 with origin AS15899 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15899 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS15899 whose prefix no peer sees AS15899 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 31.42.92.0/22 | RIPE | No ROA |
| 31.42.94.0/24 | RIPE | Valid |
| 91.90.228.0/23 | RIPE | Valid |
| 176.106.96.0/22 | 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.