This is pure DNS only. Doesnât have anything to do with actual availability of sites using CloudFlare.
I wonder how many emails youâve sent in the first 5 minutes of the outage
Your domain registrar probably provides basic DNS for free.
Itâs not free, but I use ClouDNSâ premium DNS and it works very well. They do appear to have a free plan, but it doesnât give you access to their anycast servers: Premium DNS hosting plans. Test for Free | ClouDNS
some more metrics for Cloudflare
This outage was unfortunately due to cpu load spikes across Cloudflare systems - I know the reason for the spikes - related to CF WAF 
(being an official Cloudflare MVP and all) but probably let CF folks explain the specifics as they normally do via their blog most likely.
edit: dam John is quick https://blog.cloudflare.com/cloudflare-outage/
very informative⌠thanks !
Keep flexing on us mere plebs
At least they clarify all in detail, take the blame, and apologize.
They couldâve just pointed away to external factors.
Again not free but Azure DNS and AWS Route 53 are cheap and great for DNS
I really want to see the regular expression that caused 100% CPU usage. Iâve seen it in the past, and some people have written papers about it (https://dl.acm.org/citation.cfm?id=3236027), but I really want to see what caused it in this particular case 
regex can do that - i.e. bad mod_security regexes etc
Over 4k 
Yeah⌠I linked to a research paper about it. Iâm curious about this particular case and exactly what caused the problem 
They tried to filter your companysâ pervasive webbugs.
This is the regex that broke everything:
.*(?:.*=.*)
Their post-mortem is surprisingly detailed: Details of the Cloudflare outage on July 2, 2019. I wonder if theyâll switch to something like re2 that limits backtracking.
Holy shit thatâs greedier than âMy 600lb lifeâ in a buffet line.