|
Distributel congestionPretty much every day around 9-10:30 pings across all server jump to about +80 of usual. I don't think this is node congestion as i live in a sparse neighborhood and only started happening after it switched from videotron. Does Distributel needs to update their backend. This server should be about 30ms. It is now doubled sometimes reaching in the 100's
C:\Users\Jessegr>tracert 198.144.179.99
Tracing route to host.colocrossing.com [198.144.179.99] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1 2 7 ms 6 ms 6 ms 10.246.203.65 3 34 ms 37 ms 33 ms ppp-206-80-245-49.nas01.totftds.ext.distributel. net [206.80.245.49] 4 35 ms 37 ms 37 ms ppp-206-80-245-49.nas01.totftds.ext.distributel. net [206.80.245.49] 5 43 ms 82 ms 40 ms 206.80.255.45 6 43 ms 44 ms 60 ms xe-3-0-2.cr1.tor1.ca.nlayer.net [69.31.142.129]
7 55 ms 53 ms 51 ms xe-0-1-1.cr2.ord1.us.nlayer.net [69.22.142.77] 8 77 ms 38 ms 42 ms as23352.ae6-102.cr2.ord1.us.nlayer.net [69.31.11 1.3] 9 43 ms 45 ms 95 ms ae4.cr2.ord6.us.scnet.net [204.93.204.87] 10 52 ms 61 ms 52 ms 72.ae2.ar2.ord6.us.scnet.net [204.93.204.159] 11 49 ms 40 ms 41 ms as36352.xe-0-1-0.ar2.ord6.us.scnet.net [50.31.17 0.126] 12 40 ms 40 ms 38 ms 10ge-1-3-2.fz146.cr2.chi.colocrossing.com [206.2 17.137.254] 13 50 ms 45 ms 47 ms host.colocrossing.com [205.234.152.250] 14 38 ms 41 ms 43 ms host.colocrossing.com [198.144.179.99]
Trace complete.
If Distributel could comment on backend problems this would be great. |
|
Nitra join:2011-09-15 Montreal |
Nitra
Member
2013-Oct-10 10:17 pm
Try winmtr to your server, will give you a better picture of the issue. |
|
|
DuPie to jessegr
Anon
2013-Oct-12 1:14 am
to jessegr
If you could post the results of the higher latency traceroute that be helpful, and what time you're seeing it. |
|
|
|---------------------------------------------------------------------------------- --------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | 192.168.1.1 - 0 | 36 | 36 | 0 | 0 | 1 | 0 | | 10.246.203.65 - 0 | 36 | 36 | 7 | 9 | 17 | 8 | | 206-80-244-169.cpe.distributel.net - 0 | 36 | 36 | 39 | 50 | 66 | 53 | | 206-80-244-169.cpe.distributel.net - 0 | 36 | 36 | 40 | 50 | 64 | 50 | | 206.80.255.49 - 0 | 36 | 36 | 39 | 55 | 66 | 56 | | gw-google.torontointernetxchange.net - 4 | 33 | 32 | 129 | 156 | 206 | 160 | | 209.85.255.232 - 0 | 36 | 36 | 56 | 70 | 79 | 65 | | 72.14.239.73 - 0 | 36 | 36 | 33 | 36 | 46 | 37 | | yyz08s10-in-f24.1e100.net - 0 | 36 | 36 | 62 | 71 | 84 | 76 | |________________________________________________|______|______|______|______|______|______| WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider |
|
jessegr |
Distributel congestion issues during peak using WinMTR. |
|
|
DuPie
Anon
2013-Oct-15 8:42 pm
It would be more beneficial if you could post traceroutes during affected and unaffected times to the same location... Your 2 posted traceroutes are for different locations so it's hard to compare. Latency in hops 3-5 seems the be slightly different.. but only by 10ms during the time periods, nothing really bad.
Re-reading your message I think what the real issue is - currently you're routing from Montreal -> Toronto -> peer in US -> server in Chicago.
With Videotron you might have had a more direct route to the colo company in the US, most likely didn't go through Toronto first to reach US peer.
If that's the issue, not much can be done about that. |
|
|
C:\Users\Jessegr>tracert google.ca
Tracing route to google.ca [173.194.43.111] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1 2 7 ms 7 ms 7 ms 10.246.203.65 3 65 ms 79 ms 75 ms 206-80-244-169.cpe.distributel.net [206.80.244.1 69] 4 71 ms 73 ms 75 ms 206-80-244-169.cpe.distributel.net [206.80.244.1 69] 5 78 ms 55 ms 76 ms 206.80.255.225 6 72 ms 68 ms 67 ms 206.80.255.45 7 88 ms 84 ms 86 ms 72.14.212.165 8 88 ms 87 ms 90 ms 209.85.255.232 9 87 ms 85 ms 86 ms 72.14.239.73 10 79 ms 83 ms 83 ms yyz08s10-in-f15.1e100.net [173.194.43.111]
Trace complete.
Nightly peak time slowdowns. Is distributel letting their links to videotron saturate and hoping most customers wont notice? |
|
1 edit |
Rez
Member
2014-Sep-8 9:43 pm
I'm also using distributel, and noticing slowdowns during congestion times.
C:\Windows\System32>tracert www.google.ca
Tracing route to www.google.ca [74.125.225.15] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms unknown [192.168.1.1] 2 8 ms 8 ms 7 ms 10.246.191.1 3 73 ms 70 ms 69 ms 206-80-244-169.cpe.distributel.net [206.80.244.1 69] 4 71 ms 80 ms 76 ms 206-80-244-169.cpe.distributel.net [206.80.244.1 69] 5 67 ms 75 ms 66 ms 206.80.255.225 6 72 ms 74 ms 71 ms 206.80.255.45 7 77 ms 74 ms 74 ms 72.14.212.165 8 88 ms 89 ms 86 ms 209.85.255.232 9 76 ms 70 ms 72 ms 216.239.46.162 10 111 ms 111 ms 109 ms 72.14.237.132 11 71 ms 74 ms 69 ms 72.14.237.109 12 119 ms 122 ms 125 ms ord08s12-in-f15.1e100.net [74.125.225.15]
Trace complete. |
|
|
Videotronland? Is so please post tracert. 100+ pings in all my games. |
|
|
Rez
Member
2014-Sep-8 11:00 pm
Tracing route to www.google.ca [173.194.46.127] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms unknown [192.168.1.1] 2 10 ms 9 ms 7 ms 10.246.191.1 3 10 ms 10 ms 8 ms ppp-206-80-245-49.nas01.totftds.ext.distributel. net [206.80.245.49] 4 13 ms 8 ms 15 ms ppp-206-80-245-49.nas01.totftds.ext.distributel. net [206.80.245.49] 5 16 ms 17 ms 16 ms 206.80.255.45 6 26 ms 27 ms 30 ms 72.14.212.165 7 29 ms 27 ms 26 ms 209.85.255.232 8 30 ms 28 ms 29 ms 216.239.46.162 9 29 ms 31 ms 30 ms 209.85.254.241 10 28 ms 30 ms 28 ms 209.85.245.225 11 28 ms 29 ms 29 ms ord08s13-in-f31.1e100.net [173.194.46.127]
Trace complete.
Taken when congestion period is done? |
|
|
Seems to have quieted down. It was lagging till about 10:30pm EST |
|
1 edit |
Rez
Member
2014-Sep-9 8:53 pm
Happening again. This is getting out of hand now. This is the exact same reason why I left Bell. After hours upon hours of trying to tell them what packet loss meant, they refused to see a problem with the connection. Simply because my speed tests were fine. |
|
|
Links to Videotron seem to be saturated again.
C:\Users\Jessegr>tracert google.ca
Tracing route to google.ca [173.194.43.88] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1 2 8 ms 7 ms 7 ms 10.246.203.65 3 64 ms 52 ms 51 ms 206-80-244-169.cpe.distributel.net [206.80.244.1 69] 4 51 ms 48 ms 51 ms 206-80-244-169.cpe.distributel.net [206.80.244.1 69] 5 19 ms 20 ms 52 ms 206.80.255.225 6 37 ms 36 ms 34 ms 206.80.255.45 7 112 ms 99 ms 86 ms 72.14.212.165 8 58 ms 59 ms 61 ms 216.239.47.114 9 61 ms 61 ms 63 ms 72.14.239.19 10 74 ms 70 ms 70 ms yyz08s09-in-f24.1e100.net [173.194.43.88]
Trace complete.
C:\Users\Jessegr> |
|
|
Ivona
Anon
2014-Sep-11 9:13 pm
Experience this issue as well, high latencies in peak usage hours, up to 400ms on trace to google.ca; live in the Waterloo ON area. |
|
|
kwguy123
Anon
2014-Sep-12 4:16 pm
Ditto.
Stanley park area in Kitchener |
|
|
to jessegr
Yea I been having issues with them lately too around 830pm-11pm. I dont know if its being on a grandfathered plan (28/1) and having to do with their newer plans.
Used to be great up till this started happening over a month ago now.
I know some sites see me as in Ottawa even though I'm in Toronto. |
|
1 edit |
C:\Users\Jessegr>tracert google.ca
Started at 8pm today.
Tracing route to google.ca [173.194.43.87] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1 2 8 ms 7 ms 7 ms 10.246.203.65 3 63 ms 61 ms 62 ms 206-80-244-169.cpe.distributel.net [206.80.244.1 69] 4 68 ms 68 ms 64 ms 206-80-244-169.cpe.distributel.net [206.80.244.1 69] 5 30 ms 61 ms 20 ms 206.80.255.225 6 43 ms 43 ms 42 ms 206.80.255.45 7 94 ms 96 ms 97 ms 72.14.212.165 8 65 ms 64 ms 129 ms 216.239.47.114 9 60 ms 62 ms 63 ms 72.14.239.19 10 57 ms 58 ms 58 ms yyz08s09-in-f23.1e100.net [173.194.43.87]
Trace complete.
C:\Users\Jessegr> |
|
|
to jessegr
Yup I am in London, Ontario with Distributel Cable 25 down 2 up.
I just ran a speed test came back with 8 down & just under 2 up..
I was wondering what was going on! Jeez!
Now just ran a 2nd one at a different location(Toronto) and the results were much
better! Huh!
Setup is only 1 rental cable modem directly connected via ethernet to the desktop pc so.
Crazy! |
|
|
Panchos
Anon
2014-Sep-16 10:41 am
When using speedtest sites, I have found that sometimes some speedtest providers do not give you consistent results. One server might say 8 Mbps on a 25 Mbps connection and another might give you more to your proper amount. It depends on the bandwidth and the server they are using.
Also, with Distributel internet, always use Toronto. |
|
|
Yeah, you are right! However I am absolutely getting congestion crazy ping/latency after 7/8pm I am playing Marvel Heroes 2015. It is a very simple setup, 1 rental cable modem Huawei MT130U directly connected via ethernet to my NIC on my desktop PC. No router, no wifi/wireless. This congestion and high ping/latency has happened the past 2 days in a row! Sigh... |
|
|
The lag period has begun for me as well. I wonder if Distributel even check these forums. At least Teksavvy has a presence here.... |
|
|
to jessegr
Yup, same thing again as well here. So sad & frustrating! |
|
|
jessegr
Member
2014-Sep-16 11:00 pm
Exactly 11pm and the lantency subsides. The problem is i have full speed during this time. Could this be some sort of throttling or traffic shaping to reduce load on the network. |
|
|
Chosen1
Anon
2014-Sep-17 6:19 am
Guys contact Distributel I did and tonight I had no issues with my internet. technical.support@distributel.ca also check out this site - » speedtest.distributel.net/ once done you can see your latency etc |
|
|
|
C:\Users\Jessegr>tracert google.ca
Pretty bad tonight guys.
Tracing route to google.ca [74.125.226.119] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1 2 7 ms 7 ms 8 ms 10.246.203.65 3 80 ms 79 ms 83 ms 206-80-244-169.cpe.distributel.net [206.80.244.1 69] 4 77 ms 79 ms 81 ms 206-80-244-169.cpe.distributel.net [206.80.244.1 69] 5 73 ms 69 ms 95 ms 206.80.255.225 6 92 ms 88 ms 91 ms 206.80.255.45 7 98 ms 94 ms 88 ms 72.14.212.165 8 120 ms 121 ms 120 ms 216.239.47.114 9 * 98 ms 95 ms 209.85.250.207 10 114 ms 114 ms 116 ms yyz08s13-in-f23.1e100.net [74.125.226.119]
Trace complete.
C:\Users\Jessegr> |
|
|
VolumexD
Anon
2014-Sep-18 1:42 pm
I called one time since I can't play any games from 8 to 11:30. They told me to do a speedtest and it was fine so he didn't understand the problem. He told me that he would love to help but didn't know, I told him which hops were spiking like crazy, which in my case were the NTT routers but he didn't understand anything outside of speedtest. |
|
jmckformerly 'shaded' join:2010-10-02 Ottawa, ON |
jmck
Member
2014-Sep-18 5:19 pm
well you haven't posted anything here yet. while NTT has some US presence most of their network is out in Asia so high latency there wouldn't be a surprise. |
|
|
Chosen1 to VolumexD
Anon
2014-Sep-18 6:13 pm
to VolumexD
CONTACT DISTRIBUTEL
technical.support@distributel.ca
Provide them with all the information including the links to this forum. Tell them the exact times it happens, I did all this and they have sent my information to Rogers to look into the issue further.
THIS IS WHAT YOU NEED TO DO..DON'T BOTHER CALLING
also contact
linda@distributel.ca she's the community manager and is aware of issues, the same issues I reported already. |
|
1 edit |
to jessegr
Continue to post traceroutes if you are experiencing this issue. Do a traceroute to the first address in the traceroute and post the results. That will help in the debugging. |
|
|
to jessegr
I've been getting horrible speeds/latency between around 7:00-11:00 pm every night here in Toronto (North York) for the past few weeks as well. Glad to see it isn't only me with this problem, but if it persists for much longer, I'll have no choice but to switch ISPs. |
|