|
psyq
Anon
2014-Aug-12 2:01 pm
[BC] Weird connection issueI've been trying for over an hour to track down the reason I can't connect to coastcapitalsavings.com on my Telus connection.
I'm at work on a different provider and it's working fine. For some odd reason I can't work out the problem. Doesn't seen to be DNS related as I've changed that around a few times and rebooted all my hardware. I'm post this over the same connection.
any ideas? anyone else have issues resolving coastcapitalsavings.com? |
|
Gardener Premium Member join:2006-10-19 Burnaby, BC ·TELUS
|
Gardener
Premium Member
2014-Aug-12 2:35 pm
Not good:
[C:\Program Files\JPSoft\TCMD16x64]ping www.coastcapitalsavings.com
Pinging www.coastcapitalsavings.com [208.69.252.179] with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out.
Ping statistics for 208.69.252.179: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
I'm using opendns, not Telus DNS. |
|
|
psyq
Anon
2014-Aug-12 2:37 pm
Yeah, I'm using OpenDNS too, but I also tested Google DNS with the same results. |
|
psyq |
psyq
Anon
2014-Aug-12 2:39 pm
I ran a DSL line test just to see what the results would be. I'm really out of ideas on tracking this down on my end. This looks pretty bad to me. Think Telus is having some system issues? » /pingt ··· 47?r=791 |
|
|
to psyq
no problem for me and using Google DNS. » www.coastcapitalsavings. ··· ersonal/208.69.252.179 not pingable Maybe on the route that is the problem Navigata.net? After 3 of them, it then goes to unresolved on a tracert. |
|
|
psyq
Anon
2014-Aug-12 3:59 pm
I did notice the route issue with navigata.net
traceroute to coastcapitalsavings.com (208.69.252.179), 30 hops max, 38 byte pac kets 1 10.240.48.1 (10.240.48.1) 10.005 ms 8.151 ms 9.513 ms 2 209.121.72.206 (209.121.72.206) 10.279 ms 8.463 ms 9.164 ms 3 173.182.214.132 (173.182.214.132) 9.685 ms 7.934 ms 173.182.214.134 (173. 182.214.134) 9.119 ms 4 * * 154.11.22.114 (154.11.22.114) 12.711 ms 5 STTLWAWBCI01.bb.telus.com (75.154.217.106) 7.033 ms STTLWAWBCI01.bb.telus. com (75.154.217.108) 8.286 ms STTLWAWBCI01.bb.telus.com (75.154.217.106) 8.63 6 ms 6 96.1.252.141 (96.1.252.141) 8.799 ms 21.199 ms 13.326 ms 7 10ge1-1.core1.yvr1.he.net (184.105.222.2) 14.390 ms 14.167 ms 17.214 ms 8 navigata-communications-2009-inc.10gigabitethernet1-4.core1.yvr1.he.net (216 .218.192.198) 12.893 ms 6.991 ms 8.791 ms 9 * Vlan2.vsb2.navigata.net (204.244.12.14) 11.347 ms * 10 * * * 11 * * * 12 * * *.... etc etc
Looks like they've fixed it; I can resolve the address now. That route was messed up for almost 6 hours. That's like a 100 years in Internet terms.
Thanks for the help guys! |
|
|
to psyq
» www.nux.ro/archive/2014/ ··· one.htmlPerhaps has something to do with it. Lot of Cisco routers around the world are losing their minds |
|
kevinds Premium Member join:2003-05-01 Calgary, AB |
kevinds
Premium Member
2014-Aug-13 3:05 am
An actual news article, may be easier for most to understand » www.zdnet.com/internet-h ··· 0032566/ |
|