Network · data from 2026-11-12
AS29046 RBK-AS Radiobaylanys LLP
Registry name: RBK-AS Radiobaylanys LLP, KZ · not in PeeringDB
42IPv4 routes
47.6% RPKI valid · 83.3% with a route object
2IPv6 routes
50.0% RPKI valid · 100.0% with a route object
1RPKI invalid
0 origin · 1 maxLength
22No ROA
7 with no route object for this origin
2Low visibility
seen by under 10% of full-table peers
4Route objects not announced
registered with origin AS29046, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS29046, 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.
| 81.18.46.0/24 | Invalid: maxLength | RIR databaseRIPE | 2 0%low visibility |
| 91.135.192.0/22 | No ROA | Nonecovered by 91.135.192.0/20 | 673 100% |
| 91.135.200.0/22 | No ROA | Nonecovered by 91.135.192.0/20 | 673 100% |
| 91.135.206.0/23 | No ROA | Nonecovered by 91.135.192.0/20 | 673 100% |
| 91.135.192.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 91.135.193.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 91.135.194.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 91.135.195.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 91.135.196.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 91.135.196.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 91.135.197.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 91.135.198.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 91.135.199.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 91.135.200.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 91.135.201.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 91.135.202.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 91.135.203.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 91.135.204.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 91.135.205.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 91.135.206.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 91.135.207.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 91.135.192.0/20 | No ROA | RIR databaseRIPE | 672 100% |
| 2a01:42e0::/32 | No ROA | RIR databaseRIPE | 636 100% |
| 185.122.32.0/24 | Valid | Nonecovered by 185.122.32.0/23 | 673 100% |
| 185.122.33.0/24 | Valid | Nonecovered by 185.122.32.0/23 | 673 100% |
| 185.122.34.0/24 | Valid | Nonecovered by 185.122.34.0/23 | 673 100% |
| 185.122.35.0/24 | Valid | Nonecovered by 185.122.34.0/23 | 673 100% |
| 81.18.32.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 81.18.33.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 81.18.34.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 81.18.35.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 81.18.38.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 81.18.39.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 81.18.41.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 81.18.42.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 81.18.43.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 81.18.44.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 81.18.45.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.122.32.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 81.18.32.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 81.18.36.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.18.37.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.18.40.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 2a01:42e0:1600::/40 | Valid | RIR databaseRIPE | 2 0%low visibility |
AS-SET
AS29046 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 34 are in fix.csv.
- ROA: maxLength1
- ROA: none22
- Route object: none7
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 81.18.46.0/24 | ROA 81.18.32.0/20 AS29046 has maxLength 20; the route is a /24. Raise the maxLength, or add a ROA for 81.18.46.0/24. |
| ROA: none | 91.135.192.0/22 | No ROA covers it. Add a ROA for AS29046, maxLength 22. |
| Route object: none | 91.135.192.0/22 | No route object for it. A route object for 91.135.192.0/20 with origin AS29046 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29046 in the RIR database for the space. |
| ROA: none | 91.135.200.0/22 | No ROA covers it. Add a ROA for AS29046, maxLength 22. |
| Route object: none | 91.135.200.0/22 | No route object for it. A route object for 91.135.192.0/20 with origin AS29046 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29046 in the RIR database for the space. |
| ROA: none | 91.135.206.0/23 | No ROA covers it. Add a ROA for AS29046, maxLength 23. |
| Route object: none | 91.135.206.0/23 | No route object for it. A route object for 91.135.192.0/20 with origin AS29046 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29046 in the RIR database for the space. |
| ROA: none | 91.135.192.0/24 | No ROA covers it. Add a ROA for AS29046, maxLength 24. |
| ROA: none | 91.135.193.0/24 | No ROA covers it. Add a ROA for AS29046, maxLength 24. |
| ROA: none | 91.135.194.0/24 | No ROA covers it. Add a ROA for AS29046, maxLength 24. |
| ROA: none | 91.135.195.0/24 | No ROA covers it. Add a ROA for AS29046, maxLength 24. |
| ROA: none | 91.135.196.0/23 | No ROA covers it. Add a ROA for AS29046, maxLength 23. |
| ROA: none | 91.135.196.0/24 | No ROA covers it. Add a ROA for AS29046, maxLength 24. |
| ROA: none | 91.135.197.0/24 | No ROA covers it. Add a ROA for AS29046, maxLength 24. |
| ROA: none | 91.135.198.0/24 | No ROA covers it. Add a ROA for AS29046, maxLength 24. |
| ROA: none | 91.135.199.0/24 | No ROA covers it. Add a ROA for AS29046, maxLength 24. |
| ROA: none | 91.135.200.0/24 | No ROA covers it. Add a ROA for AS29046, maxLength 24. |
| ROA: none | 91.135.201.0/24 | No ROA covers it. Add a ROA for AS29046, maxLength 24. |
| ROA: none | 91.135.202.0/24 | No ROA covers it. Add a ROA for AS29046, maxLength 24. |
| ROA: none | 91.135.203.0/24 | No ROA covers it. Add a ROA for AS29046, maxLength 24. |
| ROA: none | 91.135.204.0/24 | No ROA covers it. Add a ROA for AS29046, maxLength 24. |
| ROA: none | 91.135.205.0/24 | No ROA covers it. Add a ROA for AS29046, maxLength 24. |
| ROA: none | 91.135.206.0/24 | No ROA covers it. Add a ROA for AS29046, maxLength 24. |
| ROA: none | 91.135.207.0/24 | No ROA covers it. Add a ROA for AS29046, maxLength 24. |
| ROA: none | 91.135.192.0/20 | No ROA covers it. Add a ROA for AS29046, maxLength 20. |
| ROA: none | 2a01:42e0::/32 | No ROA covers it. Add a ROA for AS29046, maxLength 32. |
| Route object: none | 185.122.32.0/24 | No route object for it. A route object for 185.122.32.0/23 with origin AS29046 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29046 in the RIR database for the space. |
| Route object: none | 185.122.33.0/24 | No route object for it. A route object for 185.122.32.0/23 with origin AS29046 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29046 in the RIR database for the space. |
| Route object: none | 185.122.34.0/24 | No route object for it. A route object for 185.122.34.0/23 with origin AS29046 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29046 in the RIR database for the space. |
| Route object: none | 185.122.35.0/24 | No route object for it. A route object for 185.122.34.0/23 with origin AS29046 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29046 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS29046 whose prefix no peer sees AS29046 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 81.18.47.0/24 | RIPE | Invalid: maxLength |
| 185.122.32.0/23 | RIPE | Invalid: maxLength |
| 185.122.34.0/23 | RIPE | Invalid: maxLength |
| 2a01:42e0:1700::/40 | 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.