I’m experiencing the same issue. My server is also hosted with Aruba, specifically in Data Center IT3 – Bergamo.
We’ve temporarily paused Cloudflare on some of our sites, and while it’s not a permanent solution, it does allow affected users to access the sites correctly.
Most of the error reports I received came from users on Fastweb, but today one user on Telecom Italia also reported issues. Personally, I’m also on a Telecom connection — I noticed some slowdowns, but not full 522 errors.
Let me know if you’ve found anything useful on your end.
Same here, starting April 21st night, Aruba server connected to the Rome node, so from mid of Italy to Sicily.
The rest who uses Milan node seems ok, don’t know if the problem will extent to Milan too.
Hi there, please allow me some time to look into this further. In the meantime, if any user can reliably reproduce the 522 error, please try running the following command, change the hostname to your affected site from the machine experiencing the 522 issue, and see if you did see the 200 http code.
Can you raise a case for this and let us know the case number? Yes, I can see Aruba ASN origin in one of the top ASN seeing this 522 error from Italy in our log.
Hello Ikmal, I’ve similar issue with Fastweb Users from Italy. I’ve just opened a case. Here the reference
Case # : 01482486
Subject : Error 522 from Fastweb Italy
Priority : Urgent
Hello any update on this? We have the same problem since 2 days, multiple connection drops from multiple Italian providers to Aruba IT1 Datacenter, disabling cloudflare protections mitigate the issue
Same problem here affecting the majority of our customers.
Maybe the issue is related to the Vodafone / Fastweb merge that is happening in Italy in these days?
I understand that the issue is mainly in colo=FCO while who’s in colo=MXP is running smoothly.
What about some BGP configurations or reconfigurations that are in place between Fastweb and Vodafone due to the merge?
Hi all, our engineering indicate the issue has been resolved and no action from us either. Something in the Aruba firewalls were blocking these IPs until Aruba took action today. Also, I have confirmed the 522 error no longer is seeing due to this topic issue. Thanks for raising this to us.