Network · data from 2026-11-12
AS202799 SYSECT SYSECT D.O.O.
Registry name: SYSECT SYSECT D.O.O., ME · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS202799, 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.
| 194.26.25.0/24 | No ROA | Other origin only | 2 0%low visibility |
| 212.193.31.0/24 | Valid | Other origin only | 12 2%low visibility |
| 89.19.220.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 78.17.25.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 109.237.98.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 147.45.44.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 72.56.54.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 89.19.222.0/24 | Valid | RIR databaseRIPE | 483 72% |
AS-SET
AS202799 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 6 are in fix.csv.
- ROA: none1
- Route object: none2
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 194.26.25.0/24 | No ROA covers it. Add a ROA for AS202799, maxLength 24. |
| Route object: none | 194.26.25.0/24 | Route objects for it name AS63018. Add a route object with origin AS202799 in the RIR database for the space. |
| Route object: none | 212.193.31.0/24 | Route objects for it name AS201097. Add a route object with origin AS202799 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS202799 whose prefix no peer sees AS202799 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.141.85.128/25 | RIPE | Invalid: origin |
| 89.19.221.0/24 | RIPE | Valid |
| 176.98.182.0/24 | RIPE | Valid |
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.