bgpreport

Network · data from 2026-11-12

AS11971 PFIZERNET-GROTON - Pfizer Inc.

Registry name: PFIZERNET-GROTON - Pfizer Inc., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS11971, 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.168.192.0/23 No ROA Nonecovered by 148.168.192.0/22 672 100% 67
148.168.35.0/24 No ROA Nonecovered by 148.168.32.0/19 656 97% 67
146.240.1.0/24 No ROA Other IRR onlyRADB 672 100% 67
148.168.32.0/19 No ROA Other IRR onlyRADB 672 100% 67
148.168.192.0/22 No ROA Other IRR onlyRADB 672 100% 67
148.168.224.0/22 No ROA Other IRR onlyRADB 672 100% 67
148.168.0.0/16 No ROA Other IRR onlyRADB 195 29% 55

AS-SET

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

  • ROA: none7
  • Route object: none2
  • Route object: RIR5
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none148.168.192.0/23No ROA covers it. Add a ROA for AS11971, maxLength 23.672 of 673
Route object: none148.168.192.0/23No route object for it. A route object for 148.168.192.0/22 with origin AS11971 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11971 in the RIR database for the space.672 of 673
ROA: none148.168.35.0/24No ROA covers it. Add a ROA for AS11971, maxLength 24.656 of 673
Route object: none148.168.35.0/24No route object for it. A route object for 148.168.32.0/19 with origin AS11971 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11971 in the RIR database for the space.656 of 673
ROA: none146.240.1.0/24No ROA covers it. Add a ROA for AS11971, maxLength 24.672 of 673
Route object: RIR146.240.1.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none148.168.32.0/19No ROA covers it. Add a ROA for AS11971, maxLength 19.672 of 673
Route object: RIR148.168.32.0/19Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none148.168.192.0/22No ROA covers it. Add a ROA for AS11971, maxLength 22.672 of 673
Route object: RIR148.168.192.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none148.168.224.0/22No ROA covers it. Add a ROA for AS11971, maxLength 22.672 of 673
Route object: RIR148.168.224.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none148.168.0.0/16No ROA covers it. Add a ROA for AS11971, maxLength 16.195 of 673
Route object: RIR148.168.0.0/16Route object only in RADB. Add it in the RIR database for the space.195 of 673

Route objects not announced

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

146.240.0.0/16RADBNo ROA
146.240.2.0/24RADBNo ROA
148.168.47.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.