Resolved Issues with connecting to US servers (not LA)

Sud

Sud

Uncharitable Spy
Contributor
Summary:
Issues with connecting to US servers (not LA)​
Details:
Heya, I've been having some issues connecting to the US brand of servers, namely:

192.223.30.242:27016 Payload+ US Fast
192.223.26.231:27015 Badwater US

show up as server not responding.

Servers I don't have a problem connecting to:

66.150.188.54:27015 2FORT+ LA
66.150.155.156:27016 UPWARD LA
151.80.218.89:27015 BADWATER EU

I first noticed this started happening in and around the same time that Badwater LA was removed.

Things I've tried in the interim: flushing DNS, tons of router/modem powercycles, etc.

Just wanted to check if this is something I should be asking my ISP about? Seems like some kind of crazy routing issue, but I figured it should have fixed itself by now.​
 
Possibly, thanks for the link, not sure though because it's been going on for me for awhile, but I'll see how things turn out when the new router is installed.
 
The new router crashing meant that everyone got disconnected at he same time, it doesn't mean you get blocked for days.

Please use WinMTR for network problems. Since the servers are filled, it is likely an issue with your ISP.
 
heya, I just called my ISP, because this issue is still going on, not only with Skial, but I cannot connect to any tragicservers either which means I can't play tf2center lobbies at all.

After spending 15 minutes explaining to the tech how to put 192.223.26.231:27015 into a google search, he then told me the game monitor webpage result was blocked by his workplace router :|

Had him get ahold of the research department and call me back. Called me back saying "sorry but we don't support the issue you are having where you can't connect to servers in a geographical area". Argued with him a bit that, in fact, researching downed backbones and traffic routing problems is their job, and he said he'd investigate and call me back. Not thinking I'm going to get much assistance from Shaw support from this one.

edit: getting a winMTR report for you now, one sec.

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| 64.59.150.181 - 0 | 13 | 13 | 10 | 13 | 30 | 10 |
| 66.163.73.113 - 0 | 13 | 13 | 20 | 26 | 50 | 30 |
| rc3sc-be10.wp.shawcable.net - 0 | 13 | 13 | 40 | 43 | 50 | 40 |
| rc4ec-hge0-9-0-1.il.shawcable.net - 0 | 13 | 13 | 50 | 58 | 70 | 60 |
| equinix-ix.ord1.us.voxel.net - 0 | 13 | 13 | 50 | 62 | 80 | 60 |
| internap.ord1.us.voxel.net - 0 | 13 | 13 | 50 | 58 | 70 | 60 |
| border5.po2-bbnet2.chg.pnap.net - 0 | 13 | 13 | 50 | 63 | 80 | 50 |
|inap-b5.e3.router.chicago.nfoservers.com - 0 | 13 | 12 | 50 | 58 | 70 | 60 |
| ch4.skial.com - 0 | 12 | 12 | 50 | 58 | 70 | 60 |
|________________________________________________|______|______|______|______|______|______|
WinMTR - 0.8. Copyleft @2000-2002 Vasile Laurentiu Stanimir ( stanimir@cr.nivis.com )
 
So the next day "coincidentally" my internet connection, after a month+ of not working, can suddenly make connections to the skial us and tragicservers. I'm guessing the isp made some blunder on their end and didn't want to own up to it, but you can close this as resolved, thanks for the assistance bottiger.
 
You must log in or register to reply here.
Top Bottom
Back