bgpreport

Network · data from 2026-11-12

AS11941 PWLLP-AS001 - Pillsbury Madison & Sutro, Inc.

Registry name: PWLLP-AS001 - Pillsbury Madison & Sutro, Inc., US · not in PeeringDB

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

Announced routes

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

204.227.227.0/24 Valid Nonecovered by 204.227.224.0/19 672 100% 67
204.227.225.0/24 Valid Other IRR onlyRADB 672 100% 67
204.227.226.0/24 Valid Other IRR onlyRADB 672 100% 67
204.227.230.0/24 Valid Other IRR onlyRADB 672 100% 67
204.227.231.0/24 Valid Other IRR onlyRADB 672 100% 67
204.227.232.0/24 Valid Other IRR onlyRADB 672 100% 67
204.227.233.0/24 Valid Other IRR onlyRADB 672 100% 67
204.227.236.0/24 Valid Other IRR onlyRADB 672 100% 67
204.227.237.0/24 Valid Other IRR onlyRADB 672 100% 67
204.227.238.0/24 Valid Other IRR onlyRADB 672 100% 67
204.227.239.0/24 Valid Other IRR onlyRADB 672 100% 67
204.227.240.0/24 Valid Other IRR onlyRADB 672 100% 67
204.227.241.0/24 Valid Other IRR onlyRADB 672 100% 67
204.227.242.0/24 Valid Other IRR onlyRADB 672 100% 67
204.227.243.0/24 Valid Other IRR onlyRADB 672 100% 67
204.227.245.0/24 Valid Other IRR onlyRADB 670 100% 67
204.227.247.0/24 Valid Other IRR onlyALTDB, RADB 670 100% 67
204.227.254.0/24 Valid Other IRR onlyALTDB 670 100% 67
204.227.228.0/24 Valid Other IRR onlyALTDB, NTTCOM 666 99% 67
204.227.246.0/24 Valid Other IRR onlyALTDB, RADB 666 99% 67
204.227.251.0/24 Valid Other IRR onlyALTDB, RADB 666 99% 67
204.227.255.0/24 Valid Other IRR onlyALTDB 666 99% 67

AS-SET

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

  • Route object: none1
  • Route object: RIR21
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
Route object: none204.227.227.0/24No route object for it. A route object for 204.227.224.0/19 with origin AS11941 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11941 in the RIR database for the space.672 of 673
Route object: RIR204.227.225.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR204.227.226.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR204.227.230.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR204.227.231.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR204.227.232.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR204.227.233.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR204.227.236.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR204.227.237.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR204.227.238.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR204.227.239.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR204.227.240.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR204.227.241.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR204.227.242.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR204.227.243.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR204.227.245.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR204.227.247.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR204.227.254.0/24Route object only in ALTDB. Add it in the RIR database for the space.670 of 673
Route object: RIR204.227.228.0/24Route object only in ALTDB, NTTCOM. Add it in the RIR database for the space.666 of 673
Route object: RIR204.227.246.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR204.227.251.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR204.227.255.0/24Route object only in ALTDB. Add it in the RIR database for the space.666 of 673

Route objects not announced

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

204.227.224.0/19ARINValid
204.227.224.0/24RADBValid
204.227.229.0/24RADBValid
204.227.234.0/24RADBValid
204.227.235.0/24RADB, RIPE-NONAUTHValid
204.227.244.0/24RADBValid
204.227.248.0/24RADBValid
204.227.249.0/24RADBValid
204.227.250.0/24RADBValid
204.227.252.0/24RADBValid
204.227.253.0/24RADBValid
204.227.254.0/23NTTCOMValid

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.