its just very slow for me even though the new route still works
its just very slow for me even though the new route still works
Hsometimes
HI take that back lol its dead again lol
Cup and down
CI mean you're talking on Disc through CF so something must be working
Cyea, they've got a generic status page up now
RI had to refresh Discord a bunch to get here 
Cthey're still working out impact
and trying to find the if (random.chance(0.50) { explode } /s
and trying to find the if (random.chance(0.50) { explode } /s
Rbut I haven't experienced any more issues since then
RIt was an immediate 502 too like it wasn't even trying to reach the origin servers.
CCF has internal mechanisms to give up/not flood the origin endlessly fwiw, only so many connections allowed to attempt at a time and such protections to try to avoid flooding failing origin servers. There's a blog post about it somewhere
Ccould be something else too, who knows
Rand down again 
REven cdn-cgi/trace 502s
DFor REST APIs, does using HTTP/2 gain anything over HTTP/1.1?
Ayes
Aits a better protocol use it where you can
Aany news on ech?
CCwell maybe same root cause but diff status post at least
Dhmm, why isn't it the default everywhere then?
Aits used wherever its supported
RA 
localhost
EEmail Routing enforces DMARC so if the sending domains setup disallows spoofing then that wouldn't reach you at all
VHow does one disable 
Advanced Certificate Manager
Vnice, ty!
S:(
Sat least my worker responds lol
DHey, I'll try to escalate this
AIf it's being escalated I'm sure you don't need it, but I'm also seeing the blocked message
DWe've escalated this to the team, thanks for your reports!
Vme too!
Amight be a good growth hack.... you have been blocked. Upgrade to a enterprise plan to get access 
