 bbbc
join:2001-10-02
NorthAmerica
kudos:2
1 edit | [BC] TSI West / Shaw: Can't access Techbargains.comCan someone else see if they can access Techbargains.com on Shaw. Mind you, I'm unable to access it under TSI West Cable aka Shaw. I'm not using TSI's DNS servers, instead UnblockUs'. I can access the site through Wind Mobile and I also get a response from downforeveryoneorjustme.com that everything is peachy. I haven't been able to access Techbargains.com for a while.
Traceroute has started...
traceroute to techbargains.com (204.11.109.167), 64 hops max, 72 byte packets
1 dd-wrt (192.168.1.1) 5.206 ms 1.103 ms 0.901 ms
2 * * *
3 * * 69-172-144-1.cable.teksavvy.com (69.172.144.1) 11.185 ms
4 bdr01.van.cable.teksavvy.com (76.10.191.33) 15.041 ms !N 13.798 ms !N 9.276 ms !N
Ping has started...
PING techbargains.com (204.11.109.167): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
Request timeout for icmp_seq 6
Request timeout for icmp_seq 7
Request timeout for icmp_seq 8
--- techbargains.com ping statistics ---
10 packets transmitted, 0 packets received, 100.0% packet loss
--
Consumerist.com | Consumers Union |
|
|
Pinging techbargains.com [204.11.109.167] with 32 bytes of data:
Reply from 204.11.109.167: bytes=32 time=51ms TTL=241
Reply from 204.11.109.167: bytes=32 time=53ms TTL=241
Reply from 204.11.109.167: bytes=32 time=51ms TTL=241
Reply from 204.11.109.167: bytes=32 time=57ms TTL=241
Ping statistics for 204.11.109.167:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 51ms, Maximum = 57ms, Average = 53ms
Server 2008 R2 doing my DHCP, DNS and forwarders set to google's.
|
|
|
|
1 edit | reply to bbbc
I can access it, loads in IE...
Kind of slow, but it works without issue.
SE Calgary.
Using DNS on 2008r2 - direct queries, not forwarding to another server.
Tracing route to techbargains.com [204.11.109.167]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.5.1
2 * * * Request timed out.
3 12 ms 14 ms 15 ms gw1ct.ek.shawcable.net [64.59.132.205]
4 9 ms 13 ms 29 ms rc2so-tge0-3-0-0.cg.shawcable.net [66.163.71.158]
5 27 ms 23 ms 25 ms rc2wh-tge0-2-1-0.vc.shawcable.net [66.163.77.226]
6 29 ms 30 ms 26 ms 66.163.76.150
7 27 ms 27 ms 29 ms xe-11-0-0.edge1.Seattle3.Level3.net [4.59.232.85]
8 29 ms 28 ms 28 ms ae-31-51.ebr1.seattle1.level3.net [4.69.147.150]
9 44 ms 44 ms 48 ms ae-7-7.ebr2.sanjose1.level3.net [4.69.132.49]
10 57 ms 46 ms 49 ms ae-72-72.csw2.sanjose1.level3.net [4.69.153.22]
11 45 ms 45 ms 52 ms ae-23-70.car3.SanJose1.Level3.net [4.69.152.69]
12 45 ms 45 ms 45 ms splice-comm.car3.sanjose1.level3.net [4.71.112.66]
13 51 ms 51 ms 47 ms 204.11.108.145
14 48 ms 45 ms 66 ms 204.11.109.167
Trace complete.
--
Yes, I am not employed and looking for IT work. Have passport, will travel. |
|
bbbc
join:2001-10-02
NorthAmerica
kudos:2
4 edits | reply to bbbc
Thanks folks. I also am unable to load tmobile.com . I guess I have to pursue this with TSI. I just wanted to make sure it wasn't Shaw related.
--
Consumerist.com | Consumers Union |
|
| reply to bbbc
Tried playing with DNS? |
|
| He is getting it to resolve, so doesn't look like a DNS issue. |
|
| reply to bbbc
Yup, no problem reaching it thru Shaw. |
|
