I’ve also done this for one of our sites and it’s working now. Good to reiterate that it’s a temp solution at best and it’s important to be able to return the DNS to correct settings when this issue resolves.
Yep all domains still down in AU here. Is there any other hostnames working for anyone?
All our sites - static, SSR or otherwise are not accessible from AUS.
Turning on a VPN to the US works. Don’t forget about us @Netlify
According to GPT:
When will it be fixed?
Historically these “single-region edge misroutes” clear within a few hours once Netlify’s SRE team is alerted and re-publishes their GeoDNS / route-origin data.
Netlify’s Oceania edge is accidentally pointing traffic at a Microsoft anycast IP that drops packets inside Australia & New Zealand.
@MWAV Yeah, that’s their automated response.
Under normal circumstances you’re looking at a few day turnaround on tickets.
I’d expect them to update here once they actually notice there is a wider issue.
From what I’ve seen over the years they’re a smaller team than you may think, and I believe the bulk of their staff are located in San Francisco, where it’s now after 6pm.
While they mention having support staff in a few time zones, I primarily only see @hrishikesh responding on the forum outside of the hours of the rest of their team.
They’re probably all wide awake and pounding coffee though after they day they would have had. As a fellow developer, I don’t envy them 
Same here. All AU customers are unable to access our platform.
Same issue here, all sites not accessible from AU. We did delete our edge-functions folder and trigger a redeploy. Weirdly it seemed to fix one of our sites (.com.au) but our .com and .co.nz are still down.
Can confirm this approach worked for us too.
While a temporary fix, this is working well for the meantime the IP I have changed things to is 52.220.155.145 as an A record, changing from the CNAME.
Once things are resolved we will change it back.
I’m not running edge functions and I’ve tried redeploy’s (including clearing the cache) and that isn’t working for me
They hear us!
Is anyone from Netlify working on this?
We are really hurting here. Our customers are furious.
@mrwiyums They are now, as per the banner at the top of the forum…
my sites are back now
My site just started working.
I’d been struggling to access a Netlify site via a .it domain, and that’s suddenly started working too.
I had thought it was just the site, but seems it was related.
This has been an incident: Netlify Status - Sites Not Accessible in AU Region (now more or less resolved).
Seems to have been some kind of DNS issue - both our internal *.netlify.app staging site and our production site on a custom domain were returning the same A record (13.107.135.208) since 5:40am this morning. 8 hours later, and 2 minutes after finally updating the status page to say there were issues in AU, the IP being returned is now 13.55.224.97 and sites are live again.
Really hope there’s some monitoring fixes that are put in place for this as a result of the outage…