Network · data from 2026-11-12
AS35122 SatNet-AS Satnet LTD
Registry name: SatNet-AS Satnet LTD, BG · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS35122, 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.
| 85.255.166.0/24 | Invalid: maxLength | RIR databaseRIPE | 1 0%low visibility |
| 45.146.140.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 85.255.160.0/20 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS35122 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 16 are in fix.csv.
- ROA: maxLength1
- Route object: not announced15
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 85.255.166.0/24 | ROA 85.255.160.0/20 AS35122 has maxLength 20; the route is a /24. Raise the maxLength, or add a ROA for 85.255.166.0/24. |
Route objects not announced
Route objects with origin AS35122 whose prefix no peer sees AS35122 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 85.255.160.0/24 | RIPE | Invalid: maxLength |
| 85.255.161.0/24 | RIPE | Invalid: maxLength |
| 85.255.162.0/24 | RIPE | Invalid: maxLength |
| 85.255.163.0/24 | RIPE | Invalid: maxLength |
| 85.255.164.0/24 | RIPE | Invalid: maxLength |
| 85.255.165.0/24 | RIPE | Invalid: maxLength |
| 85.255.167.0/24 | RIPE | Invalid: maxLength |
| 85.255.168.0/24 | RIPE | Invalid: maxLength |
| 85.255.169.0/24 | RIPE | Invalid: maxLength |
| 85.255.170.0/24 | RIPE | Invalid: maxLength |
| 85.255.171.0/24 | RIPE | Invalid: maxLength |
| 85.255.172.0/24 | RIPE | Invalid: maxLength |
| 85.255.173.0/24 | RIPE | Invalid: maxLength |
| 85.255.174.0/24 | RIPE | Invalid: maxLength |
| 85.255.175.0/24 | RIPE | Invalid: maxLength |
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.