Network · data from 2026-11-12
AS47909 Baikal-Telecom Ltd.
Registry name: BAIKAL-AS BAIKAL TELECOM LLC, RU · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS47909, 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.
| 94.154.80.0/32 | No ROA | Nonecovered by 94.154.80.0/24 | 7 1%low visibility |
| 94.154.87.255/32 | No ROA | Nonecovered by 94.154.87.0/24 | 5 1%low visibility |
| 94.154.80.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 94.154.80.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 94.154.81.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 94.154.82.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 94.154.83.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 94.154.84.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 94.154.85.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 94.154.86.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 94.154.87.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 194.143.148.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 194.143.148.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 194.143.149.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 2a02:2808:2001::/48 | No ROA | RIR databaseRIPE | 636 100% |
| 2a05:a7c7::/32 | Valid | RIR databaseRIPE | 636 100% |
AS-SET
AS47909's PeeringDB record names no 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 23 are in fix.csv.
- ROA: none15
- Route object: none2
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 94.154.80.0/32 | No ROA covers it. Add a ROA for AS47909, maxLength 32. |
| Route object: none | 94.154.80.0/32 | No route object for it. A route object for 94.154.80.0/24 with origin AS47909 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS47909 in the RIR database for the space. |
| ROA: none | 94.154.87.255/32 | No ROA covers it. Add a ROA for AS47909, maxLength 32. |
| Route object: none | 94.154.87.255/32 | No route object for it. A route object for 94.154.87.0/24 with origin AS47909 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS47909 in the RIR database for the space. |
| ROA: none | 94.154.80.0/21 | No ROA covers it. Add a ROA for AS47909, maxLength 21. |
| ROA: none | 94.154.80.0/24 | No ROA covers it. Add a ROA for AS47909, maxLength 24. |
| ROA: none | 94.154.81.0/24 | No ROA covers it. Add a ROA for AS47909, maxLength 24. |
| ROA: none | 94.154.82.0/24 | No ROA covers it. Add a ROA for AS47909, maxLength 24. |
| ROA: none | 94.154.83.0/24 | No ROA covers it. Add a ROA for AS47909, maxLength 24. |
| ROA: none | 94.154.84.0/24 | No ROA covers it. Add a ROA for AS47909, maxLength 24. |
| ROA: none | 94.154.85.0/24 | No ROA covers it. Add a ROA for AS47909, maxLength 24. |
| ROA: none | 94.154.86.0/24 | No ROA covers it. Add a ROA for AS47909, maxLength 24. |
| ROA: none | 94.154.87.0/24 | No ROA covers it. Add a ROA for AS47909, maxLength 24. |
| ROA: none | 194.143.148.0/23 | No ROA covers it. Add a ROA for AS47909, maxLength 23. |
| ROA: none | 194.143.148.0/24 | No ROA covers it. Add a ROA for AS47909, maxLength 24. |
| ROA: none | 194.143.149.0/24 | No ROA covers it. Add a ROA for AS47909, maxLength 24. |
| ROA: none | 2a02:2808:2001::/48 | No ROA covers it. Add a ROA for AS47909, maxLength 48. |
Route objects not announced
Route objects with origin AS47909 whose prefix no peer sees AS47909 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 194.143.148.76/30 | RIPE | No ROA |
| 194.143.149.32/28 | RIPE | No ROA |
| 194.143.149.48/28 | RIPE | No ROA |
| 194.143.149.64/26 | RIPE | No ROA |
| 194.143.149.128/29 | RIPE | No ROA |
| 194.143.149.144/28 | 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.