Update on Temporary Access Issues

Written by Eddie Snowie • The Reasonable Adjustment

First, an apology. A recent set of changes to our Cloudflare Worker led to some readers getting blocked when visiting the site. The Worker did not directly block you. The way your device connected to the site through the network triggered an automated rule that stepped in and said no. That rule was too broad. That is on us.

What happened in plain English

We tuned security to keep the noisy stuff out. In the process, a small group of real visitors shared a connection pattern that looked similar to traffic we normally challenge. Our filter could not tell the difference quickly enough. It threw a block. If that was you, we are sorry.

What we fixed

• Adjusted the rule so it recognises legitimate Cloudflare egress and common mobile browser patterns.
• Allowed first party analytics and WordPress API calls that were caught in the crossfire.
• Raised observability so we can spot friendly fire before it becomes a nuisance.

What did not happen

• No security incident. This was configuration, not compromise.
• No risk to your data. The block was a gatekeeping mistake, nothing more.

If you still have trouble

Quick checks you can try:

• Refresh the page and try an ordinary browser tab, not a headless or data saver mode.
• Disable aggressive content blockers for this domain and reload.
• If on mobile, toggle Wi Fi off and on so you pick up a fresh route.

Still blocked or seeing a challenge loop

• Email [email protected] with your device, browser, and an approximate time of the issue.
• If you have it, include the Cloudflare Ray ID from the block page. That lets us fix the exact edge case fast.

Thanks for sticking with us

Stronger security is useful. Accurate security is better. We aim for both. Thank you for the patience while we tuned the dials.

Signed, Eddie Snowie
For The Reasonable Adjustment