[mythtv-users] Zap2it outage?

[kanetse@gmail.com]

On 2/9/06, Anthony Floyd <anthonyfloyd at gmail.com> wrote:
> ...
>  5:  72.51.24.189 (72.51.24.189)                            1.499ms
>  6:  oc48pos5-0.sea-dis-2.peer1.net (216.187.88.226)        5.154ms
>  7:  216.187.88.178 (216.187.88.178)                        6.317ms
>  8:  12.127.70.61 (12.127.70.61)                          asymm 13   5.615ms
>  9:  tbr2-p012502.st6wa.ip.att.net (12.123.203.178)       asymm 20  72.089ms
> 10:  tbr2-cl11.cgcil.ip.att.net (12.122.10.61)            asymm 19  72.412ms
> 11:  gar3-p370.cgcil.ip.att.net (12.123.6.5)              asymm 17  70.112ms
> 12:  mdf1-gsr12-2-pos-7-0.chi1.attens.net (12.122.255.194) asymm 18  74.196ms
> 13:  mdf1-bi8k-1-eth-2-3.chi1.attens.net (63.240.128.190) asymm 19  73.108ms
>
> ... and then timeouts beyond that.
>
> So, I see that the work packets have been routed through *.attens.net
> where the home packets seem to be dropped there.  However, they both
> make it to the same *.att.net routers.
>
> So, what's attens.net?  Well, it seems to be part of AT&T's network.
> Why would my home packets get dropped there?
>
> At least the problem doesn't seem to be my own ISP killing the packets.
>

Don't know if this helps out or not, but I am also in Vancouver, BC on
Shaw.  I have had no problems with my zap2it listings being updated (I
currently have 14 days worth of guide data up to Feb-23).

When I run a traceroute from my home machine, I get soemthing very
similar to what you are seeing, so maybe that's not the problem:

[snip]
 3  rd1bb-ge2-2-2.vc.shawcable.net (64.59.158.194)  30.132 ms  23.069
ms  46.542 ms
 4  rc1bb-pos15-0.vc.shawcable.net (66.163.69.70)  19.585 ms  43.028
ms  15.046 ms
 5  rc1wt-pos2-3.wa.shawcable.net (66.163.77.26)  25.246 ms  18.453 ms
 17.880 ms
 6  ge-6-2.car4.Seattle1.Level3.net (4.79.110.1)  17.842 ms  15.542 ms
 17.995 ms
 7  ge-1-0-0-53.gar1.Seattle1.Level3.net (4.68.105.73)  16.893 ms
ge-1-0-0-55.gar1.Seattle1.Level3.net (4.68.105.137)  15.359 ms
ge-2-0-0-56.gar1.Seattle1.Level3.net (4.68.105.169)  14.534 ms
 8  att-level3-oc48.Seattle1.Level3.net (4.68.127.110)  14.288 ms 
14.601 ms  13.691 ms
 9  12.122.84.38 (12.122.84.38)  66.518 ms  66.519 ms  67.324 ms
     MPLS Label=30927 CoS=0 TTL=1 S=1
10  tbr2-cl11.cgcil.ip.att.net (12.122.10.61)  66.325 ms  65.912 ms  66.527 ms
     MPLS Label=32560 CoS=0 TTL=1 S=1
11  gar3-p370.cgcil.ip.att.net (12.123.6.5)  65.824 ms  64.277 ms  66.615 ms
12  mdf1-gsr12-2-pos-7-0.chi1.attens.net (12.122.255.194)  72.245 ms 
71.755 ms  72.267 ms
13  mdf1-bi8k-1-eth-2-1.chi1.attens.net (63.240.128.137)  70.435 ms 
80.435 ms  78.127 ms
14  * * *


I am able to access the www.zap2it.com and labs.zap2it.com website fine.

Kane