3 ms·
Seems to be back now. https://twitter.com/#!/CloudFlareSys/status/197785441360023552 https://twitter.com/#!/CloudFlareSys/status/1977854413600235... blames an
by eli 15y ago
Seems to be back now.
https://twitter.com/#!/CloudFlareSys/status/197785441360023552 https://twitter.com/#!/CloudFlareSys/status/1977854413600235... blames an upstream network issue. But I dunno, cloudflare.com was giving me a 502 error from ngnix, which indicates a cloudflare-backend problem.
- jjoe 15y agoJust thought I'd expand on this part of your comment: "cloudflare.com was giving me a 502 error from ngnix, which indicates a cloudflare-backend problem" Everything is a backend (ex: your server). Your CF hosted website is a backend to their front end (Nginx). Except the "backend" here is located in a remote network where your actual server is hosted. So it could very well be a routing issue between their network (Nginx nodes) and your server. Hence the 502 (backend unreachable). Regards
- deleted 15y ago[deleted]
- micro-ram 15y agoYes, but CloudFlare is supposed to show a cached copy of my site when my server (i.e. backend) is unreachable.