dslreports logo
 
    All Forums Hot Topics Gallery
spc
Search similar:


uniqs
3810

SDL L3Tech
join:2011-06-07
Tyler, TX

SDL L3Tech to dd31879

Member

to dd31879

Re: Suddenlink Internet Issues

I believe that most recent outage for you was an actual node outage. I see that neighboring modems stopped responding at the same time and all came back online at the same time.

As far as your PingPlotter traces, it does not show much packet-loss. Most of your comments say 33% when PingPlotter showed 0 packet-loss for the majority of them and a few that showed 1-2 packets lost. Where are you seeing 33%?
dd31879
join:2013-02-27
Boyce, LA

dd31879

Member

Click for full size
well i looked at it in like 6hr view mode when i put the comment arrows down so if they are a bit off when you zoom down farther then im sorry.

here is a picture of what im seeing right now.
a bunch of little red marks for sure and hop 8 even spikes up to 858ms

SDL L3Tech
join:2011-06-07
Tyler, TX

SDL L3Tech to dd31879

Member

to dd31879
The timeout between 6:22 and 6:23 and the timeout between 6:26p and 6:27p are the only indications of a problem in your PP trace. Note how it affects the destination hop and you can follow it back to hop 2.

If you see packet-loss/latency mid-trace (like hop 8) but that problem does not affect the destination (hop 16), then the mid-trace problem is not an actual problem. It likely is just limiting responses to low priority packets to it, but not through it.

I see some intermittent FEC errors on the upstream of your node that are causing your packet-loss. I'll gather information and send it to the local techs to further troubleshoot the RF plant.
dd31879
join:2013-02-27
Boyce, LA

dd31879

Member

something odd looks like it is happening. of course odd could just be my point of view...

the route looks like it keeps changing and to me it looks like there is packet loss trying to path to suddenlink.com. is something going on?

also, i may be wrong.. but i dont think its normal for my modem to say [3]QPSK [3]16QAM.

pathping:
Tracing route to suddenlink.com [69.168.97.113]
over a maximum of 30 hops:
  0  Owner-PC [192.168.0.100]
  1  192.168.0.1
  2  10.238.64.1
  3  173-219-244-32-link.sta.suddenlink.net [173.219.244.32]
  4  173-219-234-52-link.sta.suddenlink.net [173.219.234.52]
  5  173-219-234-215-link.sta.suddenlink.net [173.219.234.215]
  6  173-219-234-212-link.sta.suddenlink.net [173.219.234.212]
  7  173-219-231-116-link.sta.suddenlink.net [173.219.231.116]
  8  173-219-246-186-link.sta.suddenlink.net [173.219.246.186]
  9  ae-20.r01.dllstx04.us.bb.gin.ntt.net [129.250.203.77]
 10  ae-5.r08.dllstx09.us.bb.gin.ntt.net [129.250.3.232]
 11  ae-0.centurylink.dllstx09.us.bb.gin.ntt.net [129.250.8.82]
 12  lwc2-cntr-01.inet.qwest.net [205.171.97.1]
 13     *     63.146.163.67
 14  69.168.97.113
 
Computing statistics for 35 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           Owner-PC [192.168.0.100]
                                0/  10 =  0%   |
  1    0ms     0/  10 =  0%     0/  10 =  0%  192.168.0.1
                                0/  10 =  0%   |
  2    8ms     0/  10 =  0%     0/  10 =  0%  10.238.64.1
                                0/  10 =  0%   |
  3   56ms     0/  10 =  0%     0/  10 =  0%  173-219-244-32-link.sta.suddenlink.net [173.219.244.32]
                                0/  10 =  0%   |
  4   53ms     0/  10 =  0%     0/  10 =  0%  173-219-234-52-link.sta.suddenlink.net [173.219.234.52]
                                0/  10 =  0%   |
  5   58ms     0/  10 =  0%     0/  10 =  0%  173-219-234-215-link.sta.suddenlink.net [173.219.234.215]
                                0/  10 =  0%   |
  6   58ms     0/  10 =  0%     0/  10 =  0%  173-219-234-212-link.sta.suddenlink.net [173.219.234.212]
                                0/  10 =  0%   |
  7   58ms     0/  10 =  0%     0/  10 =  0%  173-219-231-116-link.sta.suddenlink.net [173.219.231.116]
                                0/  10 =  0%   |
  8   69ms     0/  10 =  0%     0/  10 =  0%  173-219-246-186-link.sta.suddenlink.net [173.219.246.186]
                                0/  10 =  0%   |
  9  109ms     0/  10 =  0%     0/  10 =  0%  ae-20.r01.dllstx04.us.bb.gin.ntt.net [129.250.203.77]
                                0/  10 =  0%   |
 10   96ms     0/  10 =  0%     0/  10 =  0%  ae-5.r08.dllstx09.us.bb.gin.ntt.net [129.250.3.232]
                                1/  10 = 10%   |
 11  140ms     2/  10 = 20%     1/  10 = 10%  ae-0.centurylink.dllstx09.us.bb.gin.ntt.net [129.250.8.82]
                                0/  10 =  0%   |
 12  123ms     6/  10 = 60%     5/  10 = 50%  lwc2-cntr-01.inet.qwest.net [205.171.97.1]
                                0/  10 =  0%   |
 13  113ms     1/  10 = 10%     0/  10 =  0%  63.146.163.67
                                3/  10 = 30%   |
 14  126ms     4/  10 = 40%     0/  10 =  0%  69.168.97.113
 
Trace complete.
 
GeorgetownTX
join:2006-11-28
Georgetown, TX

1 edit

GeorgetownTX

Member

The packet loss in the trace you provided is outside SL's network.

Very amusing that SL's own home page, suddenlink.com, is apparently outsourced and hosted on an external network instead of being hosted inside their own network. Even more amusing is to see CenturyLink in the route, which I see as well even though my current route goes through Level3 instead of NTT.

Luckily SL's email servers still do appear to be hosted inside their network, so path to suddenlink.com homepage should not be an issue unless you are browsing their site.

Maybe you should try dslreports.com for PP target as a more reliable destination than suddenlink.com.
dd31879
join:2013-02-27
Boyce, LA

dd31879

Member

said by GeorgetownTX:

Very amusing that SL's own home page, suddenlink.com, is apparently outsourced and hosted on an external network instead of being hosted inside their own network.

said by GeorgetownTX:

Maybe you should try dslreports.com for PP target as a more reliable destination than suddenlink.com

ill try suddenlink.net then. when i do a tracert it looks like it is all suddenlink.
still, im wondering about the upstream modulation saying QPSK when normally it doesnt.

SDL L3Tech
join:2011-06-07
Tyler, TX

SDL L3Tech

Member

Starting early yesterday morning (4/6) the SNR significantly dropped down to unacceptable levels which has also caused an increase in FEC errors and packet-loss.

I have contacted the local techs/engineers to investigate.