Network · data from 2026-11-12
AS26534 ABBVIE-2 - AbbVie, Inc.
Registry name: ABBVIE-2 - AbbVie, Inc., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS26534, 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.
| 69.49.0.0/24 | No ROA | Nonecovered by 69.49.0.0/19 | 673 100% |
| 69.49.4.0/24 | No ROA | Nonecovered by 69.49.0.0/19 | 673 100% |
| 69.49.8.0/22 | No ROA | Nonecovered by 69.49.0.0/19 | 673 100% |
| 69.49.0.0/19 | No ROA | Other IRR onlyRADB | 673 100% |
| 159.180.141.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 159.180.148.0/23 | No ROA | Other IRR onlyRADB | 673 100% |
| 159.180.150.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
AS-SET
AS26534 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: none7
- Route object: none3
- Route object: RIR4
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 69.49.0.0/24 | No ROA covers it. Add a ROA for AS26534, maxLength 24. |
| Route object: none | 69.49.0.0/24 | No route object for it. A route object for 69.49.0.0/19 with origin AS26534 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26534 in the RIR database for the space. |
| ROA: none | 69.49.4.0/24 | No ROA covers it. Add a ROA for AS26534, maxLength 24. |
| Route object: none | 69.49.4.0/24 | No route object for it. A route object for 69.49.0.0/19 with origin AS26534 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26534 in the RIR database for the space. |
| ROA: none | 69.49.8.0/22 | No ROA covers it. Add a ROA for AS26534, maxLength 22. |
| Route object: none | 69.49.8.0/22 | No route object for it. A route object for 69.49.0.0/19 with origin AS26534 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26534 in the RIR database for the space. |
| ROA: none | 69.49.0.0/19 | No ROA covers it. Add a ROA for AS26534, maxLength 19. |
| Route object: RIR | 69.49.0.0/19 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 159.180.141.0/24 | No ROA covers it. Add a ROA for AS26534, maxLength 24. |
| Route object: RIR | 159.180.141.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 159.180.148.0/23 | No ROA covers it. Add a ROA for AS26534, maxLength 23. |
| Route object: RIR | 159.180.148.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 159.180.150.0/24 | No ROA covers it. Add a ROA for AS26534, maxLength 24. |
| Route object: RIR | 159.180.150.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS26534 whose prefix no peer sees AS26534 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 159.180.128.0/22 | RADB | No ROA |
| 209.143.176.0/23 | RADB | 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.