# Region failover email template

> Explore this region failover email template for technology and software. Preview its status, three key details, and next action.

Source: https://design.moosewave.com/templates/region-failover-email-template/

---

Transactional Alerts & status

# Region failover email template

Traffic moved between regions with the user-visible effect stated.
Illustrative example. Replace the fictional sender, dates, amounts, locations, and account details before use.
**Best for**
: Traffic moved between regions with the user-visible effect stated
**Structure**
: State or event context · Plain-language explanation · Three labelled facts
**Style**
: dispatch · industrial
**Industry fit**
: Technology & software
Responsive design preview

## See the message before you make it yours.

Compare the desktop and mobile compositions, or unfold the full design. The complete starting copy remains readable below.
Want to change the copy and style?

## Try one of the editable browser templates.

This page is a read-only reference. The five hands-on studios let you edit a local preview, compare desktop and mobile, and review every change before continuing.
Message anatomy

## A useful starting point, with the important parts named.

The failover worked as designed and you probably did not notice. The only visible effect is slightly higher latency until we move back.

### What you can change

- Brand name
- Subject line
- Preheader
- Eyebrow
- Headline
- Supporting copy
- Primary action label
- Primary action URL

### What to keep clear

- State or event context
- Plain-language explanation
- Three labelled facts
- Primary and secondary action
- Support or privacy footer
Complete starting copy

## Read it as text, not only as a picture.

**From**
: Lewknor Alerts
**Subject**
: We moved you to another region at 04:12
**Preheader**
: Slightly slower. Nothing lost. Nothing to do.
Failover

### Running from a different region, about 40 ms slower

The failover worked as designed and you probably did not notice. The only visible effect is slightly higher latency until we move back.

#### Failed over

04:12

#### Added latency

About 40 ms

#### Moving back

Once the primary is stable
Moosewave MCP

## Give an agent the structure, the job, and a stopping point.

The brief asks for a new draft and stops before send.

**Read the complete brief**
Connected work

## Take the design beyond the canvas.

Keep exploring

## Related transactional templates

[001 Transactional Open preview ↗ Alerts & status Service degraded A partial outage reported while it is still happening Technology & software](/templates/service-degraded-email-template/)
[002 Transactional Open preview ↗ Alerts & status Update ready Game update available with save-file and accessibility notes Technology & software · Health & accessibility](/templates/update-ready-email-template/)
[003 Transactional Open preview ↗ Alerts & status Anomaly detected Unusual activity flagged with the reasoning shown Technology & software](/templates/anomaly-detected-email-template/)
[004 Transactional Open preview ↗ Alerts & status Backup failed A failed backup reported the same morning with the real exposure Technology & software](/templates/backup-failed-email-template/)