Bonka
join:2002-12-05
Tamaqua, PA | SECV internet issues Since Wednesday I've been experiencing extremely high packet loss of 80%+ somewhat sporadically. It started some time after 6pm on Wednesday and continued through the night and Thursday morning. I talked to someone at the cable company Thursday morning and was supposed to call back if I had any further issues since it was alright at the time. Of course I had no issues until after 5pm when they close, again for the entire night until about 7am Friday. I left them a message and they sent someone out Friday afternoon to check the line. He said he fixed something local before he came to my house since someone else was having issues and ran tests for a while here and it looked ok. It looked ok for me too with my traceroutes/pings, until just before 6pm when it was running at the extremely high packet loss again. Now I'm stuck the entire weekend not being able to do anything that requires a constant connection as I don't know when it's going to go out next.
There is one major thing to go along with this, being that on Monday I called and got my SB6121 mac address put in and started using that over an Arris rental. All was fine until Wednesday evening, a little over 2 days after swapping. I knew I should have had them swap me back to the Arris today before they were closed for the weekend.
I have no idea if the modem could be causing this. I have spurts of 10-30 minutes where the packet loss is so high I'm unable to do anything, and then can be ok for probably an average of about 30 to 40 minutes. During the packet loss, the modem gives me T3 timeouts from no ranging response.
I'm also confused as to why it's happening between the hours of about 5pm to apparently 7am (or later) but is alright during the mid day hours. If it was a peak traffic problem, I wouldn't be seeing the packet loss at 4am, yet I am.
I am going to attempt to see if my cousin who lives nearby is having issues at the same time over the weekend, which would eliminate the modem as being the issue. Sadly the cable company is going to be of no use. Not only do I have to wait until Monday, but they don't work during the hours these problems are occurring, so I'm not sure how they're going to pinpoint the problem when they run tests during the day when the issues are not apparent.
Edit: I forgot to mention that at no point do any lights on the modem go out, and it doesn't reboot from T4 timeouts very often. The line stats also look ok when the problem is happening. |
|
 JeepMattC'mon the UPremium
