"Further detail will be provided as more information becomes available."
"This incident has been resolved."
I guess more information hasn't become available, even though they've apparently fixed the issue. Or did they forget they offered to give more information?
Not a fan of companies / people who just say what they think others want to hear, with no regards for actually understanding and meaning what they say.
I guess their focus was to actually solve the issue. Now once everything is stable the people that were involved in fixing this will have the time and capacity to share what they found. I'm sure we'll see a blogpost with more details in the coming days.
20 comments
[ 2.8 ms ] story [ 45.2 ms ] threadedit: seems to have either gotten working again or hard refresh on browser fixed it.
I think there is a DNSSEC issue with the .com zone, but it's spotty (fails 75% of the time)
If you are using cloudflare then archive.is links does not work anyway :D
https://jarv.is/notes/cloudflare-dns-archive-is-blocked/
"This incident has been resolved."
I guess more information hasn't become available, even though they've apparently fixed the issue. Or did they forget they offered to give more information?
Not a fan of companies / people who just say what they think others want to hear, with no regards for actually understanding and meaning what they say.
Seems like a bad update/patch was pushed to primary resolver?
https://www.cloudflarestatus.com/incidents/j3h00yhjyw6p
CF has a secondary resolver at 1.0.0.1 which should fix the issue
My local dns resolver currently configured with 9.9.9.9 so no issues on my end.