Network · data from 2026-11-12
AS12831 TASK-AS Technical University of Gdansk, Academic Computer Center TASK
Registry name: TASK-AS Technical University of Gdansk, Academic Computer Center TASK, PL · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS12831, 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.
| 91.194.106.0/23 | No ROA | RIR databaseRIPE | 672 100% |
| 91.209.116.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 178.217.248.0/21 | No ROA | RIR databaseRIPE | 672 100% |
| 194.169.236.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 89.191.160.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 89.191.176.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 91.221.26.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 91.244.248.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 213.192.64.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 213.192.80.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 213.192.96.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 213.192.112.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 2001:4070:8000::/33 | Valid | RIR databaseRIPE | 636 100% |
AS-SET
AS12831 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 4 are in fix.csv.
- ROA: none4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 91.194.106.0/23 | No ROA covers it. Add a ROA for AS12831, maxLength 23. |
| ROA: none | 91.209.116.0/24 | No ROA covers it. Add a ROA for AS12831, maxLength 24. |
| ROA: none | 178.217.248.0/21 | No ROA covers it. Add a ROA for AS12831, maxLength 21. |
| ROA: none | 194.169.236.0/24 | No ROA covers it. Add a ROA for AS12831, maxLength 24. |
Route objects not announced
Every route object with origin AS12831 is announced.
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.