Intermittent DNS Resolution Errors
Oct 22, 22:32 UTCOct 23, 04:02 UTC
Duration
5h 29m
Impact
Informational
Root cause
DNS
Atlassian, 90 days
0 incidents
Affected
Not listed by the vendor.
Final update
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.
Timeline
- Resolved · Oct 23, 04:02 UTC
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.
- Monitoring · Oct 23, 01:32 UTC
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.
- Identified · Oct 23, 01:32 UTC
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.
- Identified · Oct 23, 01:08 UTC
We continue to work on resolving intermittent failure connecting to Atlassian Cloud for some cloud customers. We will provide hourly updates.
- Identified · Oct 23, 00:12 UTC
We continue to work on resolving intermittent failure connecting to Atlassian Cloud for some cloud customers. We will provide hourly updates.
- Investigating · Oct 22, 22:32 UTC
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.
More from Atlassian
Full history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Mar 407:31 UTC | Issues with 403 user authentication errors across Atlassian products | none | 0m |
| Sep 1010:26 UTC | Slow loading times and extended response times for Cloud products in the EU-West region. | none | 2h 18m |
| Sep 908:56 UTC | High RDS CPU on multiple environments | none | 9h 16m |
| Sep 209:23 UTC | Slowness in Jira. | none | 8d 3h |
| Aug 2011:46 UTC | Data residency migrations halted. | minor | 2d 23h |
| Jul 320:51 UTC | Some products are hard down | none | 7h 3m |
Also caused by dns
All| Started | Vendor | Incident | Impact | Duration |
|---|---|---|---|---|
| Jul 2720:34 UTC |  Supabase | Delays in creation of DNS recordsSupabase | minor | 2h 2m |
| Jun 2301:05 UTC |  Snowflake | INC20000046Snowflake | major | 1h 30m |
| Jun 410:12 UTC |  DigitalOcean | DNS API ServiceDigitalOcean | minor | 1h 35m |
| May 2223:27 UTC |  Upstash | New Database Creation Failing Due to Upstream Provider IssueUpstash | none | 32m |
| May 1413:57 UTC | DigitalOcean | DNS service, Certificates and Managed MongoDBDigitalOcean | minor | 6h 49m |
| May 715:17 UTC |  MongoDB | AWS Cluster DNS Changes Degraded PerformanceMongoDB | major | 6h 58m |
From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.