@thepastrybox Yep, still. Tried clearing cookies/cache and also going via Google, but same result - 522 timeout.
-
-
-
Replying to @thepastrybox
@thepastrybox Afraid not - still get the same error. Maybe it's cached somewhere between me and the host? I'll try switching to OpenDNS...1 reply 0 retweets 0 likes -
Replying to @matthewpennell
@matthewpennell So sorry about that. I literally have no way of finding out what's going wrong...1 reply 0 retweets 0 likes -
Replying to @thepastrybox
@thepastrybox Yeah, very strange. OpenDNS didn't make any difference; trying a traceroute now to see if that helps.1 reply 0 retweets 0 likes -
Replying to @matthewpennell
@thepastrybox Traceroute resolves no problem, ping is fine. Seems Cloudflare has an issue serving the site to me for some reason. :(1 reply 0 retweets 0 likes -
Replying to @matthewpennell
@matthewpennell Argh... Which region are you in?cc:@CloudFlare1 reply 0 retweets 0 likes -
Replying to @thepastrybox
@thepastrybox Eastern Cambridgeshire.@CloudFlare The 522 error page gives me this specific error - Ray ID: 1a16dbbe213c0cd11 reply 0 retweets 0 likes -
Replying to @matthewpennell
@matthewpennell@thepastrybox I was having the same problem (522, same RayID). Using https + www (https://www.the-pastry-box-project.net/ ) works though!2 replies 0 retweets 0 likes -
Replying to @mil336
@mil336@thepastrybox Indeed, that solves it! Some strange combination of protocol and subdomain and@Cloudflare?1 reply 0 retweets 0 likes
@matthewpennell @mil336 @thepastrybox 522s can indicate something blocking requests from our IPs. See: https://support.cloudflare.com/hc/en-us/articles/200171906-Error-522 …
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.