join:2001-12-28
Wilmington, DE
kudos:2 | Bonka-
Next time it happens, post some trace routes. Would be curious to see where the PL is originating from.
--
"ONE team - ONE city - ONE dream!!" |
|
| reply to Bonka
I'm off SECV in birdsboro, ptd.net 12/1 plan. 4 downstream / 3 upstream bonded on a Moto 6120.
Noticed Friday night my xbox dashboard UI running REALLY SLOW. Was also having trouble calling up YouTube videos and VEVO.
Then I tried speedtest on my wifi through iphone. Was getting 0.7mbps down! When I disabled wifi and went out AT&T 4G, the speed was much better!
Signals were great. The problem resolved itself the next day.
How are your speeds now? |
|
Bonka
join:2002-12-05
Tamaqua, PA
2 edits | I'm running out of Mahanoy City, since I didn't mention that before. After having 40 minutes of 80%+ packet loss on Friday from about 5:40pm to 6:20pm, I didn't have any major issues until about 5:48pm today (Monday) and am currently experiencing 20%+ packet loss. I was running ping tests for this one to send to the cable company since that's easier to look at than the trace routes I had running with over 6000 responses to each hop saved in a text file.
This is what I had running for a few hours until a little after my problems started today. Leaving the individual responses out, but I'll also post a short example of what it would look like. Delay between attempts was 2000ms.
1. 192.168.1.1 [E1200]
2. 75.97.32.1 [75.97.32.1.res-cmts.sebh.ptd.net]
3. 207.44.120.61 [gateway-t3-2-brhblocal1.brh.ptd.net]
4. 204.186.48.102 [www2.ptd.net]
1. IP address: 192.168.1.1
Host name: E1200
Sent: 5943
Received: 5943
Lost: 0
Loss rate: 0 %
Min. time: 22 ms
Max. time: 143 ms
Avg. time: 43 ms
2. IP address: 75.97.32.1
Host name: 75.97.32.1.res-cmts.sebh.ptd.net
Sent: 5895
Received: 5641
Lost: 254
Loss rate: 4 %
Min. time: 30 ms
Max. time: 952 ms
Avg. time: 67 ms
3. IP address: 207.44.120.61
Host name: gateway-t3-2-brhblocal1.brh.ptd.net
Sent: 5927
Received: 5827
Lost: 100
Loss rate: 1 %
Min. time: 29 ms
Max. time: 287 ms
Avg. time: 54 ms
4. IP address: 204.186.48.102
Host name: www2.ptd.net
Sent: 5953
Received: 5847
Lost: 106
Loss rate: 1 %
Min. time: 23 ms
Max. time: 224 ms
Avg. time: 41 ms
6048. 13.02.18 18:11:09 Timeout
6049. 13.02.18 18:11:11 Timeout
6050. 13.02.18 18:11:13 Timeout
6051. 13.02.18 18:11:14 Reply from [204.186.48.102] Bytes = 32 TTL = 61 Time = 29 ms
6052. 13.02.18 18:11:16 Reply from [204.186.48.102] Bytes = 32 TTL = 61 Time = 28 ms
6053. 13.02.18 18:11:18 Reply from [204.186.48.102] Bytes = 32 TTL = 61 Time = 29 ms
6054. 13.02.18 18:11:20 Reply from [204.186.48.102] Bytes = 32 TTL = 61 Time = 29 ms
6055. 13.02.18 18:11:22 Reply from [204.186.48.102] Bytes = 32 TTL = 61 Time = 27 ms
6056. 13.02.18 18:11:25 Timeout
6057. 13.02.18 18:11:27 Timeout
6058. 13.02.18 18:11:29 Reply from [204.186.48.102] Bytes = 32 TTL = 61 Time = 29 ms
6059. 13.02.18 18:11:31 Timeout
6060. 13.02.18 18:11:33 Reply from [204.186.48.102] Bytes = 32 TTL = 61 Time = 29 ms
6061. 13.02.18 18:11:35 Reply from [204.186.48.102] Bytes = 32 TTL = 61 Time = 28 ms
6062. 13.02.18 18:11:37 Reply from [204.186.48.102] Bytes = 32 TTL = 61 Time = 28 ms
6063. 13.02.18 18:11:39 Reply from [204.186.48.102] Bytes = 32 TTL = 61 Time = 42 ms
6064. 13.02.18 18:11:41 Timeout
6065. 13.02.18 18:11:43 Timeout
6066. 13.02.18 18:11:45 Reply from [204.186.48.102] Bytes = 32 TTL = 61 Time = 37 ms
6067. 13.02.18 18:11:47 Reply from [204.186.48.102] Bytes = 32 TTL = 61 Time = 58 ms
6068. 13.02.18 18:11:49 Reply from [204.186.48.102] Bytes = 32 TTL = 61 Time = 37 ms
6069. 13.02.18 18:11:51 Reply from [204.186.48.102] Bytes = 32 TTL = 61 Time = 29 ms
6070. 13.02.18 18:11:53 Reply from [204.186.48.102] Bytes = 32 TTL = 61 Time = 29 ms
6071. 13.02.18 18:11:55 Reply from [204.186.48.102] Bytes = 32 TTL = 61 Time = 46 ms
6072. 13.02.18 18:11:58 Timeout
6073. 13.02.18 18:12:00 Timeout
6074. 13.02.18 18:12:01 Reply from [204.186.48.102] Bytes = 32 TTL = 61 Time = 28 ms
6075. 13.02.18 18:12:03 Reply from [204.186.48.102] Bytes = 32 TTL = 61 Time = 28 ms
6076. 13.02.18 18:12:05 Reply from [204.186.48.102] Bytes = 32 TTL = 61 Time = 29 ms
6077. 13.02.18 18:12:08 Reply from [204.186.48.102] Bytes = 32 TTL = 61 Time = 29 ms
6078. 13.02.18 18:12:10 Reply from [204.186.48.102] Bytes = 32 TTL = 61 Time = 28 ms
6079. 13.02.18 18:12:12 Reply from [204.186.48.102] Bytes = 32 TTL = 61 Time = 29 ms
6080. 13.02.18 18:12:14 Timeout
6081. 13.02.18 18:12:16 Timeout
6082. 13.02.18 18:12:18 Timeout
I've been getting a constant few percent packet loss to that first hop, it never goes away. I only get loss to anything after that hop when I actually have connection issues and can notice lag or complete drop offs from games/streaming. Also, not sure why my pings to my router are so high. They average 0 ms if I hit google, but they're high to PTD or yahoo, but only sometimes. I have results from days ago where my router pings when tracing to PTD were normal 0ms.
So that said, something may be wierd with the router, but my modem just had a No Ranging Response received - T3 time-out during this latest packet loss episode. If the modem has issues with the CMTS, that's definitely not caused by my router.
I want to call tomorrow and try the rental modem again, but swapping at any time other than when I'm having packet loss issues won't actually help me determine whether it's a problem with the modem. |
|
Bonka
join:2002-12-05
Tamaqua, PA | Going to run pathpings now instead of tracerts. Not entirely sure the difference between them, but they do give me different results. According to the tracerts, the 75.97.32.1 hop looks to be the problem, but the pathping makes it seem like 207.44.120.61 could be, based on the amount of timeouts. Don't know what to take from these, but I'll be emailing result files to support once I have more.
1. 192.168.1.1 [E1200]
2. 75.97.32.1 [75.97.32.1.res-cmts.sebh.ptd.net]
3. 207.44.120.61 [gateway-t3-2-brhblocal1.brh.ptd.net]
4. 204.186.48.102 [www2.ptd.net]
1. IP address: 192.168.1.1
Host name: E1200
Sent: 624
Received: 624
Lost: 0
Loss rate: 0 %
Min. time: 0 ms
Max. time: 39 ms
Avg. time: 0 ms
2. IP address: 75.97.32.1
Host name: 75.97.32.1.res-cmts.sebh.ptd.net
Sent: 637
Received: 612
Lost: 25
Loss rate: 3 %
Min. time: 6 ms
Max. time: 55 ms
Avg. time: 15 ms
3. IP address: 207.44.120.61
Host name: gateway-t3-2-brhblocal1.brh.ptd.net
Sent: 650
Received: 610
Lost: 40
Loss rate: 6 %
Min. time: 29 ms
Max. time: 236 ms
Avg. time: 36 ms
4. IP address: 204.186.48.102
Host name: www2.ptd.net
Sent: 652
Received: 626
Lost: 26
Loss rate: 3 %
Min. time: 26 ms
Max. time: 66 ms
Avg. time: 29 ms |
|
JeepMattC'mon the UPremium
join:2001-12-28
Wilmington, DE
kudos:2 Reviews:
 ·Comcast
 ·Verizon FiOS
