Network · data from 2026-11-12
AS51929 IT-mastaren Mitt AB
Registry name: ITM-SE Advania Sverige AB, SE · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS51929, 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.
| 81.94.160.0/21 | No ROA | RIR databaseRIPE | 670 100% |
| 81.94.168.0/23 | No ROA | RIR databaseRIPE | 668 99% |
| 81.94.170.0/23 | No ROA | RIR databaseRIPE | 668 99% |
| 81.94.172.0/22 | No ROA | RIR databaseRIPE | 668 99% |
| 81.94.172.0/23 | No ROA | RIR databaseRIPE | 668 99% |
| 81.94.174.0/23 | No ROA | RIR databaseRIPE | 668 99% |
| 185.58.76.0/22 | No ROA | RIR databaseRIPE | 668 99% |
| 193.180.206.0/24 | No ROA | RIR databaseRIPE | 668 99% |
| 193.183.200.0/22 | No ROA | RIR databaseRIPE | 668 99% |
| 2a00:7800::/32 | No ROA | RIR databaseRIPE | 2 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS51929: AS-ITMASTAREN. 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 (AS51929 isn't in the set, or no route object for AS51929 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 | AS51929 in it | Not covered |
|---|---|---|---|---|---|
| AS-ITMASTAREN | RIPE | 6 | 1 | Yes | 0 |
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 11 are in fix.csv.
- ROA: none10
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 81.94.160.0/21 | No ROA covers it. Add a ROA for AS51929, maxLength 21. |
| ROA: none | 81.94.168.0/23 | No ROA covers it. Add a ROA for AS51929, maxLength 23. |
| ROA: none | 81.94.170.0/23 | No ROA covers it. Add a ROA for AS51929, maxLength 23. |
| ROA: none | 81.94.172.0/22 | No ROA covers it. Add a ROA for AS51929, maxLength 22. |
| ROA: none | 81.94.172.0/23 | No ROA covers it. Add a ROA for AS51929, maxLength 23. |
| ROA: none | 81.94.174.0/23 | No ROA covers it. Add a ROA for AS51929, maxLength 23. |
| ROA: none | 185.58.76.0/22 | No ROA covers it. Add a ROA for AS51929, maxLength 22. |
| ROA: none | 193.180.206.0/24 | No ROA covers it. Add a ROA for AS51929, maxLength 24. |
| ROA: none | 193.183.200.0/22 | No ROA covers it. Add a ROA for AS51929, maxLength 22. |
| ROA: none | 2a00:7800::/32 | No ROA covers it. Add a ROA for AS51929, maxLength 32. |
Route objects not announced
Route objects with origin AS51929 whose prefix no peer sees AS51929 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 193.180.100.0/22 | 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.