Forum Discussion

Freezezzy's avatar
Freezezzy
New Contributor
4 years ago

Packet Loss and latency in Phoenix

For the past couple of days, I've been experiencing packet loss and latency whenever I try to play any sort of online game. I've also experienced some difficulty in streaming via Netflix or YouTube, etc.

My current setup includes the following:

MODEM - Motorola Surfboard SB5120 (provided by Cox)

ROUTER - Netgear N300 Wireless Router WNR2000 v3

At most, I have 2 devices connected to it at any time, and have had little trouble with it over the years.

Upon testing via Traceroute and Pathping, I received the following results:

NETWORK DIAGNOSTIC TEST LOG
----------------------------
Path Ping (pathping.exe)
Trace Route (tracert.exe)
============================

** [ July 7, 2020 - 1:34 PM ] **

(Traceroute)

Tracing route to cox.net [45.60.45.167]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  192.168.1.1
  2     8 ms    13 ms    32 ms  10.112.56.1
  3    10 ms    65 ms    31 ms  100.127.73.12
  4    23 ms     9 ms    13 ms  100.120.100.0
  5     *        *       29 ms  lag-103.bear2.Phoenix1.Level3.net [4.14.52.225]

  6    20 ms    18 ms    20 ms  4.69.215.133
  7     *       20 ms    20 ms  4.7.26.34
  8    26 ms    59 ms    19 ms  45.60.45.167

Trace complete.
----------------------------------------------------------------------------------------------------

** [ July 7, 2020 - 1:38 PM ] **

(Traceroute)

Tracing route to cox.net [45.60.45.167]
over a maximum of 30 hops:

  1     1 ms     1 ms     3 ms  192.168.1.1
  2     8 ms     8 ms     7 ms  10.112.56.1
  3     *       15 ms    40 ms  100.127.73.12
  4     7 ms    11 ms    10 ms  100.120.100.0
  5     *       27 ms    25 ms  lag-103.bear2.Phoenix1.Level3.net [4.14.52.225]

  6    21 ms    32 ms    34 ms  4.69.215.133
  7  2053 ms    30 ms    30 ms  4.7.26.34
  8    19 ms    29 ms    24 ms  45.60.45.167

Trace complete.
----------------------------------------------------------------------------------------------------

** [ July 7, 2020 - 1:42 PM ] **

(Traceroute)

Tracing route to cox.net [45.60.106.167]
over a maximum of 30 hops:

  1     1 ms     1 ms     5 ms  192.168.1.1
  2    15 ms    10 ms    36 ms  10.112.56.1
  3     *       10 ms     8 ms  100.127.73.12
  4     9 ms     9 ms     *     100.120.100.0
  5     *       11 ms    10 ms  lag-103.bear2.Phoenix1.Level3.net [4.14.52.225]

  6    80 ms    67 ms    67 ms  ae-1-9.bar1.Toronto1.Level3.net [4.69.151.109]
  7     *       66 ms    89 ms  4.16.52.155
  8    72 ms    70 ms    66 ms  45.60.106.167

Trace complete.
----------------------------------------------------------------------------------------------------

** [ July 7, 2020 - 2:06 PM ] **

(Traceroute)

Tracing route to cox.net [45.60.106.167]
over a maximum of 30 hops:

  1     1 ms     1 ms     5 ms  192.168.1.1
  2    15 ms    10 ms    36 ms  10.112.56.1
  3     *       10 ms     8 ms  100.127.73.12
  4     9 ms     9 ms     *     100.120.100.0
  5     *       11 ms    10 ms  lag-103.bear2.Phoenix1.Level3.net [4.14.52.225]

  6    80 ms    67 ms    67 ms  ae-1-9.bar1.Toronto1.Level3.net [4.69.151.109]
  7     *       66 ms    89 ms  4.16.52.155
  8    72 ms    70 ms    66 ms  45.60.106.167

Trace complete.
----------------------------------------------------------------------------------------------------

** [ July 7, 2020 - 2:07 PM ] **

(Pathping)

Tracing route to cox.net [45.60.45.167]
over a maximum of 30 hops:
  0  Teradrive [192.168.1.6]
  1  192.168.1.1
  2  10.112.56.1
  3  100.127.73.12
  4     *     100.120.100.0
  5     *     lag-103.bear2.Phoenix1.Level3.net [4.14.52.225]
  6     *        *        *
