Guard experienced a major incident on October 24, 2023, lasting 9h 38m. The incident has been resolved; the full update timeline is below.
Update timeline
- investigating Oct 24, 2023, 12:22 AM UTC
We are investigating an issue with emails that have been sent out to admins stating domain verification is failing. We will provide more details within the next hour.
- investigating Oct 24, 2023, 01:49 AM UTC
We are continuing to investigate this issue. We are aware that this incident is impacting custom email configuration and some Jira notifications are being sent with the default email address instead of the configured custom email. We will provide more details in the next hour.
- investigating Oct 24, 2023, 02:44 AM UTC
The investigation is still ongoing. We are working on a mitigation.
- identified Oct 24, 2023, 05:04 AM UTC
We continue to work on resolving the issue with domain verification. We have identified the root cause and expect recovery shortly.
- monitoring Oct 24, 2023, 06:15 AM UTC
We have mitigated the problem. We are now monitoring this closely. Please contact us at https://support.atlassian.com/contact/ if you are still facing issues with email domain verification.
- identified Oct 24, 2023, 06:48 AM UTC
We identified that the mitigation method doesn't fix the issue in some affected Cloud instances. We are continuing with the investigation.
- identified Oct 24, 2023, 07:47 AM UTC
We have identified the issue and a fix is currently being implemented. We expect this issue to be resolved shortly.
- resolved Oct 24, 2023, 10:01 AM UTC
Between 22:00 UTC 23rd October and 07:45 UTC 24th October, we experienced an issue with custom domain validation, this resulted in Atlassian Access notification emails for some customers to be sent from generic Atlassian email domains rather than the custom domain email address. The issue has been resolved and the service is operating normally.