Network · data from 2026-11-12
AS49079 CONAPTO Conapto AB
Registry name: CONAPTO Conapto AB, SE · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS49079, 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.
| 89.107.208.0/20 | No ROA | RIR databaseRIPE | 673 100% |
| 45.132.44.0/22 | No ROA | RIR databaseRIPE | 671 100% |
| 185.103.212.0/22 | No ROA | RIR databaseRIPE | 671 100% |
| 193.181.161.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 193.234.180.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 195.5.111.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 185.131.20.0/22 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
AS49079 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 10 are in fix.csv.
- ROA: none6
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 89.107.208.0/20 | No ROA covers it. Add a ROA for AS49079, maxLength 20. |
| ROA: none | 45.132.44.0/22 | No ROA covers it. Add a ROA for AS49079, maxLength 22. |
| ROA: none | 185.103.212.0/22 | No ROA covers it. Add a ROA for AS49079, maxLength 22. |
| ROA: none | 193.181.161.0/24 | No ROA covers it. Add a ROA for AS49079, maxLength 24. |
| ROA: none | 193.234.180.0/24 | No ROA covers it. Add a ROA for AS49079, maxLength 24. |
| ROA: none | 195.5.111.0/24 | No ROA covers it. Add a ROA for AS49079, maxLength 24. |
Route objects not announced
Route objects with origin AS49079 whose prefix no peer sees AS49079 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 89.107.216.0/21 | RIPE | No ROA |
| 2001:67c:287c::/48 | RIPE | No ROA |
| 2a03:a020::/32 | RIPE | Valid |
| 2a03:d900::/32 | 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.