bgpreport

Network · data from 2026-11-12

AS26478 NOVARTIS-PHARMA - Novartis Pharmaceuticals

Registry name: NOVARTIS-PHARMA - Novartis Pharmaceuticals, US · not in PeeringDB

7IPv4 routes 57.1% RPKI valid · 71.4% with a route object
0IPv6 routes
1RPKI invalid 1 origin · 0 maxLength
2No ROA 2 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS26478, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS26478, 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.
200.57.1.48/28 Invalid: origin None 1 0%low visibility 1
205.181.102.0/24 No ROA None 672 100% 67
162.86.66.0/24 No ROA RIR databaseRIPE 667 99% 67
86.117.47.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
160.62.14.0/24 Valid RIR databaseRIPE 672 100% 67
160.62.15.0/24 Valid RIR databaseRIPE 672 100% 67
160.62.140.0/23 Valid RIR databaseRADB, RIPE 672 100% 67

AS-SET

AS26478 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 7 are in fix.csv.

  • ROA: origin1
  • ROA: none2
  • Route object: none2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin200.57.1.48/28ROAs covering it name AS18734, not AS26478. If AS26478 should announce it, add a ROA for AS26478.1 of 673
Route object: none200.57.1.48/28No route object for it. Add a route object with origin AS26478 in the RIR database for the space.1 of 673
ROA: none205.181.102.0/24No ROA covers it. Add a ROA for AS26478, maxLength 24.672 of 673
Route object: none205.181.102.0/24No route object for it. Add a route object with origin AS26478 in the RIR database for the space.672 of 673
ROA: none162.86.66.0/24No ROA covers it. Add a ROA for AS26478, maxLength 24.667 of 673

Route objects not announced

Route objects with origin AS26478 whose prefix no peer sees AS26478 announce. Many are kept on purpose (backup routes, space announced only in some places).

160.62.22.0/24RIPEValid
161.61.160.0/24RADBNo 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.