Most likely: a CloudFlare administrator flagged the site to be routed around CloudFlare at the DNS level. The DNS change may not have propagated yet or the site owner may have hard wired DNS to statically point at CloudFlare.
Less likely: a CloudFlare administrator flagged the site for abuse or terms of service violations and the new DNS routing information has not yet fully propagated