<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Under the Hood :: alwaysdata Documentation</title><link>https://help.alwaysdata.com/en/under-the-hood/</link><description>Index 2026-05-05: Analysis of an HTTP/2 connectivity incident with Cloudflare</description><generator>Hugo</generator><language>en</language><atom:link href="https://help.alwaysdata.com/en/under-the-hood/index.xml" rel="self" type="application/rss+xml"/><item><title>Analysis of an HTTP/2 Connectivity Incident with Cloudflare</title><link>https://help.alwaysdata.com/en/under-the-hood/2026-05-05-connectivity-incident-cloudflare/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://help.alwaysdata.com/en/under-the-hood/2026-05-05-connectivity-incident-cloudflare/</guid><description>Date | May 5th, 2026 Authors | François Lesueur &amp; Cyril Baÿ From March 25th to 27th, 2026, we experienced service disruptions for websites hosted with us behind a Cloudflare relay. This article looks back at the incident, its causes, and the steps taken to resolve it. It also aims to document one way to handle this type of incident.
This incident is (briefly) described in a Cloudflare status and a thread on their forum. On our end, the incident was tracked in this status.</description></item></channel></rss>