Network · data from 2026-11-12
AS15969 Systemia.pl
Registry name: Systemia-AS Systemia.pl Sp. z o.o., PL · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS15969, 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.
| 45.86.214.129/32 | Invalid: maxLength | Nonecovered by 45.86.212.0/22 | 2 0%low visibility |
| 45.86.212.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 46.227.240.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 46.227.242.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 46.227.244.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 46.227.245.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 46.227.246.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 185.7.168.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 185.7.170.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 194.187.72.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 195.110.48.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 2a01:5e00::/29 | Valid | RIR databaseRIPE | 634 100% |
| 2a01:7600::/29 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS15969: RIPE::AS15969:AS-SYSTEMIA. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS15969 isn't in the set, or no route object for AS15969 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS15969 in it | Not covered |
|---|---|---|---|---|---|
| RIPE::AS15969:AS-SYSTEMIA | RIPE | 2 | 1 | Yes | 1 |
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: maxLength1
- Route object: none1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 45.86.214.129/32 | ROA 45.86.212.0/22 AS15969 has maxLength 22; the route is a /32. Raise the maxLength, or add a ROA for 45.86.214.129/32. |
| Route object: none | 45.86.214.129/32 | No route object for it. A route object for 45.86.212.0/22 with origin AS15969 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS15969 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS15969 whose prefix no peer sees AS15969 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 46.227.240.0/21 | RIPE | No ROA |
| 194.187.72.0/24 | RIPE | Invalid: maxLength |
| 194.187.75.0/24 | RIPE | Invalid: maxLength |
| 2a10:f781:10:d494::/64 | 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.