Network · data from 2026-11-12
AS679 TUNET-AS Technische Universitat Wien
Registry name: TUNET-AS Technische Universitat Wien, AT · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS679, 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.
| 2001:629::/32 | Invalid: origin | RIR databaseRIPE | 1 0%low visibility |
| 128.130.0.0/15 | No ROA | RIR databaseRIPE | 671 100% |
| 192.35.240.0/22 | No ROA | RIR databaseRIPE | 671 100% |
AS-SET
AS679 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 8 are in fix.csv.
- ROA: origin1
- ROA: none2
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 2001:629::/32 | ROAs covering it name AS1853, not AS679. If AS679 should announce it, add a ROA for AS679. |
| ROA: none | 128.130.0.0/15 | No ROA covers it. Add a ROA for AS679, maxLength 15. |
| ROA: none | 192.35.240.0/22 | No ROA covers it. Add a ROA for AS679, maxLength 22. |
Route objects not announced
Route objects with origin AS679 whose prefix no peer sees AS679 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 192.35.244.0/24 | RIPE | No ROA |
| 193.170.72.0/21 | RIPE | Invalid: origin |
| 193.170.72.0/22 | RIPE | Invalid: origin |
| 193.170.76.0/23 | RIPE | Invalid: origin |
| 193.170.78.0/24 | RIPE | Invalid: origin |
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.