British Airways Plc

2018 年的事件展示了支付页面如何保持可用且令人信服，而结账流程中的代码却将客户数据复制到其他地方。这种无声的差异使远程访问、生产代码完整性、出站流量监控和精确通知成为一条责任链的一部分。

英国航空 2017 年 5 月的中断始于其主数据中心的电力故障，并演变为一场为期三天的考验：航空公司能否恢复值机、航班放行、行李、客户沟通和改签背后的数字运营架构。公开记录确认了大致事件及其后果，但未确认完整的电气顺序及每个人员和供应商的身份与行为。本分析首先重建 5 月 27 日至 29 日的时间线，保持该证据边界，然后将基础设施原因与航空公司在通知、关怀、改签和赔偿方面的独立责任区分开来。

The 2018 incident showed how a payment page could remain available and convincing while code inside the checkout journey copied customer data elsewhere. That silent divergence made remote access, production-code integrity, outbound-flow monitoring and precise notification parts of one accountability chain.

British Airways' May 2017 disruption began with a power failure at its primary data centre and became a three-day test of whether an airline could recover the digital operating fabric behind check-in, flight dispatch, baggage, customer communication and rebooking. The public record confirms the broad event and its consequences, but not the complete electrical sequence or the identity and conduct of every person and supplier involved. This analysis reconstructs 27-29 May first, preserves that evidence boundary, then separates infrastructure causation from the airline's independent duties to inform, care for, reroute and compensate passengers.