Network · data from 2026-11-12
AS50607 EPIX-KTW-GlobalMix Stowarzyszenie e-Poludnie
Registry name: EPIX-KTW-GlobalMix Stowarzyszenie e-Poludnie, PL · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS50607, 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.
| 2a10:f783::/48 | No ROA | RIR databaseRIPE | 624 98% |
| 91.198.97.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
| 176.126.56.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
| 176.126.57.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
| 176.126.59.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
AS-SET
AS50607 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 17 are in fix.csv.
- ROA: none1
- Route object: not announced16
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2a10:f783::/48 | No ROA covers it. Add a ROA for AS50607, maxLength 48. |
Route objects not announced
Route objects with origin AS50607 whose prefix no peer sees AS50607 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 109.207.105.0/24 | RIPE | Valid |
| 176.126.56.0/22 | RIPE | Valid |
| 176.126.58.0/24 | RIPE | Valid |
| 178.216.40.0/21 | RIPE | Invalid: origin |
| 195.191.170.0/23 | RIPE | No ROA |
| 2001:470:174::/48 | ARIN | Valid |
| 2001:470:23d::/48 | ARIN | Valid |
| 2001:470:2a1::/48 | ARIN | Valid |
| 2001:470:427::/48 | ARIN | Valid |
| 2001:470:44c::/48 | ARIN | Valid |
| 2001:470:4bd::/48 | ARIN | Valid |
| 2001:470:542::/48 | ARIN | Valid |
| 2001:470:647::/48 | ARIN | Valid |
| 2001:67c:778::/48 | RIPE | Valid |
| 2001:7f8:5b::/48 | RIPE | Invalid: origin |
| 2a10:f781:10:6483::/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.