An email outage will trigger HIPAA obligations in one form or another, just not in the way most people expect. As long as the outage doesn't result in the release of protected health information (PHI), there is no breach and no notification obligation. However, the Security Rule's expectations regarding ePHI availability and contingency planning are implicated, and healthcare staff will have to use alternate methods to send and receive their HIPAA compliant email, which could lead to a breach.

A Microsoft 365 outage on November 12, 2026 made the question practical. Many Outlook users could not send or receive email for hours. In a Paubox survey of 170 US healthcare IT and security leaders, 38% named Microsoft 365 as their primary email platform.

Separately, 96% of the 50 health systems surveyed reported one or more unplanned EHR downtimes over 3 years in one Elsevier study. While this referred to EHR downtime, analogous questions would arise with respect to a staff member's inability to access an email inbox containing PHI such as referral correspondence, test results, claims, etc.

 

What the Security Rule says about availability

Covered entities must maintain the confidentiality, integrity, and availability of all ePHI that the entity creates, receives, maintains, or transmits. According to HHS, availability means that the ePHI should be "accessible and usable on demand by an authorized person.”

A great deal of ePHI is stored and maintained in an email inbox by many covered entities. If there are referrals, record release requests, or other PHI stored in email, and it can't be accessed, that ePHI is not available. Depending on the duration of the outage, the significance to patient care and business operations will vary. At a Sydney hospital, a 17-minute failure of a results reporting system left clinicians unable to log on. They then took about five times longer to read potassium results. The researchers cautioned that "Even brief system downtimes may impact patient care."

 

Why an outage alone is rarely a breach

HIPAA’s Breach Notification Rule would not be required because of an email outage. No use or disclosure of PHI occurred that would "compromise the security or privacy" of PHI, as contemplated by the Breach Notification Rule. An email outage does not by itself trigger the Breach Notification Rule. Nothing has been used or disclosed in a way that would “compromise the security or privacy” of PHI. A power cut, an internet failure, or a technical fault at the email provider leaves messages unreachable, but no unauthorized person has acquired or viewed them. On those facts alone, the provider has nothing to notify.

The operational impact still carries risk. A JAMIA analysis of 80,381 patient safety event reports found 76 tied to EHR downtime. The researchers noted that “incidents were most frequently related to "Incidents commonly involved patient identification and communication of clinical information."

 

When the cause of the outage changes the answer

If the outage was caused by a threat actor, this can have different consequences for the provider. Where a ransomware attack impacts a covered entity's information system, it is a security incident. It will be a breach if ePHI was affected (i.e., encrypted) unless there is a determination of low likelihood of compromise (see HHS ransomware guidance).

A security incident is defined under the Security Rule to include "the attempted or successful unauthorized access, use, disclosure, modification, or destruction of information or interference with system operations in an information system." Failure of a provider's IT and email infrastructure will not fall within this definition unless a threat actor is involved or suspected. Note, the provider may not initially know this to be the case and should handle the situation as a suspected security incident until confirmed as an equipment or technical failure.

Attackers could also take advantage of the situation by sending staff convincing phishing emails that offer to reinstate access to their email accounts. In one JAMA Network Open study, healthcare organizations had a 14.2% click-through rate on phishing emails, and the researchers noted that "email phishing is a major attack vector against hospital employees."

 

How workarounds create the breach risk

The larger risk is what staff does next. Some will bypass the normal process, for example, by forwarding lab reports or referral letters from a personal email account forward to providers. Such PHI will be outside the control of the provider and not subject to the terms of the provider's BAA. HHS guidance on the use of cloud computing makes clear that where ePHI is hosted or processed in a cloud service without the execution of a BAA, the covered entity will be "in violation of the HIPAA Rules."

Staff may also fail to follow established protocols and processes around their email security even when systems remain up and running. In Paubox’s Healthcare email security maturity index 2026, 48% of respondents always require a portal login to read encrypted email, and 34–40% noted that staff sometimes or often circumvent this requirement. An email outage will simply heighten this risk, as staff will have to find alternative means to conduct their business. As one Studies in Health Technology and Informatics paper noted, "Clinicians focus on patient care, not cybersecurity"

Related: Is an employee's auto-forward rule to personal Gmail a breach?

 

Name the fallback channels before an outage

Under the Security Rule's Contingency Plan implementation specifications, it requires a data backup plan, a disaster recovery plan, and an emergency mode operation plan. This will include alternate channels to send and receive email (and what PHI may be sent or received) when staff's normal inbox is down, as well as any authorizations for exceptions to their normal process. In that same survey, 70% of systems had an unplanned outage longer than eight hours and the researchers noted, "Most institutions had only partially implemented comprehensive contingency plans."

 

Keep patient communication within the Privacy Rule

Providers will still want to be able to provide PHI to patients (e.g., lab results) or send PHI for treatment, payment, and operations, like referral correspondence with another provider. Provided that appropriate safeguards are met and observed for the relevant channels, these are permitted disclosures under the Privacy Rule.

Where a patient requests to receive communications via an alternative method to their "primary" communication channel, the provider should make this option available to the patient for example "mail or telephone." The Privacy Rule does not prohibit unencrypted email, and the Security Rule treats encryption in transit as an addressable specification. That flexibility covers messages sent through the provider’s own HIPAA compliant email system, not a personal account or a vendor with no BAA. Inevitably, there will be delays in the provision of lab results and other PHI to patients and professionals. In one study of EHR downtime across two hospitals in the Mid-Atlantic region, lab results were delayed by 62% on average, commonly as a result of "improper procedural execution, and incomplete or incorrect documentation." A short script for phoning results, with somewhere to log each call, addresses both causes.

 

Document the outage and check for workarounds

Providers should maintain documentation of the email outage and how PHI was sent or received via alternate means (and from and to where). Covered entities are required to "document security incidents and their outcomes" under the Security Rule, and this will be useful to inform any changes to contingency plans. Investigate any PHI that left a staff mailbox for a personal or third-party account. Each instance needs a breach risk assessment.

In that analysis, 46% of downtime reports showed procedures were either not followed or not available. The authors pointed to “critical aspects of the downtime procedures." Similarly, more than half of respondents (58%) experienced an email breach in the past 24 months (23% experienced multiple breaches), according to the Paubox Healthcare Email Security Maturity Index 2026.

 

FAQs

Does HIPAA require a backup email provider?

No, the Security Rule requires a contingency plan but does not dictate specific security measures, so a second provider is one option to weigh in the risk analysis.

 

Can staff fax a referral while email is down?

Yes, providers may share PHI for treatment by fax when they use reasonable safeguards, such as confirming an unfamiliar fax number with the recipient before sending.

 

Should an outage change our risk analysis?

Yes, the Security Rule expects covered entities to reassess risks to ePHI regularly, and an outage is new evidence about the availability of information held in email.