So I think this is pretty clearly on your end, SE. I'm willing to be patient if you provide some kind of status report/update but this has been 3 days straight of wild instability, and I know it isn't my connection. Please fill us in! I want to continue giving you money so you can continue providing me with gaming. Don't make me not want to give you money, please!
C:\Users\Adam>pathping 184.107.107.176
Tracing route to 184.107.107.176 over a maximum of 30 hops
0 <deleted>
1 <deleted>
2 <deleted>
3 agg2-sea-a-t6-1-4000.bb.spectrumnet.us [216.243.28.205]
4 cr2-sea-b-te-0-0-0-23.bb.spectrumnet.us [174.127.140.125]
5 cr1-pdx-t6-2.bb.spectrumnet.us [174.127.141.86]
6 te3-5.ccr01.pdx01.atlas.cogentco.com [38.104.105.73]
7 te0-0-1-1.rcr11.pdx02.atlas.cogentco.com [154.54.0.86]
8 te0-0-1-2.rcr11.boi01.atlas.cogentco.com [154.54.40.98]
9 te0-0-0-8.ccr21.slc01.atlas.cogentco.com [154.54.40.89]
10 be2126.ccr21.den01.atlas.cogentco.com [154.54.25.65]
11 be2128.ccr21.mci01.atlas.cogentco.com [154.54.25.174]
12 be2156.ccr41.ord01.atlas.cogentco.com [154.54.6.86]
13 be2079.ccr21.yyz02.atlas.cogentco.com [154.54.27.182]
14 be2090.ccr21.ymq02.atlas.cogentco.com [154.54.30.206]
15 38.140.46.2
16 te7-4.dr9.mtl.iweb.com [184.107.1.110]
17 72.55.128.44
18 184.107.107.176
Computing statistics for 450 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 <deleted for privacy>
0/ 100 = 0% |
1 1ms 0/ 100 = 0% 0/ 100 = 0% <deleted for privacy>
0/ 100 = 0% |
2 4ms 0/ 100 = 0% 0/ 100 = 0% <deleted for privacy>
0/ 100 = 0% |
3 9ms 0/ 100 = 0% 0/ 100 = 0% agg2-sea-a-t6-1-4000.bb.spectrumne
t.us [216.243.28.205]
0/ 100 = 0% |
4 4ms 0/ 100 = 0% 0/ 100 = 0% cr2-sea-b-te-0-0-0-23.bb.spectrumnet.us [174.127.140.125]
0/ 100 = 0% |
5 36ms 0/ 100 = 0% 0/ 100 = 0% cr1-pdx-t6-2.bb.spectrumnet.us [174.127.141.86]
0/ 100 = 0% |
6 20ms 0/ 100 = 0% 0/ 100 = 0% te3-5.ccr01.pdx01.atlas.cogentco.com [38.104.105.73]
0/ 100 = 0% |
7 7ms 2/ 100 = 2% 2/ 100 = 2% te0-0-1-1.rcr11.pdx02.atlas.cogentco.com [154.54.0.86]
0/ 100 = 0% |
8 18ms 0/ 100 = 0% 0/ 100 = 0% te0-0-1-2.rcr11.boi01.atlas.cogentco.com [154.54.40.98]
0/ 100 = 0% |
9 25ms 0/ 100 = 0% 0/ 100 = 0% te0-0-0-8.ccr21.slc01.atlas.cogentco.com [154.54.40.89]
0/ 100 = 0% |
10 37ms 0/ 100 = 0% 0/ 100 = 0% be2126.ccr21.den01.atlas.cogentco.com [154.54.25.65]
0/ 100 = 0% |
11 49ms 0/ 100 = 0% 0/ 100 = 0% be2128.ccr21.mci01.atlas.cogentco.com [154.54.25.174]
0/ 100 = 0% |
12 60ms 0/ 100 = 0% 0/ 100 = 0% be2156.ccr41.ord01.atlas.cogentco.com [154.54.6.86]
0/ 100 = 0% |
13 75ms 0/ 100 = 0% 0/ 100 = 0% be2079.ccr21.yyz02.atlas.cogentco.com [154.54.27.182]
0/ 100 = 0% |
14 82ms 0/ 100 = 0% 0/ 100 = 0% be2090.ccr21.ymq02.atlas.cogentco.com [154.54.30.206]
0/ 100 = 0% |
15 82ms 0/ 100 = 0% 0/ 100 = 0% 38.140.46.2
0/ 100 = 0% |
16 --- 100/ 100 =100% 100/ 100 =100% te7-4.dr9.mtl.iweb.com [184.107.1.110]
0/ 100 = 0% |
17 82ms 0/ 100 = 0% 0/ 100 = 0% 72.55.128.44
0/ 100 = 0% |
18 82ms 0/ 100 = 0% 0/ 100 = 0% 184.107.107.176
Trace complete.
C:\Users\Adam>
Pathping during Server Lobby issues
Printable View
-
11-19-2014, 03:31 PMDarkkPathping during Server Lobby issues
-
11-19-2014, 03:32 PMDarkk
Country: Canada
Region: Quebec
City: Montreal
Postal Code: h3e1z6
Latitude/Longitude: 45.500000 / -73.583298
ISP: "Iweb Technologies"
Organization: "Iweb Technologies"
Host Name: te7-4.dr9.mtl.iweb.com
The number of this IP address is 184.107.1.110. This IP address is active in Canada, and registered in Montreal, Quebec. IP Country code is CA. IP address is assigned to "Iweb Technologies". In organization "Iweb Technologies". It is also assigned to a hostname te7-4.dr9.mtl.iweb.com. IP address longitude is -73.583298 and latitude is 45.5. Postal code of this IP is h3e1z6.
from IPDB.at -
11-19-2014, 03:33 PMDarkk
Please contact this ISP and do what you have to to clear the line. You as a content provider have significantly more influence to do so than I do as a consumer who is NOT a customer of this ISP.
Thank you,
Darkk -
11-19-2014, 03:42 PMMiniTofuI'm from Montreal, iWeb is not really an ISP. It's a cluster server (datacenter), colocation server, I had webhosting service from them long ago and they were so-so.Quote:
Originally Posted by Darkk
Pinging from Montreal:
Tracing route to 184.107.107.176 over a maximum of 30 hops
1 1 ms 1 ms 1 ms 192.168.1.1
2 6 ms 7 ms 7 ms <removed>
3 12 ms 9 ms 8 ms <removed>
4 18 ms 17 ms 9 ms xe-0-1-0_0-bdr01-mtl.teksavvy.com [192.171.63.17]
5 17 ms 17 ms 17 ms ae2_10-bdr01-nyc.teksavvy.com [206.248.140.218]
6 26 ms 23 ms 25 ms Assigned23.nyiix.net [198.32.160.23]
7 29 ms 29 ms 24 ms po23.cr4.mtl.iweb.com [67.205.127.117]
8 25 ms 26 ms 25 ms te7-3.dr9.mtl.iweb.com [67.205.127.214]
9 24 ms 25 ms 25 ms 72.55.128.44
10 26 ms 25 ms 25 ms 184.107.107.176
Trace complete. -
11-19-2014, 03:44 PMBlaiseArath
7 19 ms 18 ms 18 ms
8 18 ms 19 ms 66 ms
9 48 ms * 149 ms
10 39 ms 32 ms 171 ms ae-11-11.car2.Montreal2.Level3.net ]
11 32 ms 31 ms 32 ms ORMUCO-COMM.car2.Montreal2.Level3.net [
12 54 ms 54 ms 54 ms
13 49 ms 49 ms 51 ms
14 62 ms 51 ms 52 ms
15 51 ms 51 ms 49 ms
Not mine. Friends. (Level3ofcourseright) -
11-19-2014, 03:44 PMJadway
I'm from Québec City, and i just got dc'd for the third time this hour
-
11-19-2014, 03:47 PMMiniTofuThat's the Level3 from US to Montreal backbone connection.Quote:
Originally Posted by BlaiseArath
Tracert from Montreal
Tracing route to 199.91.189.74 over a maximum of 30 hops
1 1 ms 1 ms 1 ms 192.168.1.1
2 9 ms 8 ms 9 ms <removed>
3 9 ms 8 ms 9 ms <removed>
4 11 ms 10 ms 12 ms xe-0-1-0_0-bdr01-mtl.teksavvy.com [192.171.63.17]
5 16 ms 20 ms 18 ms xe-1-1-0_2210-bdr04-tor.teksavvy.com [192.171.63.161]
6 18 ms 21 ms 16 ms te0-7-0-22.ccr21.yyz02.atlas.cogentco.com [38.122.69.201]
7 25 ms 27 ms 25 ms be2090.ccr21.ymq02.atlas.cogentco.com [154.54.30.206]
8 24 ms 24 ms 24 ms 38.122.42.34
9 * * * Request timed out.
10 24 ms 22 ms 23 ms 192.34.76.2
11 25 ms 25 ms 25 ms 199.91.189.234
12 23 ms 25 ms 25 ms 199.91.189.74
Trace complete. -
11-19-2014, 03:48 PMDarkk
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!
-
11-19-2014, 03:50 PMMiniTofu
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. -
11-19-2014, 03:51 PMMiniTofuIt's on their end this time, from what it seems.Quote:
Originally Posted by Darkk
-
11-19-2014, 04:06 PMMadCabbit
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.