site Search:


 
    All Forums Hot Topics Gallery






how-to block ads


 
Search Topic:
Share Topic
Posting?
Post a:
Post a:
Links: ·FiOS Map ·Vz FiOS FAQ ·General Fiber Optics ·Vz FiOS Monitors ·Submit a FAQ
AuthorAll Replies

KillABrew

join:2000-12-20
united state

reply to war9200

Re: [Northeast] FiOS/Northern Virginia high latency every night

What it doesn't show is where the latency is happening. Is it on the VZ network or outside the network.

war9200

join:2002-03-30
Ashburn, VA

Good point, I use Comcast as well and I use that my control below, for ALL DNS servers, I use Comcast & Verizon to monitor, only Verizon has problems:

This particular host in question is (but remember, it does not matter which host, ALL hosts are affected across multiple different companies in the US): 207.172.3.8



KillABrew

join:2000-12-20
united state

Good point, but peering could be different between the providers and producing different results.
Example, when I had BrightHouse it would take 7 hops to get to a site vs. 15 on VZ to get to the same site. On VZ I have to route to Miami or Atlanta to get to the Tampa area. BrightHouse kept it in the Tampa area.
I would ping the last hop that I see on the VZ route and compare that to the ping to the far end. That would give you a picture of it is off or on network for VZ.


war9200

join:2002-03-30
Ashburn, VA

Good point also.

Currently I am not affected, but to to see where the loss is occurring at the time I suppose I'd need to check at that time; however, this seems to affect everything so it has to be something (early hop in the chain)..

Comcast:

12. tge8-1.aggr1.lnh.md.rcn.net 0.0% 8 19.9 21.0 19.9 21.9 0.7
13. ns1.dns.rcn.net 0.0% 8 21.9 22.9 20.1 35.8 5.3

64 bytes from tge8-1.aggr1.lnh.md.rcn.net (207.172.15.4): icmp_req=1 ttl=244 time=33.1 ms
64 bytes from tge8-1.aggr1.lnh.md.rcn.net (207.172.15.4): icmp_req=2 ttl=244 time=32.7 ms

                                       Packets               Pings
 Host                                Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. (omitted/privacy)                 0.0%     9   22.7  24.3  15.8  42.1   7.9
 2. (omitted/privacy)                 0.0%     8   45.8  13.9   8.2  45.8  12.9
 3. xe-5-0-0-0-ar02.charlvilleco.va.  0.0%     8   18.3  28.7  13.9 118.7  36.4
 4. pos-1-2-0-0-cr01.ashburn.va.ibon  0.0%     8   20.8  19.6  17.1  21.5   1.7
    pos-1-3-0-0-cr01.ashburn.va.ibone.comcast.net
    be-99-cr01.ashburn.va.ibone.comcast.net
 5. xe-11-3-0.edge2.Washington12.Lev  0.0%     8   18.9  17.9  16.9  19.0   0.8
 6. vlan51.ebr1.Washington12.Level3.  0.0%     8   18.1  21.7  18.1  28.3   3.5
 7. ae-8-8.ebr1.Washington1.Level3.n  0.0%     8   18.8  19.1  18.0  22.1   1.3
 8. ae-71-71.csw2.Washington1.Level3  0.0%     8   18.3  23.3  18.3  38.1   6.5
 9. ae-2-70.edge2.Washington4.Level3  0.0%     8   20.2  25.8  19.4  46.8  11.0
10. RCN-CORPORA.edge2.Washington4.Le  0.0%     8   20.2  20.3  19.4  21.0   0.5
11. tge0-0-0-1.core1.lnh.md.rcn.net   0.0%     8   21.2  23.1  19.9  37.5   5.9
12. tge8-1.aggr1.lnh.md.rcn.net       0.0%     8   20.6  20.9  20.1  22.0   0.6
13. ns1.dns.rcn.net                   0.0%     8   21.9  21.7  19.9  24.7   1.5
 

Verizon:

13. tge7-1.aggr1.lnh.md.rcn.net 0.0% 5 10.9 13.7 10.3 22.9 5.2
14. ns1.dns.rcn.net 0.0% 5 10.1 8.7 7.6 10.1 0.9

64 bytes from tge7-1.aggr1.lnh.md.rcn.net (207.172.15.28): icmp_req=1 ttl=244 time=13.6 ms
64 bytes from tge7-1.aggr1.lnh.md.rcn.net (207.172.15.28): icmp_req=2 ttl=244 time=12.3 ms

                                       Packets               Pings
 Host                                Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. (omitted/privacy)                 0.0%    16    2.5   4.4   1.4  13.1   3.6
 2. (omitted/privacy)                 0.0%    16    4.9   4.5   2.7   6.0   1.0
 3. P13-0-0.CLPPVA-LCR-02.verizon-gn  0.0%    16    7.0   5.5   3.8   7.1   1.0
 4. so-12-0-0-0.RES-BB-RTR1.verizon-  0.0%    16    4.2  12.0   3.5 103.8  24.6
 5. 0.ae2.BR1.IAD8.ALTER.NET          0.0%    16    5.9   6.6   4.3  16.1   2.7
    0.ae2.BR2.IAD8.ALTER.NET
 6. ae16.edge1.washingtondc12.level3  0.0%    16    7.2   6.3   4.6   8.1   1.1
    ae17.edge1.washingtondc12.level3.net
 7. vl-3603-ve-227.ebr2.Washington12  0.0%    16    5.0   8.3   5.0  15.0   3.3
 8. ae-5-5.ebr2.Washington1.Level3.n  0.0%    16    6.2   6.5   5.1   8.3   1.1
 9. ae-92-92.csw4.Washington1.Level3  0.0%    16    7.1  10.2   5.6  17.9   3.7
10. ae-4-90.edge2.Washington4.Level3  0.0%    16    8.2   8.2   5.6  25.1   4.6
11. RCN-CORPORA.edge2.Washington4.Le  0.0%    16    6.8   7.5   6.2   9.4   1.0
12. tge0-1-0-1.core2.lnh.md.rcn.net   0.0%    16    8.9   9.3   7.6  11.0   0.9
13. tge7-1.aggr1.lnh.md.rcn.net       0.0%    16   11.2  10.4   9.0  11.9   0.9
14. ns1.dns.rcn.net                   0.0%    16   10.2   8.7   7.0  10.2   1.1
 

It appears from the traceroutes above they roughly follow the same route except Verizon doesn't go directly to LEVEL3 but ALTER.NET first. Will need to do this at night sometime when the problem starts happening.

war9200

join:2002-03-30
Ashburn, VA

Spoke to Verizon, they said the same thing, I need to call them when the problem is happening so they can look at it.


Tuesday, 21-May 01:11:46 Terms of Use & Privacy | feedback | contact | Hosting by nac.net - DSL,Hosting & Co-lo
over 13.5 years online © 1999-2013 dslreports.com.
Most commented news this week
Hot Topics