Pathping during Server Lobby issues

[Jadway]

I'm from Québec City, and i just got dc'd for the third time this hour

[Darkk]

Obviously these issues are more complicated than they appear, but I still stand by my statement that as a content provider, SE has significantly more influence to exert over these issues than I do. I know it's storming like a bastard right now, and if this is just a data center crashing out or whatever, fine, but I still feel it's their responsibility to investigate and inform us. Thanks for the additional information!

[MiniTofu]

Obviously these issues are more complicated than they appear, but I still stand by my statement that as a content provider, SE has significantly more influence to exert over these issues than I do. I know it's storming like a bastard right now, and if this is just a data center crashing out or whatever, fine, but I still feel it's their responsibility to investigate and inform us. Thanks for the additional information!

It's on their end this time, from what it seems.

[MadCabbit]

I've been thinking up until this point that the problem has solely been on Square's side, because every traceroute I've done has never shown anything. It still doesn't, but I gave pathping a try, since I never knew MS set up a more versatile tool like that, and I'm also getting a bump on the iweb hop:

7 13ms 0/ 100 = 0% 0/ 100 = 0% te0-3-0-2.ccr21.cle04.atlas.cogent
co.com [38.122.54.41]
0/ 100 = 0% |
8 24ms 0/ 100 = 0% 0/ 100 = 0% be2009.ccr21.alb02.atlas.cogentco.
com [154.54.25.89]
0/ 100 = 0% |
9 28ms 0/ 100 = 0% 0/ 100 = 0% be2088.ccr21.ymq02.atlas.cogentco.
com [154.54.43.17]
0/ 100 = 0% |
10 31ms 0/ 100 = 0% 0/ 100 = 0% 38.140.46.2
0/ 100 = 0% |
11 --- 100/ 100 =100% 100/ 100 =100% te7-4.dr9.mtl.iweb.com [184.107.1.
110]
0/ 100 = 0% |
12 31ms 0/ 100 = 0% 0/ 100 = 0% 72.55.128.44
0/ 100 = 0% |
13 31ms 0/ 100 = 0% 0/ 100 = 0% 184.107.107.176

Trace complete.

Now, this could mean it's iweb/their colocation/datacenter provider is at fault, but it could be a problem with the link between that hop and the one before causing the issue, which could still reflect back on cogentco. Seeing cogentco popping up here may be a common thread. There's also the possibility this one hop just doesn't accept pings. But, once again, if there are enough people disconnecting that go through cogentco, that's probably the culprit. That and level3, but they've pretty much become a bad running joke.

[MiniTofu]

Tracert to my Lamia server specifically, that I can't connect.

Tracing route to 199.91.189.38 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 192.168.1.1
2 10 ms 8 ms 7 ms <removed>
3 8 ms 10 ms 10 ms <removed>
4 10 ms 10 ms 10 ms xe-0-1-1_0-bdr01-mtl.teksavvy.com [206.248.155.109]
5 18 ms 15 ms 18 ms xe-0-0-0_2220-bdr03-tor.teksavvy.com [192.171.63.165]
6 18 ms 17 ms 19 ms te0-7-0-22.ccr22.yyz02.atlas.cogentco.com [38.122.69.197]
7 18 ms 22 ms 16 ms be2373.ccr21.yyz02.atlas.cogentco.com [154.54.46.33]
8 25 ms 24 ms 31 ms be2090.ccr21.ymq02.atlas.cogentco.com [154.54.30.206]
9 23 ms 25 ms 23 ms 38.122.42.34
10 * * * Request timed out.
11 * * 132 ms 192.34.76.2
12 * * * Request timed out.
13 132 ms * 135 ms 199.91.189.38

Trace complete.