Activating *both* probably will tell us nothing - both companies are in all datacenters, so they'll
Activating both probably will tell us nothing - both companies are in all datacenters, so they'll route packets to each other at random 
EIf I understand it correctly having both enabled would use Argo to route to AWS's global network which.. wouldnt really achieve anything, and then AWS Global Accelerator would take over and do the actual routing, rendering Argo completely useless
EBenchmarking both would be really cool to see but unfortunately would be difficult to do reliably
EI think so too. So I'd want to measure performance of "Edge -> CF Argo -> CF Tunnel -> Origin" vs "Edge -> AWS Global Accelerator -> origin". Seems this will be difficult to do now if I have only one on/off switch. Will need to create a different account.
EYes, benchmarking the network can be like reading tea leaves. For this case, I'd setup a simple echo page for each network route, and run WebPageTest / SpeedVitals on it.
Kuse spectrum :^))))
Kvery cheap
EI care somewhat. Right now, to my best measure, routing everything through a Cloudflare Worker adds 80-250ms latency (as compared to routing directly to origin). This is acceptable, but 500ms wouldn't be. Our specific use-case is an SPA with API calls, so it's mostly plaintext and relatively little bandwidth.
Kthat's not very orange cloud of you
K
JWait, thatβs not kian
Jthatβs Kian with reversed mouth
K
DI envy all these custom(?) stickers & emojis
EWe all do
T
Kdidn't even know headers with underscores were valid but RFC7230 says they supposedly are
Jseems it's still happening for a few folks. Same errors/location?
JIf it's all the same as yesterday, then probably no need. But if anything has changed, feel free! 
JDom's the best!
Jto confirm, this isn't impacting your ability to actually use the Workers dashboard, right? It's just a bit noisy with the errors (which seem to be analytics related)?
Jalso cc @williamhorning and @plotzes who I know were also having issues yesterday
Jthe workers page thing?
Jyeah so
Jthe errors are related to the request count endpoint
Jit doesnt break the functionality
Jonly spits out an absolute ton of errors
Jyeah im still getting the error
Jsame account id
Jat the same colo (PIT)
Jcool thanks, just trying to gauge severity. Noisy non-user triggered errors are definitely annoying, but at least things are usable 
Jits working more it seems?
Jnope
Ji just got lucky
Jworkers still run and the dash looks fine
Jgreat, thanks for the info y'all 
J is the endpoint that's failing