News for hackers. Stuff that matters.
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by Quad9 on Wednesday July 16, 2025 @12:31PM (#44584186)
What is your ticket #? Let's see if we can get this resolved for you.
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by dmitrygr on Wednesday July 16, 2025 @05:00PM (#44586721)
Why not address the REAL issue:

> I haven't been able to find any recourse. [...] there seems to be no way to clear my name.

Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by seb1204 on Wednesday July 16, 2025 @05:25PM (#44586952)
From the parent comment the path of recourse is a ticket. Does not help if hn is needed to have it looked at.
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by BenjiWiebe on Thursday July 17, 2025 @11:25AM (#44594381)
Looks like no ticket was actually created until now though.
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by Aachen on Wednesday July 16, 2025 @08:53PM (#44588559)
Oh hey, didn't expect this to actually be seen by many people, let alone you guys!

There was no ticket number yet because I was mainly trying to resolve it upstream (whoever made it get into uBlock's default block list, Quad9, and probably other places) and then today when I checked your site specifically, the link in "False Positive? <Please contact us>" (when you do a lookup for a blocked domain) just links back to itself so I couldn't open a case there either. Now that I look at the page again, with the advice in mind from a sibling comment to just email you, I now see that maybe this is supposed to go to the generic contact form and I needn't go through this domain status page. Opening the contact page now, I see that removal from blocklist is a selectable option so I'll use that :)

The ticket number I just submitted is 41905. Not that I'd want you to now apply preferential treatment, I didn't expect my post above to be seen by many people though I very much appreciate that you've reached out here. Makes me think you're actually interested in resolving this type of issue for small website operators, where the complete block without so much as a heads up felt a bit, well, like that might not get me anywhere. If the process just works as it normally should, that's good enough for me! Thanks for encouraging me to actually open a ticket!

Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by Quad9 on Thursday July 17, 2025 @11:14AM (#44594276)
Glad to hear you were able to submit a ticket! The website form wasn't working a brief time ago. But YES, we want to help! You can DM me in the fedi if you need anything: https://mastodon.social/@quad9dns