100% packet loss at alter.net

[capefarewell]

I am having 100% packet loss at alter.net.

Exactly the same problem as:

http://forums.verizon.com/t5/FiOS-Internet/100-packet-loss-through-152-179-220-125-n-a-GW13-NYC1-ALT...

I need to know if Verizon has fixed their hardware & software, & what I need to do?

[capefarewell]

Synopsis of Tracing a path from Boston to California:

   Hops locally to Major city (Boston)

   Jumps to New York.

    Bounces around in  New  York 6 times (Verizon throttling?)

    At hop #10, exits verizon system (all alter.net entries are Verizon).

Verizon technician said "verizon has no control after hop 5" (right before 100% packet loss @hop 6).

C:\Users\K>tracert  youtube.com

Tracing route to youtube.com [173.194.123.33]
over a maximum of 30 hops:

  1     1 ms     1 ms     3 ms  Wireless_Broadband_Router.home [192.168.1.1]
  2     7 ms     8 ms     9 ms  L100.BSTNMA-VFTTP-95.verizon-gni.net [98.110.194.1]
  3     8 ms    11 ms    13 ms  G0-11-4-5.BSTNMA-LCR-22.verizon-gni.net [100.41.204.123]
  4    55 ms    73 ms     9 ms  ae2-0.BOS-BB-RTR2.verizon-gni.net [130.81.151.76]
  5    19 ms    16 ms    15 ms  0.ae11.XL4.NYC1.ALTER.NET [152.63.20.117]
  6     *        *        *     Request timed out.
  7    15 ms    16 ms    16 ms  3.et-2-0-1.TL2.NYC1.ALTER.NET [140.222.227.34]
  8    18 ms    23 ms    34 ms  TenGigE0-5-2-0.GW8.NYC4.ALTER.NET [152.63.16.125]
  9    16 ms    15 ms    16 ms  google-gw.customer.alter.net [152.179.72.62]
 10    15 ms    21 ms    16 ms  216.239.50.106
 11    19 ms    18 ms    19 ms  209.85.240.113
 12    14 ms    16 ms    19 ms  lga15s47-in-f1.1e100.net [173.194.123.33]

Trace complete.

Pingplotter program reveals 100% packet loss at hop  #6.

Why is hop #6 hidden? 

How do I find  more information about this server?

[eljefe2 · Accepted solution]

That trace route you posted looks completely normal.

Many servers are configured not to respond to ping packets.  I have my FiOS router set to not respond to ping packets.  If you tracert to my WAN IP address it will show 100% packet loss, could not be reached, etc.  Yet all use of the Internet is normal from here.

The bottom line on the tracert you posted is at step 12 the total latency is very low.  That means your ping packets are taking no more than 19 ms worst case, and less than that on average.  There can't be any significant delay happening at step 6.

There's no problem with that routing.

[Hubrisnxs]

that isn't packet loss.  Packets can't regenerate themselves if they are dropped.   They are either dropped or not dropped.

The fact that it passes that router and continues uninterrupted to all the remaining hops shows you that it's not dropped.  That router simply doesn't respond to trace's or pings.  They were programmed not to. 

This is a good website that shows you how to analyze that trace and other trace's properly.

https://www.linode.com/docs/networking/diagnosing-network-issues-with-mtr#analyzing-mtr-reports

[levdog]

@Hubrisnxs using MTR, I'm seeing 100% loss at the 6th hop with alter.net - please advise. Thx.

HOST: levdogMBP.home                   Loss%   Snt   Last   Avg  Best  Wrst StDev

  1.|-- wireless_broadband_router.home          0.0%   100    1.2   1.4   0.9  15.6   1.5

  2.|-- l100.nycmny-vfttp-156.verizon-gni.net   0.0%   100    4.6   5.5   2.4  36.7   5.4

  3.|-- g0-1-3-1.nycmny-lcr-22.verizon-gni.net  0.0%   100    9.0   7.2   4.0  20.4   2.1

  4.|-- ae2-0.ny5030-bb-rtr1.verizon-gni.net    0.0%   100   17.3  15.8   3.6  90.9  20.7

  5.|-- 0.ae13.xl3.nyc1.alter.net               0.0%   100    6.1   6.2   4.4  11.4   0.9

  6.|-- ???                                    100.0   100    0.0   0.0   0.0   0.0   0.0

  7.|-- 3.ae1.xt1.nyc4.alter.net                0.0%   100    5.1  16.9   4.7 144.9  26.2

  8.|-- tengige0-6-4-0.gw8.nyc4.alter.net       0.0%   100   11.2  12.4   4.6  21.5   3.8

  9.|-- google-gw.customer.alter.net            0.0%   100    5.9   6.7   4.5  47.5   4.8

10.|-- 209.85.255.68                           0.0%   100    5.1   8.4   4.6 103.7  11.1

11.|-- 209.85.245.181                          0.0%   100    6.7   7.1   4.9  18.1   1.6

12.|-- lga15s44-in-f8.1e100.net                0.0%   100    7.8   6.3   4.9  13.6   0.9

[smith6612]

100% loss that does not carry onto any further hops means that the router or device at hop 6 is simply programmed to not respond to ICMP or UDP Echo requests. This is usually to save CPU power on the gear for handing other requests.