bgpreport

Network · data from 2026-11-12

AS13778 JOHNSON-AND-JOHNSON - Johnson & Johnson

Registry name: JOHNSON-AND-JOHNSON - Johnson & Johnson, US · not in PeeringDB

18IPv4 routes 0.0% RPKI valid · 50.0% with a route object
10IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
18No ROA 9 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
40Route objects not announced registered with origin AS13778, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS13778, 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.

148.177.0.0/18 No ROA Other origin only 672 100% 67
148.177.97.0/24 No ROA None 672 100% 67
148.177.98.0/24 No ROA None 672 100% 67
199.65.0.0/23 No ROA Other origin only 672 100% 67
199.65.124.0/22 No ROA Other origin only 672 100% 67
199.65.208.0/21 No ROA Other origin only 672 100% 67
199.65.224.0/24 No ROA None 672 100% 67
148.177.192.0/23 No ROA Nonecovered by 148.177.192.0/21 2 0%low visibility 2
148.177.193.0/24 No ROA Other origin onlycovered by 148.177.192.0/21 2 0%low visibility 2
148.177.128.0/21 No ROA Other IRR onlyRADB 672 100% 67
148.177.144.0/22 No ROA Other IRR onlyRADB 672 100% 67
148.177.169.0/24 No ROA Other IRR onlyRADB 672 100% 67
148.177.242.0/24 No ROA Other IRR onlyRADB 672 100% 66
199.65.128.0/23 No ROA Other IRR onlyRADB 672 100% 67
199.65.130.0/23 No ROA Other IRR onlyRADB 672 100% 67
199.65.200.0/21 No ROA Other IRR onlyRADB 672 100% 67
199.65.64.0/24 No ROA Other IRR onlyRADB 671 100% 67
148.177.184.0/22 No ROA Other IRR onlyNTTCOM 668 99% 67
2602:281::/32 Valid RIR databaseARIN, RADB 636 100% 67
2602:282::/32 Valid RIR databaseARIN, RADB 636 100% 67
2602:284::/32 Valid RIR databaseARIN, RADB 636 100% 69
2620:147:110::/44 Valid RIR databaseARIN 636 100% 67
2620:147:120::/44 Valid RIR databaseARIN 636 100% 67
2620:147:140::/44 Valid RIR databaseARIN 636 100% 69
2620:147::/36 Valid RIR databaseARIN 635 100% 69
2602:280::/28 Valid RIR databaseARIN 634 100% 69
2602:283::/32 Valid RIR databaseARIN, RADB 634 100% 67
2620:147:130::/44 Valid RIR databaseARIN 633 100% 67

AS-SET

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

  • ROA: none18
  • Route object: none9
  • Route object: RIR9
  • Route object: not announced40
