Network · data from 2026-11-12
AS35546 NORTHSTAR Northstar Technology Company W.L.L.
Registry name: NORTHSTAR Northstar Technology Company W.L.L., BH · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS35546, 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.
| 80.241.144.0/24 | Valid | Nonecovered by 80.241.144.0/21 | 671 100% |
| 80.241.145.0/24 | Valid | Nonecovered by 80.241.144.0/21 | 671 100% |
| 80.241.146.0/24 | Valid | Nonecovered by 80.241.144.0/21 | 671 100% |
| 80.241.147.0/24 | Valid | Nonecovered by 80.241.144.0/21 | 671 100% |
| 80.241.144.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 80.241.153.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 80.241.154.0/24 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
AS35546 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 11 are in fix.csv.
- Route object: none4
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 80.241.144.0/24 | No route object for it. A route object for 80.241.144.0/21 with origin AS35546 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35546 in the RIR database for the space. |
| Route object: none | 80.241.145.0/24 | No route object for it. A route object for 80.241.144.0/21 with origin AS35546 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35546 in the RIR database for the space. |
| Route object: none | 80.241.146.0/24 | No route object for it. A route object for 80.241.144.0/21 with origin AS35546 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35546 in the RIR database for the space. |
| Route object: none | 80.241.147.0/24 | No route object for it. A route object for 80.241.144.0/21 with origin AS35546 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35546 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS35546 whose prefix no peer sees AS35546 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 80.241.144.0/20 | RADB | No ROA |
| 80.241.152.0/21 | RADB | No ROA |
| 80.241.152.0/24 | RIPE | No ROA |
| 80.241.155.0/24 | RIPE | No ROA |
| 80.241.156.0/24 | RIPE | No ROA |
| 80.241.157.0/24 | RIPE | No ROA |
| 80.241.158.0/24 | 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.