Network · data from 2026-11-12
AS54282 JJINTEROP - Johnson & Johnson
Registry name: JJINTEROP - Johnson & Johnson, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS54282, 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.
| 199.65.16.0/24 | Valid | Nonecovered by 199.65.16.0/20 | 673 100% |
| 199.65.17.0/24 | Valid | Nonecovered by 199.65.16.0/20 | 668 99% |
| 193.135.46.0/23 | Valid | Other IRR onlyRADB | 673 100% |
AS-SET
AS54282 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 6 are in fix.csv.
- Route object: none2
- Route object: RIR1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 199.65.16.0/24 | No route object for it. A route object for 199.65.16.0/20 with origin AS54282 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54282 in the RIR database for the space. |
| Route object: none | 199.65.17.0/24 | No route object for it. A route object for 199.65.16.0/20 with origin AS54282 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54282 in the RIR database for the space. |
| Route object: RIR | 193.135.46.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS54282 whose prefix no peer sees AS54282 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 199.65.16.0/20 | RADB | Valid |
| 2620:8:8200::/48 | RADB | No ROA |
| 2620:147::/40 | ARIN | Valid |
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.