new ISP and possible packet loss

moriz

moriz

??ber t??k-n??sh'??n

Join Date: Jan 2006

Canada

R/

i've just changed my ISP, and i've been getting some connection problems. they are usually nothing serious, but with my ping fluctuating between 100 and 330, i suspect there are possible packet loss problems. i did a trace with GW's built in diagnostics, and here's what i've found:

Code:
==============================================================================
= Tracing network paths
==============================================================================
*--> pathping -w 500 -q 3 -4 222.231.14.228 <--*

Tracing route to 222.231.14.228 over a maximum of 30 hops

  0  tehMoriz-PC [192.168.2.2] 
  1  192.168.1.1 
  2  67.55.10.1 
  3  66.49.255.193 
  4  te4-2.mpd01.yyz02.atlas.cogentco.com [38.117.84.25] 
  5     *     te8-2.mpd01.ord01.atlas.cogentco.com [154.54.7.73] 
  6  te7-2.mpd01.mci01.atlas.cogentco.com [154.54.2.189] 
  7  te3-4.mpd01.sfo01.atlas.cogentco.com [154.54.6.165] 
  8  te9-3.mpd01.sjc04.atlas.cogentco.com [154.54.0.170] 
  9  dacom.sjc04.atlas.cogentco.com [154.54.12.114] 
 10  203.255.234.169 
 11     *     203.255.234.221 
 12  210.120.105.46 
 13     *     211.233.55.49 
 14     *     211.233.88.238 
 15  211.174.55.250 
 16     *        *        *     
Computing statistics for 11 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           tehMoriz-PC [192.168.2.2] 
                                0/   3 =  0%   |
  1    2ms     0/   3 =  0%     0/   3 =  0%  192.168.1.1 
                                0/   3 =  0%   |
  2   15ms     0/   3 =  0%     0/   3 =  0%  67.55.10.1 
                                0/   3 =  0%   |
  3   16ms     0/   3 =  0%     0/   3 =  0%  66.49.255.193 
                                0/   3 =  0%   |
  4   16ms     0/   3 =  0%     0/   3 =  0%  te4-2.mpd01.yyz02.atlas.cogentco.com [38.117.84.25] 
                                0/   3 =  0%   |
  5   52ms     0/   3 =  0%     0/   3 =  0%  te8-2.mpd01.ord01.atlas.cogentco.com [154.54.7.73] 
                                0/   3 =  0%   |
  6   77ms     0/   3 =  0%     0/   3 =  0%  te7-2.mpd01.mci01.atlas.cogentco.com [154.54.2.189] 
                                0/   3 =  0%   |
  7  107ms     1/   3 = 33%     1/   3 = 33%  te3-4.mpd01.sfo01.atlas.cogentco.com [154.54.6.165] 
                                0/   3 =  0%   |
  8   99ms     0/   3 =  0%     0/   3 =  0%  te9-3.mpd01.sjc04.atlas.cogentco.com [154.54.0.170] 
                                0/   3 =  0%   |
  9  109ms     1/   3 = 33%     1/   3 = 33%  dacom.sjc04.atlas.cogentco.com [154.54.12.114] 
                                0/   3 =  0%   |
 10   97ms     0/   3 =  0%     0/   3 =  0%  203.255.234.169 
                                1/   3 = 33%   |
 11  ---       3/   3 =100%     2/   3 = 66%  203.255.234.221 
                                0/   3 =  0%   |
 12  214ms     1/   3 = 33%     0/   3 =  0%  210.120.105.46 
                                0/   3 =  0%   |
 13  325ms     2/   3 = 66%     1/   3 = 33%  211.233.55.49 
                                0/   3 =  0%   |
 14  211ms     2/   3 = 66%     1/   3 = 33%  211.233.88.238 
                                0/   3 =  0%   |
 15  268ms     1/   3 = 33%     0/   3 =  0%  211.174.55.250 

Trace complete.
*--> pathping -w 500 -q 3 -4 206.127.145.228 <--*

Tracing route to 206-127-145-228.plaync.com [206.127.145.228]
over a maximum of 30 hops:
  0  tehMoriz-PC [192.168.2.2] 
  1  192.168.1.1 
  2     *     67.55.10.1 
  3  66.49.255.193 
  4     *        *        *     
Computing statistics for 2 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           tehMoriz-PC [192.168.2.2] 
                                0/   3 =  0%   |
  1   32ms     0/   3 =  0%     0/   3 =  0%  192.168.1.1 
                                1/   3 = 33%   |
  2   83ms     1/   3 = 33%     0/   3 =  0%  67.55.10.1 
                                0/   3 =  0%   |
  3   15ms     1/   3 = 33%     0/   3 =  0%  66.49.255.193 

