https://flyitalyadsb.com/en/status/feed.xml 2026-10-23T09:21:00.000Z FlyItalyADSB https://flyitalyadsb.com/en/status/#evento-2026-10-20-firewall-blocks 2026-10-20T19:22:00.000Z 2026-10-23T09:21:00.000Z <p><b>Investigating</b> — 2026-10-23 08:55 UTC<br/>A visitor writes that the site blocks them with &quot;Sorry, you have been blocked&quot; after clicking English, and that no page opens for them since.</p><p><b>Identified</b> — 2026-10-23 09:05 UTC<br/>We find the cause in the firewall events and reproduce it. It isn&apos;t just them: about 50 visitors a day since 20 October.</p><p><b>Resolved</b> — 2026-10-23 09:21 UTC<br/>Fix applied and checked against every referrer that used to be blocked. Visitors who were blocked can open the site and the map again, with nothing to do on their side.</p><p>From the evening of 20 October, visitors arriving from a <strong>Bing</strong> search, a <strong>Facebook</strong> link or <strong>Naver</strong> could open the first page, but from the next one on they were blocked on the whole site and the map. The block stayed in the following days too.</p> <p>The cause was a generic anti-attack firewall rule (OWASP) that read the statistics cookie set on arrival as suspicious: that cookie holds the address of the page the visitor came from, and some query strings pushed it over the rule’s threshold. About 50 visitors a day were affected between 20 and 23 October. <strong>The REST API, the MCP server and the data were not affected.</strong></p> <p>That rule no longer applies to the pages of the site and the map, which are static; it stays on the API and on everything that receives data. We also added a daily check that tells us when the firewall blocks many more real visitors than usual, so a mistake like this one shows up for us the next day instead of in a report.</p> <p>If you still see the block page, clear the site data for flyitalyadsb.com or try a private window, and <a href="/en/contact/">write to us</a>.</p>