Network · data from 2026-11-12
AS50537 QSS-AS QSS D.O.O. Sarajevo
Registry name: QSS-AS QSS D.O.O. Sarajevo, BA · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS50537, 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.
| 109.205.32.0/21 | No ROA | RIR databaseRIPE | 671 100% |
| 109.205.32.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 109.205.33.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 109.205.34.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 109.205.35.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 109.205.36.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 109.205.37.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 109.205.38.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 109.205.39.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 193.222.144.0/22 | No ROA | RIR databaseRIPE | 671 100% |
| 193.222.145.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 2a0c:1600::/32 | No ROA | RIR databaseRIPE | 635 100% |
AS-SET
AS50537 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 15 are in fix.csv.
- ROA: none12
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 109.205.32.0/21 | No ROA covers it. Add a ROA for AS50537, maxLength 21. |
| ROA: none | 109.205.32.0/24 | No ROA covers it. Add a ROA for AS50537, maxLength 24. |
| ROA: none | 109.205.33.0/24 | No ROA covers it. Add a ROA for AS50537, maxLength 24. |
| ROA: none | 109.205.34.0/24 | No ROA covers it. Add a ROA for AS50537, maxLength 24. |
| ROA: none | 109.205.35.0/24 | No ROA covers it. Add a ROA for AS50537, maxLength 24. |
| ROA: none | 109.205.36.0/24 | No ROA covers it. Add a ROA for AS50537, maxLength 24. |
| ROA: none | 109.205.37.0/24 | No ROA covers it. Add a ROA for AS50537, maxLength 24. |
| ROA: none | 109.205.38.0/24 | No ROA covers it. Add a ROA for AS50537, maxLength 24. |
| ROA: none | 109.205.39.0/24 | No ROA covers it. Add a ROA for AS50537, maxLength 24. |
| ROA: none | 193.222.144.0/22 | No ROA covers it. Add a ROA for AS50537, maxLength 22. |
| ROA: none | 193.222.145.0/24 | No ROA covers it. Add a ROA for AS50537, maxLength 24. |
| ROA: none | 2a0c:1600::/32 | No ROA covers it. Add a ROA for AS50537, maxLength 32. |
Route objects not announced
Route objects with origin AS50537 whose prefix no peer sees AS50537 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 193.222.144.0/24 | RIPE | No ROA |
| 193.222.146.0/24 | RIPE | No ROA |
| 193.222.147.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.