What visitors reported during this incident
No visitor reports were filed for this incident.
Having problems with Atlassian (Jira & Confluence) now? Check the current statusUpdates (6)
- Oct 23, 2019, 04:02 AMIntermittent DNS Resolution Errors
Between 23:45 UTC to 02:19 UTC, some customers experienced intermittent failure connecting to Atlassian Cloud. The root cause was an increased DNS error rate from our infrastructure supplier. The supplier fixed the upstream issue and we have verified that the services have recovered. The conditions that caused the issue have been addressed and we are actively working on a permanent fix. The issue has been resolved and the service is operating normally.
Atlassian (Jira & Confluence) ↗ - Oct 23, 2019, 01:32 AMIntermittent DNS Resolution Errors
We have identified the root cause of the intermittent failure connecting to Atlassian Cloud for some cloud customers and have mitigated the problem. We are now monitoring closely.
Atlassian (Jira & Confluence) ↗ - Oct 23, 2019, 01:32 AMIntermittent DNS Resolution Errors
We have identified the root cause of the intermittent failure connecting to Atlassian Cloud for some cloud customers and have mitigated the problem. We are now monitoring closely.
Atlassian (Jira & Confluence) ↗ - Oct 23, 2019, 01:08 AMIntermittent DNS Resolution Errors
We continue to work on resolving intermittent failure connecting to Atlassian Cloud for some cloud customers. We will provide hourly updates.
Atlassian (Jira & Confluence) ↗ - Oct 23, 2019, 12:12 AMIntermittent DNS Resolution Errors
We continue to work on resolving intermittent failure connecting to Atlassian Cloud for some cloud customers. We will provide hourly updates.
Atlassian (Jira & Confluence) ↗ - Oct 22, 2019, 10:32 PMIntermittent DNS Resolution Errors
We are aware that some customers may be experiencing intermittent failure connecting to Atlassian Cloud. We are working with our cloud hosting provider (AWS) to resolve the DNS related errors. We will provide hourly updates.
Atlassian (Jira & Confluence) ↗
What to do next
- Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
- Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
- Watch the provider going forward. Follow Atlassian (Jira & Confluence)'s status feed →
GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.