Trace complete.
*--> pathping -w 500 -q 3 -4 216.107.246.36 <--*

Tracing route to 216-107-246-36.plaync.com [216.107.246.36]
over a maximum of 30 hops:
  0  tehMoriz-PC [192.168.2.2] 
  1  192.168.1.1 
  2  67.55.10.1 
  3  66.49.255.193 
  4  te4-2.mpd01.yyz02.atlas.cogentco.com [38.117.84.25] 
  5  te3-3.mpd01.ord01.atlas.cogentco.com [154.54.2.161] 
  6  te8-2.mpd01.ord03.atlas.cogentco.com [154.54.25.66] 
  7  btn.ord03.atlas.cogentco.com [154.54.10.58] 
  8  p5-15-c0-ncla-pub.plaync.net [208.251.113.186] 
  9  216-107-255-70.plaync.com [216.107.255.70] 
 10     *     216-107-246-36.plaync.com [216.107.246.36] 

Computing statistics for 7 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           tehMoriz-PC [192.168.2.2] 
                                0/   3 =  0%   |
  1   15ms     0/   3 =  0%     0/   3 =  0%  192.168.1.1 
                                0/   3 =  0%   |
  2   25ms     0/   3 =  0%     0/   3 =  0%  67.55.10.1 
                                0/   3 =  0%   |
  3   21ms     0/   3 =  0%     0/   3 =  0%  66.49.255.193 
                                0/   3 =  0%   |
  4   55ms     1/   3 = 33%     1/   3 = 33%  te4-2.mpd01.yyz02.atlas.cogentco.com [38.117.84.25] 
                                0/   3 =  0%   |
  5   60ms     1/   3 = 33%     1/   3 = 33%  te3-3.mpd01.ord01.atlas.cogentco.com [154.54.2.161] 
                                0/   3 =  0%   |
  6   59ms     1/   3 = 33%     1/   3 = 33%  te8-2.mpd01.ord03.atlas.cogentco.com [154.54.25.66] 
                                0/   3 =  0%   |
  7   55ms     0/   3 =  0%     0/   3 =  0%  btn.ord03.atlas.cogentco.com [154.54.10.58] 
                                1/   3 = 33%   |
  8  ---       3/   3 =100%     2/   3 = 66%  p5-15-c0-ncla-pub.plaync.net [208.251.113.186] 
                                0/   3 =  0%   |
  9  ---       3/   3 =100%     2/   3 = 66%  216-107-255-70.plaync.com [216.107.255.70] 
                                0/   3 =  0%   |
 10   85ms     1/   3 = 33%     0/   3 =  0%  216-107-246-36.plaync.com [216.107.246.36] 

Trace complete.
Completed in 106.53 seconds
there seems to be some packet loss occurring, but since i know next to nothing about internet connections and routing, i'll ask anyone who can make proper sense of that to help me. is it GW's problem, or really packet loss from my ISP?

Tarun

Tarun

Technician's Corner Moderator

Join Date: Jan 2006

The TARDIS

http://www.lunarsoft.net/ http://forums.lunarsoft.net/

You'll need to contact your ISP because there are losses occurring at their level.

See:
7 107ms 1/ 3 = 33% 1/ 3 = 33% te3-4.mpd01.sfo01.atlas.cogentco.com [154.54.6.165]

Chthon

Grotto Attendant

Join Date: Apr 2007

Looks like the problem is with cogentco. I'd have to do some lookups for the physical locations of those IP's to be sure, but it looks like they're not routing you properly.

If you really want to get a better picture of what's going on, try the trial version of pingplotter (it's shareware, so you can continue to use it (with nag screens) after the trial expires).


Edit: Hang on, I may have to take that back:
Quote:
1 32ms 0/ 3 = 0% 0/ 3 = 0% 192.168.1.1
1/ 3 = 33% |
2 83ms 1/ 3 = 33% 0/ 3 = 0% 67.55.10.1
Could you run some more tests looking at this first hop here? You should never be getting something this bad right out of the gate. This makes me suspicious that the problem could be your immediate ISP connection. You wouldn't happen to be on a college network, would you?

moriz

moriz

??ber t??k-n??sh'??n

Join Date: Jan 2006

Canada

R/

this is my home network. i can try running diagnostics with my router disconnected, and modem connected directly to my computer.

my connection is DSL, provided by Acanac. the modem they sent me has the connection info already built in, which is somewhat awkward to set up with a router.