where do u see this kind of stuff
where do u see this kind of stuff
CI'm just looking at logpush events which indictate which colo they hit
Cdoesn't mean you could hit arn, could be they removed some routes/partially rerouted, but at least some requests are
Heh too lazy to set it up, is CPH alive?
Cno clue I didn't have anything hitting it before
Hdefinitely ISP issue then, just rerouted to FRA now
Cgoing on a bit of a trip
Cdo you know how your isp was reaching cph before? Could have been peering or their transit was peered, then it dropped and traffic just got scrambled
HI in fact just done a tracert before all of this happened
HTracing route to discord.com [162.159.136.232]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms OpenWrt.lan [192.168.1.1]
2 3 ms 3 ms 3 ms
3 3 ms 3 ms 3 ms
4 5 ms 3 ms 3 ms m-b-peer1-link.se.telia.net [81.228.86.13]
5 4 ms 5 ms 5 ms kbn-b1-link.ip.twelve99.net [62.115.123.158]
6 5 ms 5 ms 5 ms cloudflare-ic-358851.ip.twelve99-cust.net [62.115.46.151]
7 5 ms 5 ms 5 ms 162.159.136.232
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms OpenWrt.lan [192.168.1.1]
2 3 ms 3 ms 3 ms
3 3 ms 3 ms 3 ms
4 5 ms 3 ms 3 ms m-b-peer1-link.se.telia.net [81.228.86.13]
5 4 ms 5 ms 5 ms kbn-b1-link.ip.twelve99.net [62.115.123.158]
6 5 ms 5 ms 5 ms cloudflare-ic-358851.ip.twelve99-cust.net [62.115.46.151]
7 5 ms 5 ms 5 ms 162.159.136.232
Clooks like they used Telia which had an interconnect with cf in cph
HIts now (was) reaching oslo like this:
5 5 ms 5 ms 3 ms kbn-b1-link.ip.twelve99.net [62.115.123.158]
6 4 ms 5 ms 4 ms kbn-bb6-link.ip.twelve99.net [62.115.138.112]
7 12 ms 11 ms 11 ms oso-b1-link.ip.twelve99.net [62.115.116.106]
8 15 ms 13 ms 11 ms cloudflare-ic-372160.ip.twelve99-cust.net [80.239.196.115]
9 12 ms 11 ms 11 ms 162.159.138.232
5 5 ms 5 ms 3 ms kbn-b1-link.ip.twelve99.net [62.115.123.158]
6 4 ms 5 ms 4 ms kbn-bb6-link.ip.twelve99.net [62.115.138.112]
7 12 ms 11 ms 11 ms oso-b1-link.ip.twelve99.net [62.115.116.106]
8 15 ms 13 ms 11 ms cloudflare-ic-372160.ip.twelve99-cust.net [80.239.196.115]
9 12 ms 11 ms 11 ms 162.159.138.232
Csounds like cph may indeed be rerouted and the rest was just it changing paths. We were just told that 502/530/etc errors are a known issue they're looking into atm
Hdid they send half of cf's traffic to cph by accident
Cwould be funny lol
Ccph is just a single colo
Hwhat would be even more funny if they send the whole worlds traffic to a tiny datacenter in the middle of nowhere lol
C
Cit's not anymore. Did you see impact? Very possible since it's DOs itself but also possible it was more specific to something
Cahh rip, all resolved now though or still hitting errors?
Hits 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