Network · data from 2026-11-12
AS16037 TETRAPAK-AS AB Tetra Pak
Registry name: TETRAPAK-AS AB Tetra Pak, SE · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS16037, 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.
| 151.183.32.0/20 | No ROA | Other origin onlycovered by 151.183.0.0/16 | 672 100% |
| 151.183.34.0/23 | No ROA | Other origin onlycovered by 151.183.0.0/16 | 672 100% |
| 151.183.16.0/20 | No ROA | Other IRR onlyRADB | 673 100% |
| 151.183.0.0/20 | No ROA | RIR databaseRIPE | 673 100% |
| 151.183.2.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 151.183.255.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 151.183.4.0/23 | No ROA | RIR databaseRIPE | 671 100% |
AS-SET
AS16037 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 12 are in fix.csv.
- ROA: none7
- Route object: none2
- Route object: RIR1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 151.183.32.0/20 | No ROA covers it. Add a ROA for AS16037, maxLength 20. |
| Route object: none | 151.183.32.0/20 | Route objects for it name AS17554. A route object for 151.183.0.0/16 with origin AS16037 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16037 in the RIR database for the space. |
| ROA: none | 151.183.34.0/23 | No ROA covers it. Add a ROA for AS16037, maxLength 23. |
| Route object: none | 151.183.34.0/23 | Route objects for it name AS17554. A route object for 151.183.0.0/16 with origin AS16037 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16037 in the RIR database for the space. |
| ROA: none | 151.183.16.0/20 | No ROA covers it. Add a ROA for AS16037, maxLength 20. |
| Route object: RIR | 151.183.16.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 151.183.0.0/20 | No ROA covers it. Add a ROA for AS16037, maxLength 20. |
| ROA: none | 151.183.2.0/23 | No ROA covers it. Add a ROA for AS16037, maxLength 23. |
| ROA: none | 151.183.255.0/24 | No ROA covers it. Add a ROA for AS16037, maxLength 24. |
| ROA: none | 151.183.4.0/23 | No ROA covers it. Add a ROA for AS16037, maxLength 23. |
Route objects not announced
Route objects with origin AS16037 whose prefix no peer sees AS16037 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 151.183.0.0/16 | RIPE | No ROA |
| 151.183.6.0/23 | 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.