Routing Issue apparently, any other suggestions?

[xendrome]

So I have a remote site on Comcast and our main site is on Brighthouse.

 

Last night I started getting dropped pings from our monitoring software, with our IPSEC VPN tunnel to the remote site dropping and reconnecting all night.

 

This morning, I am unable to ping the normally ping responsive IP of the remote Comcast site. The ping fails from the main Brighthouse site, and my personal Brighthouse connection.

 

However I can ping the remote Comcast site from my AT&T LTE connection or a 3rd party outside ping site like http://ping.eu/

 

A tracert from the Main Brighthouse site to the Comcast IP, looks like the connection is dying in Atlanta on one of their backbone connections:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3     8 ms     7 ms     6 ms  ten0-0-0-3.ORLD11-ser2.bhn.net [72.31.195.44]
  4     8 ms    10 ms    10 ms  ten0-15-0-5.orld11-car2.bhn.net [71.44.60.152]
  5    16 ms    21 ms    10 ms  ten0-14-0-0.orld71-car2.bhn.net [97.69.193.150]

  6    13 ms    14 ms    14 ms  72-31-193-191.net.bhntampa.com [72.31.193.191]
  7    14 ms    10 ms    15 ms  10.bu-ether15.orldfljo00w-bcr00.tbone.rr.com [66
.109.6.98]
  8    24 ms    25 ms    27 ms  bu-ether18.atlngamq47w-bcr01.tbone.rr.com [66.10
9.1.72]
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.

A tracert from the Comcast connection to the Main Brighthouse seems to make it back to Central Florida.

  1    <1 ms    <1 ms    <1 ms  172.31.20.1
  2    29 ms    31 ms    20 ms  96.120.22.53
  3    13 ms     9 ms     9 ms  te-1-2-ur01.mtplymouth.fl.lakecnty.comcast.net [
69.139.188.41]
  4    10 ms     9 ms     9 ms  te-1-1-ur01.fruitlandpr.fl.lakecnty.comcast.net
[68.85.210.42]
  5    10 ms     9 ms    11 ms  te-4-4-ar01.sumter.fl.lakecnty.comcast.net [68.8
5.210.50]
  6    21 ms    19 ms    19 ms  te-0-3-0-6-ar03.bonitasprngs.fl.naples.comcast.n
et [68.85.238.93]
  7    23 ms    23 ms    24 ms  pos-1-12-0-0-cr01.miami.fl.ibone.comcast.net [68
.86.89.197]
  8    33 ms    35 ms    31 ms  he-0-10-0-0-cr01.56marietta.ga.ibone.comcast.net
 [68.86.85.5]
  9   100 ms    30 ms    30 ms  be-12-pe03.56marietta.ga.ibone.comcast.net [68.8
6.82.234]
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *       42 ms  bu-ether11.orldfljo00w-bcr00.tbone.rr.com [66.10
9.1.73]
 13    45 ms     *        *     so-0-0-2.ar0.cdp01.tbone.rr.com [66.109.6.99]
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *       44 ms    42 ms  ten0-1-0-0.orld11-ser1.bhn.net [97.69.193.61]
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.

[sc302 Veteran]

Call bright house about the issue let them know what is going on. Not much you can do about it falling out in the middle.

[bnelsonjax]

You don't use tracert to diagnose packet loss, because some routers have ICMP requests turned off, so your traceroute may look like packet loss when in fact, its just the router not responding to the request.

 

Best way to find the issue is to install Pingplotter Pro demo and run several tests at the same time. you want to be testing your local router ip (example 192.168.1.1), you want to test the 1st hop past your router (the 1st hop to the ISP), you can test google.com and some other site such as yahoo.com, you will then be able to visually see any packet loss happening as well as which hop it is happening to, you can then pass this information over to your ISP.