HTML & MJML

Service Outage Apology Email Template

Rebuild trust fast after downtime with this service outage apology email template built for SaaS and technology teams. A status-page-inspired design pairs an incident-resolved banner with a precise UTC timeline, a what-changes-now summary card, and a post-mortem CTA — the exact transparency engineers and customers expect. Send this email template after outages, degraded performance, failed deploys, or security maintenance windows. Product, support, and DevOps teams get a ready-made incident communication that turns a bad day into proof your company owns its mistakes.

Edit In EmailBuilder.ai

About the Service Outage Apology Email Template

Built for SaaS companies, DevOps teams, and technical support leads, this service outage apology email transforms a painful incident into a trust-building moment. The status-page-inspired layout delivers exactly what engineers and customers expect: a resolved banner, a UTC-stamped timeline, and a clear post-mortem path. When downtime happens, this template ensures your communication is as reliable as the uptime you are working to restore.

When to use this template

Send within 30 to 60 minutes of incident resolution, once your team has confirmed stable service. Triggers include resolved outages, cleared degraded performance alerts, completed emergency security maintenance windows, or failed deploys that have been rolled back. Earlier drafts can be staged during the incident so sending is instant upon resolution.

A B2B SaaS platform apologizing after a two-hour API outage affecting enterprise clients
A cloud hosting provider communicating resolution of a regional data center failure
A fintech startup notifying users after a failed payment processing deploy causes errors
A project management tool following up on degraded performance during peak business hours
A DevOps team sending a post-incident summary after an emergency security maintenance window
A customer success team closing the loop after a database timeout impacted dashboard access

Subject line ideas

We're back — here's exactly what happened
Service restored: incident timeline and next steps
We let you down on [date] — full details inside
Resolved: outage report + what we're fixing now

Best practices for apology / oops emails

Lead with the resolved status banner so readers know service is restored before reading anything else.
Use precise UTC timestamps in the incident timeline — vague language like 'earlier today' erodes technical credibility fast.
Separate the what-happened summary from the what-changes-now card so engineers and non-technical stakeholders both find their answer quickly.
Include a direct CTA to the public post-mortem or status page rather than promising a follow-up that may never arrive.
Avoid softening language like 'minor disruption' if customers experienced real impact — match the severity of your apology to the severity of the incident.

Template anatomy

How the Service Outage Apology Email Template template is laid out, top to bottom:

section (1 column) containing text block.
section (1 column) containing text block.
section (1 column) containing text block.
section (2 columns) containing text block.
section (1 column) containing text block.
section (1 column) containing button, text block.
section (1 column) containing social row, social link, text block.

Components used

Built from the following MJML elements:

17 text blocks3 social links1 button1 social row

Color palette

Colors used across the Service Outage Apology Email Template template:

#f1f5f9

#0f172a

#ffffff

#38bdf8

#94a3b8

#2563eb

#475569

#eff6ff

#64748b

Typography

Font stacks declared in the template:

Helvetica, Arial, sans-serif

MJML source code

A preview of the MJML markup for the Service Outage Apology Email Template template. Open it free in EmailBuilder.ai to get the complete source and start customizing.

<mjml>
  <mj-head>
    <mj-title>Service Outage Apology Email Template</mj-title>
    <mj-attributes>
      <mj-all font-family="Helvetica, Arial, sans-serif"></mj-all>
      <mj-text font-size="14px" line-height="24px"></mj-text>
    </mj-attributes>
    <mj-preview>Full incident report: what broke, how we fixed it, and what changes next.</mj-preview>
  </mj-head>
  <mj-body background-color="#F1F5F9" width="600px">
    <mj-section background-color="#0F172A" padding="28px 36px 24px 36px">
      <mj-column>
        <mj-text color="#FFFFFF" font-size="18px" letter-spacing="3px" align="center" padding="0px"><strong>ACME CLOUD</strong></mj-text>
      </mj-column>
    </mj-section>
    <mj-section background-color="#0F172A" padding="20px 36px 44px 36px">
      <mj-column>
        <mj-text color="#38BDF8" font-size="14px" letter-spacing="2px" align="center" padding="0px 0px 14px 0px"><strong>INCIDENT RESOLVED</strong></mj-text>
        <mj-text color="#FFFFFF" font-size="34px" line-height="42px" align="center" padding="0px"><strong>About yesterday's outage — we're sorry.</strong></mj-text>
        <mj-text color="#94A3B8" font-size="15px" line-height="25px" align="center" padding="18px 8px 0px 0px">On Tuesday between 14:02 and 15:47 UTC, the dashboard and API were unavailable. That's 1 hour and 45 minutes of your time we cost you, and we want to explain exactly what happened.</mj-text>
      </mj-column>
    </mj-section>
    <mj-section background-color="#FFFFFF" padding="32px 36px 8px 36px">
      <mj-column>
        <mj-text color="#0F172A" font-size="20px" align="left" padding="0px 0px 18px 0px"><strong>The timeline</strong></mj-text>
      </mj-column>
    </mj-section>
    <mj-section background-color="#FFFFFF" padding="0px 36px 8px 36px">
      <mj-column width="28%" padding="0px">
        <mj-text color="#2563EB" font-size="14px" padding="6px 0px"><strong>14:02 UTC</strong></mj-text>
        <mj-text color="#2563EB" font-size="14px" padding="6px 0px"><strong>14:11 UTC</strong></mj-text>
        <mj-text color="#2563EB" font-size="14px" padding="6px 0px"><strong>15:20 UTC</strong></mj-text>
        <mj-text color="#2563EB" font-size="14px" padding="6px 0px"><strong>15:47 UTC</strong></mj-text>

Want the full MJML?Open Service Outage Apology Email Template free in the editor to copy the complete, production-ready source — and customize it with drag-and-drop.Get the full MJML — it's free