bgpreport

Network · data from 2026-11-12

AS11047 HHCC-ASN1 - Hartford Hospital

Registry name: HHCC-ASN1 - Hartford Hospital, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS11047, 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.231.22.0/24 No ROA Nonecovered by 199.231.16.0/20 670 100% 67
199.231.28.0/24 No ROA Other origin onlycovered by 199.231.16.0/20 670 100% 67
199.231.30.0/24 No ROA Other origin onlycovered by 199.231.16.0/20 670 100% 67
199.231.25.0/24 No ROA Nonecovered by 199.231.16.0/20 669 99% 67
199.231.31.0/24 No ROA Other IRR onlyRADB 670 100% 67
199.231.16.0/24 No ROA Other IRR onlyRADB 666 99% 67
199.231.17.0/24 No ROA Other IRR onlyRADB 666 99% 67
199.231.20.0/24 No ROA Other IRR onlyRADB 666 99% 67
199.231.21.0/24 No ROA Other IRR onlyRADB 666 99% 67
199.231.26.0/24 No ROA Other IRR onlyRADB 666 99% 67
199.231.27.0/24 No ROA Other IRR onlyRADB 666 99% 67
199.231.29.0/24 No ROA Other IRR onlyRADB 666 99% 67

AS-SET

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

  • ROA: none12
  • Route object: none4
  • Route object: RIR8
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none199.231.22.0/24No ROA covers it. Add a ROA for AS11047, maxLength 24.670 of 673
Route object: none199.231.22.0/24No route object for it. A route object for 199.231.16.0/20 with origin AS11047 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11047 in the RIR database for the space.670 of 673
ROA: none199.231.28.0/24No ROA covers it. Add a ROA for AS11047, maxLength 24.670 of 673
Route object: none199.231.28.0/24Route objects for it name AS46887. A route object for 199.231.16.0/20 with origin AS11047 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11047 in the RIR database for the space.670 of 673
ROA: none199.231.30.0/24No ROA covers it. Add a ROA for AS11047, maxLength 24.670 of 673
Route object: none199.231.30.0/24Route objects for it name AS46887. A route object for 199.231.16.0/20 with origin AS11047 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11047 in the RIR database for the space.670 of 673
ROA: none199.231.25.0/24No ROA covers it. Add a ROA for AS11047, maxLength 24.669 of 673
Route object: none199.231.25.0/24No route object for it. A route object for 199.231.16.0/20 with origin AS11047 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11047 in the RIR database for the space.669 of 673
ROA: none199.231.31.0/24No ROA covers it. Add a ROA for AS11047, maxLength 24.670 of 673
Route object: RIR199.231.31.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none199.231.16.0/24No ROA covers it. Add a ROA for AS11047, maxLength 24.666 of 673
Route object: RIR199.231.16.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
ROA: none199.231.17.0/24No ROA covers it. Add a ROA for AS11047, maxLength 24.666 of 673
Route object: RIR199.231.17.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
ROA: none199.231.20.0/24No ROA covers it. Add a ROA for AS11047, maxLength 24.666 of 673
Route object: RIR199.231.20.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
ROA: none199.231.21.0/24No ROA covers it. Add a ROA for AS11047, maxLength 24.666 of 673
Route object: RIR199.231.21.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
ROA: none199.231.26.0/24No ROA covers it. Add a ROA for AS11047, maxLength 24.666 of 673
Route object: RIR199.231.26.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
ROA: none199.231.27.0/24No ROA covers it. Add a ROA for AS11047, maxLength 24.666 of 673
Route object: RIR199.231.27.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
ROA: none199.231.29.0/24No ROA covers it. Add a ROA for AS11047, maxLength 24.666 of 673
Route object: RIR199.231.29.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673

Route objects not announced

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

12.200.43.0/24RADBNo ROA
131.239.51.32/27RADBNo ROA
199.231.16.0/20RADBNo 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.