All North American Data Center Worlds Network Technical Difficulties (Oct. 26)

[Hildatoon]

According to the techs for my isp and the error code it is on s.e,'s side and looking through the form I'm not the only one with this result after contancting my provider.

[AureliusDraconium]

According to the techs for my isp and the error code it is on s.e,'s side and looking through the form I'm not the only one with this result after contancting my provider.

Same for me.

[NeoMagus]

This is NOT on SE's side. The issue is with Level 3 and they are experiencing DDoS attacks which is causing this issue. Our ISPs use Level 3's infrastructure to route to the game servers. We're timing out on the Level 3 side. SE's servers are all up and running. Unless YOUR ISP adjusts its routing to by pass Level 3 you will not be able to log in.

According to the techs for my isp and the error code it is on s.e,'s side and looking through the form I'm not the only one with this result after contancting my provider.

Use an unaffected isp and theres no issue, its your provider.. my home Comcast connection even though it is connected to the internet still continues to give 90006 error and say cannot login to server but when using WiFi Mobile Hotspot thru my Verizon cell phone it works fine thank goodness I am grandfathered on unlimited or I would have lost entire day today

[Kosmos992k]

According to the techs for my isp and the error code it is on s.e,'s side and looking through the form I'm not the only one with this result after contancting my provider.

That's because the techs that you're talking to (even assuming they are techs) are not fully aware of the back bone routing, and so from the point of view of their system, there are no errors on Comcast nodes, and so the errors and time outs are happening "on SE's end". In actual fact there are timeouts at the entry point to Level3's backbone and the Exit point from their backbone. The Comcast folks don't care what happens beyond their network, tey only care about their network, which is operating just fine. So they blame the service provider - in this case SE.

AT&T. Level3.

traceroute to 199.91.189.24 (199.91.189.24), 30 hops max, 38 byte packets
1 108-219-192-1.lightspeed.nsvltn.sbcglobal.net (108.219.192.1) 59.434 ms 23.274 ms 74.581 ms
2 99.174.25.108 (99.174.25.108) 21.750 ms 21.233 ms 21.848 ms
3 99.131.205.110 (99.131.205.110) 23.995 ms 25.058 ms 26.932 ms
4 12.83.112.17 (12.83.112.17) 26.588 ms 12.83.112.9 (12.83.112.9) 25.870 ms 24.877 ms
5 12.122.117.121 (12.122.117.121) 47.885 ms 47.704 ms 47.946 ms
6 * * *
7 ae-11-11.car2.Montreal2.Level3.net (4.69.141.1) 89.625 ms 62.276 ms 69.881 ms
8 ae-11-11.car2.Montreal2.Level3.net (4.69.141.1) 106.250 ms 104.493 ms 83.473 ms
9 ORMUCO-COMM.car2.Montreal2.Level3.net (4.59.178.74) 56.985 ms 57.639 ms 57.244 ms
10 * * *
**snip**

This replicates the tracert output I generated from Charter. once the route leaves charter the 1st hop to Level 3 times out, then I see some level 3 routers and then I get another timeout and see Ormuco, and then on to SE's servers. Basically the interfaces into and out of Level 3 show as problems because Level 3 has an outage preventing it from routing traffic.

Quite why they have a major single point of failure and no fallback position is beyond me.