Confluence: Intermittent DNS Resolution Errors
Timeline of updates
- resolved
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.
From Confluence’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on confluence.status.atlassian.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Confluence, started 2019-10-22 22:32 UTC, resolved after 5.5 h, 1 update(s).
- Title
- Intermittent DNS Resolution Errors
- Vendor
- Confluence
- Date
- URL
- https://rewindex.com/company/confluence/incidents/lyc1k68yws4t
Confluence profileRecent Confluence incidentsAll outages on October 22, 2019Confluence in October 2019MarkdownJSON