Network · data from 2026-11-12
AS133013 ABBVIEINC-AS-AP - AbbVie, Inc.
Registry name: ABBVIEINC-AS-AP - AbbVie, Inc., SG · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS133013, 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.
| 159.180.177.0/24 | No ROA | Nonecovered by 159.180.176.0/22 | 673 100% |
| 159.180.179.0/24 | No ROA | Nonecovered by 159.180.176.0/22 | 673 100% |
| 159.180.180.0/24 | No ROA | Nonecovered by 159.180.176.0/21 | 673 100% |
| 159.180.181.0/24 | No ROA | Nonecovered by 159.180.176.0/21 | 673 100% |
| 159.180.182.0/24 | No ROA | Nonecovered by 159.180.176.0/21 | 673 100% |
| 159.180.183.0/24 | No ROA | Nonecovered by 159.180.176.0/21 | 673 100% |
| 159.180.176.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 159.180.176.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 159.180.178.0/24 | No ROA | RIR databaseRIPE | 673 100% |
AS-SET
AS133013 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 16 are in fix.csv.
- ROA: none9
- Route object: none6
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 159.180.177.0/24 | No ROA covers it. Add a ROA for AS133013, maxLength 24. |
| Route object: none | 159.180.177.0/24 | No route object for it. A route object for 159.180.176.0/22 with origin AS133013 covers it (filters allowing more-specifics accept it). Add a route object with origin AS133013 in the RIR database for the space. |
| ROA: none | 159.180.179.0/24 | No ROA covers it. Add a ROA for AS133013, maxLength 24. |
| Route object: none | 159.180.179.0/24 | No route object for it. A route object for 159.180.176.0/22 with origin AS133013 covers it (filters allowing more-specifics accept it). Add a route object with origin AS133013 in the RIR database for the space. |
| ROA: none | 159.180.180.0/24 | No ROA covers it. Add a ROA for AS133013, maxLength 24. |
| Route object: none | 159.180.180.0/24 | No route object for it. A route object for 159.180.176.0/21 with origin AS133013 covers it (filters allowing more-specifics accept it). Add a route object with origin AS133013 in the RIR database for the space. |
| ROA: none | 159.180.181.0/24 | No ROA covers it. Add a ROA for AS133013, maxLength 24. |
| Route object: none | 159.180.181.0/24 | No route object for it. A route object for 159.180.176.0/21 with origin AS133013 covers it (filters allowing more-specifics accept it). Add a route object with origin AS133013 in the RIR database for the space. |
| ROA: none | 159.180.182.0/24 | No ROA covers it. Add a ROA for AS133013, maxLength 24. |
| Route object: none | 159.180.182.0/24 | No route object for it. A route object for 159.180.176.0/21 with origin AS133013 covers it (filters allowing more-specifics accept it). Add a route object with origin AS133013 in the RIR database for the space. |
| ROA: none | 159.180.183.0/24 | No ROA covers it. Add a ROA for AS133013, maxLength 24. |
| Route object: none | 159.180.183.0/24 | No route object for it. A route object for 159.180.176.0/21 with origin AS133013 covers it (filters allowing more-specifics accept it). Add a route object with origin AS133013 in the RIR database for the space. |
| ROA: none | 159.180.176.0/21 | No ROA covers it. Add a ROA for AS133013, maxLength 21. |
| ROA: none | 159.180.176.0/24 | No ROA covers it. Add a ROA for AS133013, maxLength 24. |
| ROA: none | 159.180.178.0/24 | No ROA covers it. Add a ROA for AS133013, maxLength 24. |
Route objects not announced
Route objects with origin AS133013 whose prefix no peer sees AS133013 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 159.180.176.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.