# Event DNS outage: editable attendee message kit

Replace every [field] with verified details; remove any line you cannot support. Have the incident lead approve and timestamp each public update. Never post attendee personal data, account credentials or an unverified purchase link. This is a communication kit, not a DNS repair plan.

## Before an incident

- **Independent status URL:** [full URL on an unaffected domain]
- **Independent contact path:** [phone/social/support address tested without the event domain]
- **Publisher and backup publisher:** [names and access location]
- **Technical verifier / incident lead:** [names]
- **Primary attendee languages and approved translators:** [languages / owners]
- **Where this status URL is pre-shared:** [confirmation, ticket, social profile, printed materials]
- **Fallback if event-domain email fails:** [tested channel]

## Impact card — complete before publishing

| Journey | Symptom and first observed time with zone | Evidence / verifier | Works now? | Approved attendee action |
| --- | --- | --- | --- | --- |
| Public event page | [ ] | [ ] | [yes/no/unknown] | [ ] |
| Registration form | [ ] | [ ] | [yes/no/unknown] | [ ] |
| Ticket link and checkout | [ ] | [ ] | [yes/no/unknown] | [ ] |
| Confirmation and support email | [ ] | [ ] | [yes/no/unknown] | [ ] |

## 1. Investigating — first public notice

**Title:** [Event name]: difficulty accessing [confirmed service]

Some attendees cannot [specific action]. We confirmed this at [date and time, time zone]. [Other journey] is [working / not yet verified]. We are investigating and will publish the next update by [date and time, time zone] at [independent status URL]. [Verified workaround and official link, if any.] We do not yet have a confirmed recovery time.

**Approved by / published at / channels:** [ ]

## 2. Progress update — even if there is no change

As of [date and time, time zone], [specific service] is [current verified state]. Since our last update, [what changed / no confirmed change]. [Verified attendee action or state that no safe workaround exists.] We are checking [named journeys]. Next update by [date and time, time zone] at [independent status URL]. [Recovery estimate only if verified and approved.]

**Approved by / published at / channels:** [ ]

## 3. Recovery update — after journey checks

As of [date and time, time zone], we have verified that [event page], [registration], [official ticket/checkout path], and [affected email path] [work / list exceptions]. We checked [networks or test methods] at [time]. If you still cannot [action], contact [independent contact]. [Previously shared workaround] is now [retired / still needed for named users]. We will update this notice if conditions change.

**Approved by / published at / channels:** [ ]

## Publication log and closeout

| Time and zone | Stage | Public channel and URL | Claim/evidence owner | Approver | Next-update commitment |
| --- | --- | --- | --- | --- | --- |
| [ ] | Investigating | [ ] | [ ] | [ ] | [ ] |
| [ ] | Progress | [ ] | [ ] | [ ] | [ ] |
| [ ] | Recovery | [ ] | [ ] | [ ] | [ ] |

After stability is confirmed, remove stale workarounds, preserve the message timeline, and review whether the independent status path and contact details actually worked.

Sources: [Atlassian Statuspage incident template library](https://support.atlassian.com/statuspage/docs/incident-template-library/) and [Atlassian incident communication templates](https://www.atlassian.com/incident-management/incident-communication/templates).