Network · data from 2026-11-12
AS205963 BURGERKING-AS BURGER RUS LLC
Registry name: BURGERKING-AS BURGER RUS LLC, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS205963, 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.
| 185.200.216.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 185.200.216.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.200.218.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 185.200.218.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.200.219.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.200.217.0/24 | No ROA | RIR databaseRIPE | 671 100% |
AS-SET
AS205963 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.
- ROA: none6
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 185.200.216.0/23 | No ROA covers it. Add a ROA for AS205963, maxLength 23. |
| ROA: none | 185.200.216.0/24 | No ROA covers it. Add a ROA for AS205963, maxLength 24. |
| ROA: none | 185.200.218.0/23 | No ROA covers it. Add a ROA for AS205963, maxLength 23. |
| ROA: none | 185.200.218.0/24 | No ROA covers it. Add a ROA for AS205963, maxLength 24. |
| ROA: none | 185.200.219.0/24 | No ROA covers it. Add a ROA for AS205963, maxLength 24. |
| ROA: none | 185.200.217.0/24 | No ROA covers it. Add a ROA for AS205963, maxLength 24. |
Route objects not announced
Route objects with origin AS205963 whose prefix no peer sees AS205963 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a0a:b8c0::/32 | 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.