Narrative:

At cruise; we had ecams for the captain's window heat and a pack regulator fault. I completed the ecams. About 5 minutes later; the captain's nd; pfd and the upper ECAM switched back and forth between being blank and having a diagonal line; finally going totally blank. The 3 screens came back to life about five minutes later and worked well for the remainder of the flight. Simultaneously; we had a multitude of various ecams. The aircraft also started to shake considerably. I assigned the first officer (first officer) to fly and I [notified ATC]; initially asking for a diversion to [a nearby airport]. After realizing that [another nearby airport] was behind us and quite a bit closer; I changed my diversion choice. I worked through the ecams and required checklists. The first officer and I worked very well together and I kept dispatch; the flight attendants and the passengers informed as the workload decreased. One important note - my ipad froze while I was trying to access jepppro to brief the approach. I had to shut it down and restart it. Prior to this; I've never had a problem with my ipad. The airframe vibration intensified on the approach. The approach and landing were normal; but we didn't have reversers. This was a surprise because it wasn't displayed as an ECAM and didn't show on the status page. Later the flight attendants told us that there was a vibration in the rear of the aircraft and the tail was swaying side to side. This swaying was indicative of a dual yaw damper failure. This was never made aware to us because it also wasn't an ECAM and didn't appear on the status page.

Related reports:

Google
 

Original NASA ASRS Text

Title: A320 flight crew reported diverting to an alternate airport after experiencing multiple system failures in cruise flight.

Narrative: At cruise; we had ECAMs for the Captain's window heat and a pack regulator fault. I completed the ECAMs. About 5 minutes later; the Captain's ND; PFD and the upper ECAM switched back and forth between being blank and having a diagonal line; finally going totally blank. The 3 screens came back to life about five minutes later and worked well for the remainder of the flight. Simultaneously; we had a multitude of various ECAMs. The aircraft also started to shake considerably. I assigned the FO (First Officer) to fly and I [notified ATC]; initially asking for a diversion to [a nearby airport]. After realizing that [another nearby airport] was behind us and quite a bit closer; I changed my diversion choice. I worked through the ECAMs and required checklists. The FO and I worked very well together and I kept Dispatch; the flight attendants and the passengers informed as the workload decreased. One important note - my iPad froze while I was trying to access JeppPro to brief the approach. I had to shut it down and restart it. Prior to this; I've never had a problem with my iPad. The airframe vibration intensified on the approach. The approach and landing were normal; but we didn't have reversers. This was a surprise because it wasn't displayed as an ECAM and didn't show on the STATUS page. Later the flight attendants told us that there was a vibration in the rear of the aircraft and the tail was swaying side to side. This swaying was indicative of a dual yaw damper failure. This was never made aware to us because it also wasn't an ECAM and didn't appear on the STATUS page.

Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.