Increase in Cloudflare blocks Friday 13th February 2026 13:19:08

Update on Cloudflare Blocks We are actively working with Cloudflare regarding the recent increase in access blocks affecting Koha and Aspen. Cloudflare has identified that many of the recent blocks are being triggered by their JavaScript Detection system, which is assigning false-positive bot scores. Their engineering team is investigating this behavior on their side. In the meantime, we are seeing indications that some of these challenges may be failing due to browser-side issues (such as cached data or stored cookies interfering with Cloudflare’s JavaScript checks). If you are currently experiencing a block, please try the following:

1. Fully close your browser.
2. Clear cache and cookies for ByWater-hosted services (or clear all browsing data).
3. Reopen the browser and try again.
4. If the issue persists, try an incognito/private window as a quick test.

If you are still blocked after completing these steps, please reply with:

• The public IP address of the affected workstation
• The Cloudflare Ray ID shown on the block page
• The full URL being accessed at the time

We appreciate your patience while Cloudflare continues their investigation. We will provide additional updates as soon as more information becomes available.

We are continuing to work with Cloudflare regarding the recent increase in traffic blocks affecting partner access to Koha and Aspen. Cloudflare has confirmed that they are actively investigating the behavior on their side. An internal escalation has been opened with their engineering team to determine what is causing the unexpected increase in blocks. In parallel, they are reviewing our configuration to identify any potential adjustments or workarounds that may help reduce impact while the deeper investigation continues.

At this time:

• The issue remains under active review by Cloudflare engineering.
• We are in direct contact with their Network Security team.
• No final root cause has yet been identified. If you experience a block, please continue to open a support ticket and include:
• The public IP address of the affected machine
• The Cloudflare Ray ID shown on the block page
• The full URL/query being accessed at the time

This information is critical for escalation and log correlation with Cloudflare. We will provide another update as soon as we receive additional information from Cloudflare engineering.

Update: investigation so far has shown that Cloudflare appears to be blocking traffic more aggressively today than in the past, and we are working with Cloudflare on this sudden change in behaviour. If you experience a block, please open a ticket including the following: the public IP of the machine, the RayID provided by Cloudflare, and the query/URL that was trying to be accessed at the time of the block.