CloudFlare is an excellent service from many points of view, and for web site owners or web system administrators is often a bubble of oxygen. DNS manager, system of Caching, administration SSL with rules of HTTPS redirect strength, crypto, firewall and many other options are available for free via Cloudflare.
In order to benefit from the Cloudflare service, users must open a free account and add domain or domains to the console. After this step, the domain name registrant will add the new nameserver (s) indicated in the Cloud Account. From that point on, all DNS administration will be done from this service.
Like any service, even if everything works well in most of the time, there are times (quite rarely) where website owners are confronted with problems whose source is Cloudflare.
502 Bad Gateway - Cloudiness
"502 Bad Gateway"Is often an HTTP networking error generated by the host server.
A recent problem at Cloudflare generated this error, and the impact was huge. Hundreds of thousands or maybe even millions of websites could not be accessed better than 30 minutes. From blogs, portals, online publications, and to large service providers and social networks could not be accessed due to Cloudflare.
HTTP 502 errors
resolved - Cloudflare has resolved the issue and services have resumed normal operation.
Jul 2, 14: 57 UTC
Update - Cloudflare has implemented a fix for this issue and is currently monitoring the results.
Major outage has affected all Cloudflare services globally. We saw a massive spike in CPU that caused primary and secondary systems to fall over. We shut down the process that caused the CPU spike. Service restored to normal within ~ 30 minutes. We're now investigating the root cause of what happened.
Jul 2, 14: 50 UTC
Monitoring - Cloudflare has implemented a fix for this issue and is currently monitoring the results.
We will update the status once the issue is resolved.
Jul 2, 14: 15 UTC
Investigating Cloudflare is observing network performance issues. Customers may experience 502 errors while accessing sites on Cloudflare.
We are working to mitigate the impact on Internet users in this region.
Jul 2, 13: 52 UTC
However, there were also sites that, even if they were using Cloudflare, functioned in normal parameters. All these websites that worked, did not DNS and HTTP proxy (CDN) activated.
502 Bad Gateway Resolution / Cloudiness
Access the Cloud Account and go to the domain where you encountered this error. In the DNS section, set "DNS only". The Icon with the cloud will change from orange to gray.
From that point on, all traffic will bypass Cloudflare, and the real IP Internet Exit will be exposed, but the service will work normally.