Skip to main content
Atlassian Statuspage

statuspage.io domain not resolving in Brazil region for some users

Degraded Lasted 25d 12h · started · Atlassian Statuspage's page

Level
confirmed
Worst impact
Degraded
Components
HTTP Pages, Web Portal, HTTPS Pages, Public API
Regions
latam

What to do

  • Check whether you use Atlassian Statuspage HTTP Pages, Web Portal, HTTPS Pages, Public API in latam. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 25d 12h it lasted.

    Anything that failed between 2025-02-13 19:22 UTC and 2025-03-11 07:52 UTC may need a replay.
  • Subscribe to Atlassian Statuspage's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=statuspage works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Atlassian Statuspage 6

  1. investigating

    We are currently investigating this issue.

    provider

  2. investigating

    We are continuing to investigate this issue.

    provider

  3. identified

    We have determined that the connectivity issue is due to a DNS name resolution problem affecting certain ISPs in Brazil, which are unable to resolve *.statuspage.io domains. This issue does not impact all Brazilian customers and subscribers; it varies depending on the customer's or subscriber's ISP. Customers using custom domains for their status pages are not affected. While your Statuspage remains available, ISP configurations are preventing traffic from resolving the Statuspage domain. We are exploring mitigation strategies, but we advise affected customers to contact their ISP to understand why their ISP cannot resolve *.statuspage.io domains.

    provider

  4. identified

    Please follow the steps mentioned in the below link to mitigate the DNS issues in Brazil for statuspage.io domains: https://community.atlassian.com/t5/Statuspage-articles/Mitigation-steps-for-statuspage-io-domain-ISP-Issues-in-Brazil/ba-p/2951025#M274

    provider

  5. identified

    We are actively working with ISPs to resolve the current issues and to better understand the recent changes that have contributed to these problems. We also encourage our customers to contact their ISPs, as this appears to be an ISP-specific issue. Our investigation show that statuspage.io domains can be resolved using Google or Cloudflare DNS resolvers, such as 1.1.1.1 and 8.8.8.8. Please refer to the steps outlined in our community post to access all Statuspage-based domains effectively. https://community.atlassian.com/t5/Statuspage-articles/Mitigation-steps-for-statuspage-io-domain-ISP-Issues-in-Brazil/ba-p/2951025#M274

    provider

  6. resolved

    After a thorough investigation, we have determined that the recent connectivity issues experienced for statuspage.io domains in Brazil were isolated to specific Internet Service Providers (ISPs) within Brazil and there was no impact or issue with Statuspage’s infrastructure and DNS configurations itself. Our team is actively monitoring the situation and trying our best to reach out to the relevant ISPs to ensure that access issues are resolved for all affected users. If connectivity issues persist, and you are located in Brazil, we kindly ask that you open a support request with your internet service provider or follow our community post to resolve the issue. https://community.atlassian.com/forums/Statuspage-articles/Mitigation-steps-for-statuspage-io-domain-ISP-Issues-in-Brazil/ba-p/2951025#M274

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-b30ca54f18

Is Atlassian Statuspage still down?

No, this incident was resolved 2025-03-11 07:52 UTC. For Atlassian Statuspage's live state, see https://down.guide/statuspage.

How long did it last?

25d 12h, from 2025-02-13 19:22 UTC to 2025-03-11 07:52 UTC, by the times Atlassian Statuspage posted.

What was affected?

Atlassian Statuspage named HTTP Pages, Web Portal, HTTPS Pages, Public API in latam.

What caused it?

Atlassian Statuspage hasn't published a root cause. If it does, it shows here.

Where does this come from?

Atlassian Statuspage's official status page, https://metastatuspage.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.