Again

[Vespar]

No, she is still correct and it's been reported numerous times. The current issue may be DDoS, but Level3.net has been causing issues for SE for the past year for numerous people. Also notice how her post said: "Not caused by SE", so regardless, she is still correct even in that regard, so there's no "words to be eaten", sorry Vespar.

People kept saying in this thread that level3 had an outage... But SE has just confirmed this wasn't the case. So Im less inclined to believe the folks who kept providing "misinformation" which was again... MY ONLY argument towards people on here. Packet Loss and DDoS attacks are two entirely different things, though they may be apples and oranges to someone who has no clue. Which is why, rather than believing the misinformation, I requested folks wait to hear SE's word on the matter and it turns out my hunch was right.

[Tupsi]

People kept saying in this thread that level3 had an outage... But SE has just confirmed this wasn't the case.

That's the thing actually - Level3.net did have an outtage recently and is currently having spotty outtages, it just happens that wasn't the case for XIV the past 2 days, however people who say level3 causes issues are correct since that too has been confirmed by numerous companies, but level3 happens to be the biggest (and cost effective) data solution people use (and clearly a pretty solid contract that companies can't just sign out of.)

So people naturally pointed towards that because that has already been confirmed to be a problem with some MMOs and services recently.

[Squintina]

DDOS still has to go through hops. It doesn't just magically show up at the server... Since it seems the servers are near level 3 hops, it would make sense that a DDOS would end up both affecting the server AND level 3 traffic. Level 3 having issues is an indicator of either bad switches, or an overload. A DDOS powerful enough could cause the 2nd so if anything the level 3 issues were an indicator of a possible DDOS that was packeting through their hops.

Which in the end - still not SE's fault