Problems reaching various sites/services on internet from DSL Service

[ddt102]

Issue:  We have problems accessing certain sites/services.  I have done extensive testing
and it seems to be a routing problems on the internet.  It would seem that there the
immediate network I am connected to is having advertising problems and the network path
is failing.  My testing is using the Verizon DSL service vs my tethered iPhone via AT&T.

Everything worked before yesterday afternoon and now we are having problems with:
   - Netflix Video streaming (agmoviecontrol.netflix.com - not website) however www.netflix.com works
   - Dishnet Sling streaming
   - Site that is used to install Microsoft Silverlight
   - DSL Extremes' online chat service

   - my.ebay.com  (however www.ebay.com works)

-Netflix detail
  We can access www.netflix.com, however the video streaming part does not work.  I spoke
to netflix technician and they said I need access to server agmoviecontrol.netflix.com. 
I performed ping and tracert's to this and it failed from my DSL internet service.  I
then testing this by disconnecting my laptop from DSL and switching to my iPhone tether
(AT&T) and it worked.

I really appreciate any help
Best regards,
Don Thompson
fyi .. I am the Regional IT Director at IDS Scheer Americas

--Tracert using DSL Extreme
C:\>tracert 208.75.76.32

Tracing route to agmoviecontrol.netflix.com [208.75.76.32]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  DD-WRT.10HILLSIDE.COM [192.168.0.254]
  2    26 ms    26 ms    26 ms  10.7.35.1
  3    27 ms    29 ms    27 ms  so-0-2-3-0.PHIL-CORE-RTR1.verizon-gni.net [130.8
1.13.153]
  4    28 ms    27 ms    33 ms  so-7-2-0-0.PHIL-BB-RTR1.verizon-gni.net [130.81.
20.136]
  5    40 ms    37 ms    30 ms  0.xe-3-0-1.XL3.IAD8.ALTER.NET [152.63.3.61]
  6    86 ms    33 ms    32 ms  TenGigE0-6-4-0.GW7.IAD8.ALTER.NET [152.63.37.82]

  7    39 ms    33 ms    40 ms  limelight.customer.alter.net [152.179.50.82]
  8    33 ms    32 ms    33 ms  netflix.tge4-2.fr3.iad.llnw.net [69.28.157.14]
  9     *        *        *     Request timed out.
 10   106 ms   102 ms   103 ms  xe-2-2-0-954.jnrt-edge01.prod1.netflix.com [69.5
3.225.26]
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14  ^C

Tracert / ping using iPhone AT&T tether 3G connection
C:\>tracert 208.75.76.32

Tracing route to agmoviecontrol.netflix.com [208.75.76.32]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  172.20.10.1
  2   500 ms   580 ms   580 ms  172.26.236.2
  3   636 ms   928 ms   629 ms  172.18.202.106
  4   518 ms   720 ms   609 ms  172.18.203.209
  5   523 ms   619 ms   589 ms  172.18.203.85
  6   467 ms   570 ms   859 ms  172.18.213.1
  7   506 ms   650 ms   649 ms  12.88.97.9
  8   561 ms   629 ms   679 ms  cr1.attga.ip.att.net [12.123.22.6]
  9   502 ms   710 ms   969 ms  attga04jt.ip.att.net [12.122.84.149]
 10   658 ms   871 ms   618 ms  attga04jt.ip.att.net [12.122.84.149]
 11   537 ms   701 ms   818 ms  vlan52.csw2.Atlanta2.Level3.net [4.69.150.126
 12   507 ms   699 ms   599 ms  vlan52.csw2.Atlanta2.Level3.net [4.69.150.126
 13   483 ms   610 ms   959 ms  ae-71-71.ebr1.Atlanta2.Level3.net [4.69.148.2
 14   643 ms   619 ms   640 ms  ae-8-8.ebr1.Washington1.Level3.net [4.69.143.]
 15   665 ms   599 ms   679 ms  ae-71-71.csw2.Washington1.Level3.net [4.69.1334]
 16   498 ms   749 ms   639 ms  ae-71-71.csw2.Washington1.Level3.net [4.69.1334]
 17   528 ms   649 ms   739 ms  COTENDO-INC.edge3.Washington4.Level3.net [4.516.30]
 18   587 ms   589 ms   910 ms  COTENDO-INC.edge3.Washington4.Level3.net [4.516.30]
 19  1235 ms   999 ms   649 ms  xe-0-0-0-100.jnrt-edge01.sv1.netflix.com [69.230.213]
 20   594 ms   659 ms   689 ms  xe-2-2-0-954.jnrt-edge01.prod1.netflix.com [63.225.26]
 21   588 ms   629 ms   709 ms  xe-2-2-0-954.jnrt-edge01.prod1.netflix.com [63.225.26]
 22   539 ms   680 ms   729 ms  agmoviecontrol.netflix.com [208.75.76.32]

C:\>ping 208.75.76.32

Pinging 208.75.76.32 with 32 bytes of data:

Reply from 208.75.76.32: bytes=32 time=2433ms TTL=237
Reply from 208.75.76.32: bytes=32 time=238ms TTL=237
Reply from 208.75.76.32: bytes=32 time=243ms TTL=237

Ping statistics for 208.75.76.32:
    Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 238ms, Maximum = 2433ms, Average = 971ms

[smith6612]

There have been a few reports coming in over at DSLReports of routing issues that Verizon is having. A few people there have done trace-routes to some sites they are unable to visit and are seeing similar traces. Some of them involved reverse trace routes, which failed shortly after getting into to the Verizon/Alter.net backbone. Right now it seems to be an issue with some routing tables based on speculation.