Network · data from 2026-11-12
AS35526 MASTERBIT-AS Smart Technology LLC
Registry name: MASTERBIT-AS Smart Technology LLC, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS35526, 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.100.254.0/24 | No ROA | Nonecovered by 176.100.252.0/22 | 673 100% |
| 91.218.108.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 91.218.109.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 176.100.240.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 176.100.255.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.93.40.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.93.41.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.93.42.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.93.43.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.200.120.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 194.88.210.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 176.100.243.0/24 | No ROA | RIR databaseRIPE | 670 100% |
| 91.218.111.0/24 | No ROA | RIR databaseRIPE | 667 99% |
| 2a05:f640::/29 | No ROA | RIR databaseRIPE | 635 100% |
AS-SET
AS35526 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 22 are in fix.csv.
- ROA: none14
- Route object: none1
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 176.100.254.0/24 | No ROA covers it. Add a ROA for AS35526, maxLength 24. |
| Route object: none | 176.100.254.0/24 | No route object for it. A route object for 176.100.252.0/22 with origin AS35526 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35526 in the RIR database for the space. |
| ROA: none | 91.218.108.0/24 | No ROA covers it. Add a ROA for AS35526, maxLength 24. |
| ROA: none | 91.218.109.0/24 | No ROA covers it. Add a ROA for AS35526, maxLength 24. |
| ROA: none | 176.100.240.0/22 | No ROA covers it. Add a ROA for AS35526, maxLength 22. |
| ROA: none | 176.100.255.0/24 | No ROA covers it. Add a ROA for AS35526, maxLength 24. |
| ROA: none | 185.93.40.0/24 | No ROA covers it. Add a ROA for AS35526, maxLength 24. |
| ROA: none | 185.93.41.0/24 | No ROA covers it. Add a ROA for AS35526, maxLength 24. |
| ROA: none | 185.93.42.0/24 | No ROA covers it. Add a ROA for AS35526, maxLength 24. |
| ROA: none | 185.93.43.0/24 | No ROA covers it. Add a ROA for AS35526, maxLength 24. |
| ROA: none | 185.200.120.0/24 | No ROA covers it. Add a ROA for AS35526, maxLength 24. |
| ROA: none | 194.88.210.0/23 | No ROA covers it. Add a ROA for AS35526, maxLength 23. |
| ROA: none | 176.100.243.0/24 | No ROA covers it. Add a ROA for AS35526, maxLength 24. |
| ROA: none | 91.218.111.0/24 | No ROA covers it. Add a ROA for AS35526, maxLength 24. |
| ROA: none | 2a05:f640::/29 | No ROA covers it. Add a ROA for AS35526, maxLength 29. |
Route objects not announced
Route objects with origin AS35526 whose prefix no peer sees AS35526 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 91.218.108.0/22 | RIPE | No ROA |
| 176.100.252.0/22 | RIPE | No ROA |
| 185.93.40.0/22 | RIPE | No ROA |
| 194.88.210.0/24 | RIPE | No ROA |
| 194.88.211.0/24 | RIPE | No ROA |
| 2001:678:65c::/48 | RIPE | No ROA |
| 2a05:f640:1000::/36 | 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.