| Bonka-
Thanks for the traces. Def shows it is within the PTD network.
I know they recently (past 6 months) merged you guys into the SECV overall network, so I'm wondering if something has just popped up since.
I can ping your gateway from my Comcast connection w/ no issue or PL.
--
"ONE team - ONE city - ONE dream!!" |
|
Bonka
join:2002-12-05
Tamaqua, PA | The tech guy from SECV I talked to wanted to get me on a different upstream port, and since I've been on a different one, I haven't had any issues that I've been around for. I do still get packet loss on mostly 1 hop, but it doesn't seem to affect anything. So maybe there's something wrong with some of the upstream that's available to me, maybe not. I wouldn't be surprised to have this start happening again randomly. |
|
|
|
Bonka
join:2002-12-05
Tamaqua, PA
2 edits | Was ok for almost a week and had the same issues start again tonight. Sent an email with some short logs to the guy I was in contact with before. Really hope they can figure out what the problem is and fix it, because I don't appreciate not being able to play some of my games since there are penalty systems in place for abandoning games, which the packetloss makes unavoidable.
Update:
Had severe packetloss again so I decided to take this opportunity to try getting my modem to connect on a different upstream channel. I swapped from channel 2 to 1 and the packetloss was gone. I swapped back from 1 to 2 and had packetless. I'm back on channel 1 with no issues yet. Wierdly, my original problems were when I was on channel 1 and swapping to 2 'fixed' them. While I'm still annoyed, I might have temporary fixes for when this happens and have great info for the cable company to use to hopefully pinpoint the problem.
Aaaand that didn't last long. Just had issues on channel 1 and swapped to 2 for the time being. I don't expect to not have issues on 2. There must be some serious issues with hardware or their cable. |
|
| reply to Bonka
Things were slow last night too. My last go around with them convinced me they are wankers. Since my data was from a dslreports speedtest it didn't mean anything. I could only use data from their speedtest. |
|
| reply to Bonka
The latency is horrible.
Tracing route to www.google.com [74.125.131.105]
over a maximum of 30 hops:
1 1 ms 2 ms 1 ms 320n [192.168.1.1]
2 2631 ms 1374 ms 1357 ms 70.44.72.1.res-cmts.brd2.ptd.net [70.44.72.1]
3 783 ms 12 ms 15 ms gateway-t3-2-brd2blocal1.brd.ptd.net [207.44.120
.33]
4 1363 ms 1440 ms 1496 ms gateway2-t3-2-abn22eph2.abn.ptd.net [216.144.163
.222]
5 1418 ms 1512 ms 1521 ms cpe-google-unk-unk.abn.ptd.net [207.44.112.26]
6 1497 ms 1443 ms 1431 ms 216.239.46.248
7 1569 ms 1536 ms 1571 ms 72.14.236.148
8 1665 ms 1616 ms 154 ms 209.85.241.222
9 1426 ms 1401 ms 1757 ms 209.85.251.228
10 * * * Request timed out.
11 1809 ms 1669 ms 1720 ms vc-in-f105.1e100.net [74.125.131.105] |
|
| reply to Bonka
Quick question...
Do you have any other devices in the house that might be using the upstream or downstream bandwidth? Maybe a device that's doing a backup to the "cloud" or something of that sort? I've seen devices hog upstream bandwidth and tear down the connection for all other devices in the home. This might explain why it fixes it after you change upstreams/connections because the device that was uploading waits until it reestablishes its connection(s).
Edit:
What speed package do you have? |
|
| Good question.
Maybe iCloud? But not much changed on my iPhone or ipad to back up.
Latency seems better today. I did check engr.ptd.net and there were no tickets for my area.
I have 12/1. We have 3 bonded upstreams and they give us a lousy 1mbps upload this day an age. I wish they would utilize the DOCSIS 3.0 technology and at least throw us a little more upload. Also for uTorrent my upload is capped at 40 KBps. When unlimited it can cause the net to come to a crawl. 40 K never posed to be a problem.
I'm thinking of switching to Ooma for phone since SECV doesn't have any web UI to enter any phone numbers to a blacklist. But if the net is unreliable then VOIP would be too.
My latency is at the first hop after my router which is res-cmts.brd2.ptd.net. I think it's an Arris C4 judging by the MAC address.
Bonka, what about you? Anything possibly hogging your upstream? |
|