ChangePrefix or setDetailFull-table peers
ROA: none148.177.0.0/18No ROA covers it. Add a ROA for AS13778, maxLength 18.672 of 673
Route object: none148.177.0.0/18Route objects for it name AS198949. Add a route object with origin AS13778 in the RIR database for the space.672 of 673
ROA: none148.177.97.0/24No ROA covers it. Add a ROA for AS13778, maxLength 24.672 of 673
Route object: none148.177.97.0/24No route object for it. Add a route object with origin AS13778 in the RIR database for the space.672 of 673
ROA: none148.177.98.0/24No ROA covers it. Add a ROA for AS13778, maxLength 24.672 of 673
Route object: none148.177.98.0/24No route object for it. Add a route object with origin AS13778 in the RIR database for the space.672 of 673
ROA: none199.65.0.0/23No ROA covers it. Add a ROA for AS13778, maxLength 23.672 of 673
Route object: none199.65.0.0/23Route objects for it name AS198949. Add a route object with origin AS13778 in the RIR database for the space.672 of 673
ROA: none199.65.124.0/22No ROA covers it. Add a ROA for AS13778, maxLength 22.672 of 673
Route object: none199.65.124.0/22Route objects for it name AS198949. Add a route object with origin AS13778 in the RIR database for the space.672 of 673
ROA: none199.65.208.0/21No ROA covers it. Add a ROA for AS13778, maxLength 21.672 of 673
Route object: none199.65.208.0/21Route objects for it name AS198949. Add a route object with origin AS13778 in the RIR database for the space.672 of 673
ROA: none199.65.224.0/24No ROA covers it. Add a ROA for AS13778, maxLength 24.672 of 673
Route object: none199.65.224.0/24No route object for it. Add a route object with origin AS13778 in the RIR database for the space.672 of 673
ROA: none148.177.192.0/23No ROA covers it. Add a ROA for AS13778, maxLength 23.2 of 673
Route object: none148.177.192.0/23No route object for it. A route object for 148.177.192.0/21 with origin AS13778 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13778 in the RIR database for the space.2 of 673
ROA: none148.177.193.0/24No ROA covers it. Add a ROA for AS13778, maxLength 24.2 of 673
Route object: none148.177.193.0/24Route objects for it name AS23871. A route object for 148.177.192.0/21 with origin AS13778 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13778 in the RIR database for the space.2 of 673
ROA: none148.177.128.0/21No ROA covers it. Add a ROA for AS13778, maxLength 21.672 of 673
Route object: RIR148.177.128.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none148.177.144.0/22No ROA covers it. Add a ROA for AS13778, maxLength 22.672 of 673
Route object: RIR148.177.144.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none148.177.169.0/24No ROA covers it. Add a ROA for AS13778, maxLength 24.672 of 673
Route object: RIR148.177.169.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none148.177.242.0/24No ROA covers it. Add a ROA for AS13778, maxLength 24.672 of 673
Route object: RIR148.177.242.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none199.65.128.0/23No ROA covers it. Add a ROA for AS13778, maxLength 23.672 of 673
Route object: RIR199.65.128.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none199.65.130.0/23No ROA covers it. Add a ROA for AS13778, maxLength 23.672 of 673
Route object: RIR199.65.130.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none199.65.200.0/21No ROA covers it. Add a ROA for AS13778, maxLength 21.672 of 673
Route object: RIR199.65.200.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none199.65.64.0/24No ROA covers it. Add a ROA for AS13778, maxLength 24.671 of 673
Route object: RIR199.65.64.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none148.177.184.0/22No ROA covers it. Add a ROA for AS13778, maxLength 22.668 of 673
Route object: RIR148.177.184.0/22Route object only in NTTCOM. Add it in the RIR database for the space.668 of 673

Route objects not announced

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

122.248.184.0/23RADBNo ROA
148.177.0.0/21RADBNo ROA
148.177.109.0/24RADBNo ROA
148.177.168.0/21RADBNo ROA
148.177.190.0/24NTTCOMNo ROA
148.177.192.0/21RADBNo ROA
148.177.200.0/21RADBNo ROA
148.177.206.0/24NTTCOMNo ROA
148.177.216.0/22RADB, REACHNo ROA
148.177.216.0/24RADB, REACHNo ROA
148.177.217.0/24RADB, REACHNo ROA
148.177.218.0/24REACHNo ROA
148.177.219.0/24RADB, REACHNo ROA
148.177.220.0/22REACHNo ROA
148.177.220.0/24REACHNo ROA
148.177.239.0/24NTTCOM, RADBNo ROA
148.177.241.0/24RADBNo ROA
199.65.192.0/21APNIC, RADBNo ROA
199.65.192.0/24NTTCOMNo ROA
199.65.193.0/24NTTCOMNo ROA
199.65.194.0/24NTTCOMNo ROA
199.65.195.0/24NTTCOMNo ROA
199.65.196.0/24NTTCOMNo ROA
199.65.197.0/24NTTCOMNo ROA
199.65.198.0/24APNIC, NTTCOMNo ROA
199.65.199.0/24NTTCOMNo ROA
199.65.200.0/22RADBNo ROA
199.65.200.0/23RADBNo ROA
199.65.200.0/24RADBNo ROA
199.65.201.0/24RADBNo ROA
199.65.202.0/23RADBNo ROA
199.65.202.0/24RADBNo ROA
199.65.203.0/24RADBNo ROA
199.65.204.0/22RADBNo ROA
199.65.204.0/23RADBNo ROA
199.65.204.0/24RADBNo ROA
199.65.205.0/24RADBNo ROA
199.65.206.0/23RADBNo ROA
199.65.206.0/24RADBNo ROA
199.65.207.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.