Computing statistics for 125 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           Teradrive [192.168.1.6]
                                0/ 100 =  0%   |
  1    3ms     0/ 100 =  0%     0/ 100 =  0%  192.168.1.1
                               13/ 100 = 13%   |
  2   30ms    17/ 100 = 17%     4/ 100 =  4%  10.112.56.1
                                0/ 100 =  0%   |
  3   27ms    13/ 100 = 13%     0/ 100 =  0%  100.127.73.12
                                5/ 100 =  5%   |
  4   32ms    18/ 100 = 18%     0/ 100 =  0%  100.120.100.0
                               82/ 100 = 82%   |
  5  ---     100/ 100 =100%     0/ 100 =  0%  lag-103.bear2.Phoenix1.Level3.net [4.14.52.225]

Trace complete.
----------------------------------------------------------------------------------------------------

** [ July 7, 2020 - 2:18 PM ] **

(Pathping)

Tracing route to cox.net [45.60.106.167]
over a maximum of 30 hops:
  0  Teradrive [192.168.1.6]
  1  192.168.1.1
  2  10.112.56.1
  3  100.127.73.12
  4  100.120.100.0
  5  lag-103.bear2.Phoenix1.Level3.net [4.14.52.225]
  6  ae-1-9.bar1.Toronto1.Level3.net [4.69.151.109]
  7  4.16.52.155
  8  45.60.106.167

Computing statistics for 200 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           Teradrive [192.168.1.6]
                                0/ 100 =  0%   |
  1    6ms     0/ 100 =  0%     0/ 100 =  0%  192.168.1.1
                               38/ 100 = 38%   |
  2  105ms    38/ 100 = 38%     0/ 100 =  0%  10.112.56.1
                                2/ 100 =  2%   |
  3   96ms    41/ 100 = 41%     1/ 100 =  1%  100.127.73.12
                                0/ 100 =  0%   |
  4   85ms    46/ 100 = 46%     6/ 100 =  6%  100.120.100.0
                                0/ 100 =  0%   |
  5   74ms    40/ 100 = 40%     0/ 100 =  0%  lag-103.bear2.Phoenix1.Level3.net [4.14.52.225]
                                0/ 100 =  0%   |
  6  ---     100/ 100 =100%    60/ 100 = 60%  ae-1-9.bar1.Toronto1.Level3.net [4.69.151.109]
                                0/ 100 =  0%   |
  7  164ms    43/ 100 = 43%     3/ 100 =  3%  4.16.52.155
                                0/ 100 =  0%   |
  8  132ms    40/ 100 = 40%     0/ 100 =  0%  45.60.106.167

Trace complete.
----------------------------------------------------------------------------------------------------

Testing it with WinMTR yielded the following result:

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.1.1 -    0 |  502 |  502 |    0 |    5 |  104 |    4 |
|                             10.112.56.1 -   27 |  245 |  180 |    7 |   63 | 4506 |   24 |
|                           100.127.73.12 -   28 |  242 |  176 |    7 |   53 | 4506 |   21 |
|                           100.120.100.0 -   24 |  261 |  200 |    8 |   63 | 4507 |   81 |
|       lag-103.bear2.Phoenix1.Level3.net -   66 |  142 |   49 |    0 |   18 |   98 |   14 |
|         ae-1-9.bar1.Toronto1.Level3.net -   31 |  228 |  158 |    0 |  104 | 1894 |   73 |
|                             4.16.52.155 -   27 |  246 |  180 |    0 |   81 |  582 |   69 |
|                           45.60.106.167 -   35 |  214 |  140 |   63 |   77 |  561 |  111 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Any help would be appreciated.

1 Reply

  • JonathanJ's avatar
    JonathanJ
    Former Moderator
    @Freezezzy

    You mention having an SB5120 modem which is a DOCSIS 2.0 that doesn't allow you to get the full performance. We suggest upgrading to a DOCSIS 3.0 or 3.1 modem that will allow maximum performance. I'm providing a link with Cox compatible modem https://bit.ly/38Gn0ND.

    Jonathan J
    Cox Moderator