|
to jessegr
Re: Distributel congestionhad bad lag tonight till now, » imgur.com/xgm1RF6 |
|
|
to jessegr
I'm been having the same problems every night. I just send a formalish email to distributel feedback with all my tech interactions requesting immediate action and compensation or I'm switching somewhere else. Latest ping tonight, google hit 400ms!!! .
London Ontario user.
Pinging www.google.com [74.125.225.145] with 32 bytes of data
Reply from 74.125.225.145: bytes=32 time=65ms TTL=55 Reply from 74.125.225.145: bytes=32 time=30ms TTL=55 Reply from 74.125.225.145: bytes=32 time=30ms TTL=55 Reply from 74.125.225.145: bytes=32 time=52ms TTL=55 Reply from 74.125.225.145: bytes=32 time=29ms TTL=55 Reply from 74.125.225.145: bytes=32 time=31ms TTL=55 Reply from 74.125.225.145: bytes=32 time=85ms TTL=55 Reply from 74.125.225.145: bytes=32 time=39ms TTL=55 Reply from 74.125.225.145: bytes=32 time=91ms TTL=55 Reply from 74.125.225.145: bytes=32 time=28ms TTL=55 Reply from 74.125.225.145: bytes=32 time=53ms TTL=55 Reply from 74.125.225.145: bytes=32 time=122ms TTL=55 Reply from 74.125.225.145: bytes=32 time=71ms TTL=55 Reply from 74.125.225.145: bytes=32 time=29ms TTL=55 Reply from 74.125.225.145: bytes=32 time=34ms TTL=55 Reply from 74.125.225.145: bytes=32 time=39ms TTL=55 Reply from 74.125.225.145: bytes=32 time=31ms TTL=55 Reply from 74.125.225.145: bytes=32 time=94ms TTL=55 Reply from 74.125.225.145: bytes=32 time=42ms TTL=55 Reply from 74.125.225.145: bytes=32 time=30ms TTL=55 Reply from 74.125.225.145: bytes=32 time=71ms TTL=55 Reply from 74.125.225.145: bytes=32 time=30ms TTL=55 Reply from 74.125.225.145: bytes=32 time=29ms TTL=55 Reply from 74.125.225.145: bytes=32 time=31ms TTL=55 Reply from 74.125.225.145: bytes=32 time=42ms TTL=55 Reply from 74.125.225.145: bytes=32 time=170ms TTL=55 Reply from 74.125.225.145: bytes=32 time=121ms TTL=55 Reply from 74.125.225.145: bytes=32 time=110ms TTL=55 Reply from 74.125.225.145: bytes=32 time=153ms TTL=55 Reply from 74.125.225.145: bytes=32 time=155ms TTL=55 Reply from 74.125.225.145: bytes=32 time=201ms TTL=55 Reply from 74.125.225.145: bytes=32 time=161ms TTL=55 Reply from 74.125.225.145: bytes=32 time=95ms TTL=55 Reply from 74.125.225.145: bytes=32 time=84ms TTL=55 Reply from 74.125.225.145: bytes=32 time=64ms TTL=55 Reply from 74.125.225.145: bytes=32 time=31ms TTL=55 Reply from 74.125.225.145: bytes=32 time=182ms TTL=55 Reply from 74.125.225.145: bytes=32 time=90ms TTL=55 Reply from 74.125.225.145: bytes=32 time=211ms TTL=55 Reply from 74.125.225.145: bytes=32 time=323ms TTL=55 Reply from 74.125.225.145: bytes=32 time=239ms TTL=55 Reply from 74.125.225.145: bytes=32 time=188ms TTL=55 Reply from 74.125.225.145: bytes=32 time=160ms TTL=55 Reply from 74.125.225.145: bytes=32 time=243ms TTL=55 Reply from 74.125.225.145: bytes=32 time=200ms TTL=55 Reply from 74.125.225.145: bytes=32 time=232ms TTL=55 Reply from 74.125.225.145: bytes=32 time=196ms TTL=55 Reply from 74.125.225.145: bytes=32 time=150ms TTL=55 Reply from 74.125.225.145: bytes=32 time=228ms TTL=55 Reply from 74.125.225.145: bytes=32 time=214ms TTL=55 Reply from 74.125.225.145: bytes=32 time=174ms TTL=55 Reply from 74.125.225.145: bytes=32 time=230ms TTL=55 Reply from 74.125.225.145: bytes=32 time=134ms TTL=55 Reply from 74.125.225.145: bytes=32 time=250ms TTL=55 Reply from 74.125.225.145: bytes=32 time=194ms TTL=55 Reply from 74.125.225.145: bytes=32 time=185ms TTL=55 Reply from 74.125.225.145: bytes=32 time=150ms TTL=55 Reply from 74.125.225.145: bytes=32 time=255ms TTL=55 Reply from 74.125.225.145: bytes=32 time=352ms TTL=55 Reply from 74.125.225.145: bytes=32 time=154ms TTL=55 Reply from 74.125.225.145: bytes=32 time=365ms TTL=55 Reply from 74.125.225.145: bytes=32 time=249ms TTL=55 Reply from 74.125.225.145: bytes=32 time=404ms TTL=55 Reply from 74.125.225.145: bytes=32 time=308ms TTL=55 Reply from 74.125.225.145: bytes=32 time=303ms TTL=55 Reply from 74.125.225.145: bytes=32 time=257ms TTL=55 Reply from 74.125.225.145: bytes=32 time=361ms TTL=55 Reply from 74.125.225.145: bytes=32 time=265ms TTL=55 Reply from 74.125.225.145: bytes=32 time=96ms TTL=55 Reply from 74.125.225.145: bytes=32 time=132ms TTL=55 Reply from 74.125.225.145: bytes=32 time=181ms TTL=55 Reply from 74.125.225.145: bytes=32 time=54ms TTL=55 Reply from 74.125.225.145: bytes=32 time=69ms TTL=55 Reply from 74.125.225.145: bytes=32 time=85ms TTL=55 Reply from 74.125.225.145: bytes=32 time=83ms TTL=55 Reply from 74.125.225.145: bytes=32 time=65ms TTL=55 Reply from 74.125.225.145: bytes=32 time=80ms TTL=55 Reply from 74.125.225.145: bytes=32 time=90ms TTL=55 Reply from 74.125.225.145: bytes=32 time=86ms TTL=55 Reply from 74.125.225.145: bytes=32 time=29ms TTL=55 Reply from 74.125.225.145: bytes=32 time=66ms TTL=55 Reply from 74.125.225.145: bytes=32 time=96ms TTL=55 Reply from 74.125.225.145: bytes=32 time=61ms TTL=55 Reply from 74.125.225.145: bytes=32 time=104ms TTL=55 Reply from 74.125.225.145: bytes=32 time=71ms TTL=55 Reply from 74.125.225.145: bytes=32 time=32ms TTL=55 Reply from 74.125.225.145: bytes=32 time=71ms TTL=55 Reply from 74.125.225.145: bytes=32 time=29ms TTL=55 |
|
Mazgazine |
To give some better perspective , here is how spotless the ping was this morning, note how there are no spikes and this is HALF the speed of the lowest in last nights ping.
Pinging google.com [74.125.226.100] with 32 bytes of Reply from 74.125.226.100: bytes=32 time=14ms TTL=57 Reply from 74.125.226.100: bytes=32 time=17ms TTL=57 Reply from 74.125.226.100: bytes=32 time=13ms TTL=57 Reply from 74.125.226.100: bytes=32 time=15ms TTL=57 Reply from 74.125.226.100: bytes=32 time=14ms TTL=57 Reply from 74.125.226.100: bytes=32 time=15ms TTL=57 Reply from 74.125.226.100: bytes=32 time=15ms TTL=57 Reply from 74.125.226.100: bytes=32 time=13ms TTL=57 Reply from 74.125.226.100: bytes=32 time=16ms TTL=57 Reply from 74.125.226.100: bytes=32 time=15ms TTL=57 Reply from 74.125.226.100: bytes=32 time=12ms TTL=57 Reply from 74.125.226.100: bytes=32 time=14ms TTL=57 Reply from 74.125.226.100: bytes=32 time=13ms TTL=57 Reply from 74.125.226.100: bytes=32 time=14ms TTL=57 Reply from 74.125.226.100: bytes=32 time=14ms TTL=57 Reply from 74.125.226.100: bytes=32 time=12ms TTL=57 Reply from 74.125.226.100: bytes=32 time=14ms TTL=57 Reply from 74.125.226.100: bytes=32 time=26ms TTL=57 Reply from 74.125.226.100: bytes=32 time=13ms TTL=57 Reply from 74.125.226.100: bytes=32 time=15ms TTL=57 Reply from 74.125.226.100: bytes=32 time=13ms TTL=57 Reply from 74.125.226.100: bytes=32 time=13ms TTL=57 Reply from 74.125.226.100: bytes=32 time=11ms TTL=57 |
|
|
run winMTR instead of a basic ping. or use pathping instead of just typing ping » winmtr.net/both are far more useful to try and see the underlying problem. |
|
|
to jessegr
I'm not sure how exactly that program is representing my local connection... Everything I do that involves a lot of packet use - Torrents from anything, games - run like crap. Even pings to google.com - but I can run speed tests and TRacerts and NOTHING shows up.
|---------------------------------------------------------------------------------- --------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | CISCO16911 - 0 | 41 | 41 | 0 | 0 | 1 | 0 | | 10.101.78.129 - 0 | 41 | 41 | 7 | 13 | 39 | 12 | | 24.156.136.13 - 0 | 41 | 41 | 12 | 19 | 48 | 19 | | gw01.hnsn.phub.net.cable.rogers.com - 0 | 41 | 41 | 13 | 18 | 42 | 18 | | 72.14.212.165 - 0 | 41 | 41 | 13 | 17 | 43 | 15 | | 216.239.47.114 - 0 | 41 | 41 | 12 | 22 | 61 | 16 | | 216.239.46.160 - 0 | 41 | 41 | 27 | 33 | 75 | 31 | | 209.85.254.239 - 0 | 41 | 41 | 26 | 35 | 61 | 38 | | 209.85.240.150 - 3 | 37 | 36 | 27 | 32 | 47 | 29 | | ord08s08-in-f19.1e100.net - 0 | 41 | 41 | 27 | 40 | 89 | 41 | |________________________________________________|______|______|______|______|______|______| WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
What is going on here? I am literally getting under 100KB/s on stuff with 100+ connected seeders...
Is there officially throttling to torrents for 3rd party ISPS on cable now?! Its REALLY bad today... |
|
|
|---------------------------------------------------------------------------------- --------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | 192.168.1.1 - 0 | 780 | 780 | 0 | 0 | 7 | 0 | | 10.101.61.1 - 0 | 780 | 780 | 6 | 10 | 70 | 7 | |van58-6-240-153.dynamic.rogerstelecom.net - 0 | 780 | 780 | 12 | 23 | 72 | 13 | | 24.153.7.237 - 0 | 780 | 780 | 10 | 22 | 79 | 16 | |xe-1-2-0-0.ipr02.totftds.distributel.net - 1 | 776 | 775 | 10 | 13 | 55 | 22 | | ae0-709.tor10.ip4.gtt.net - 0 | 780 | 780 | 11 | 23 | 110 | 13 | | xe-0-3-2.nyc20.ip4.gtt.net - 0 | 780 | 780 | 21 | 32 | 94 | 30 | | 192.205.37.37 - 0 | 780 | 780 | 23 | 39 | 90 | 30 | | cr1.n54ny.ip.att.net - 0 | 780 | 780 | 98 | 102 | 141 | 99 | | cr2.cgcil.ip.att.net - 1 | 776 | 775 | 98 | 102 | 187 | 112 | | cr1.cgcil.ip.att.net - 0 | 780 | 780 | 98 | 105 | 155 | 106 | | cr2.dvmco.ip.att.net - 0 | 780 | 780 | 98 | 105 | 218 | 100 | | cr1.slkut.ip.att.net - 0 | 780 | 780 | 98 | 108 | 211 | 102 | | cr2.la2ca.ip.att.net - 0 | 780 | 780 | 98 | 109 | 241 | 104 | | gar5.lsrca.ip.att.net - 0 | 780 | 780 | 97 | 118 | 393 | 158 | | 12-122-254-230.attens.net - 1 | 760 | 755 | 98 | 111 | 329 | 133 | | 206.16.68.42 - 1 | 764 | 760 | 98 | 107 | 338 | 105 | | 12.129.248.118 - 1 | 776 | 775 | 98 | 103 | 147 | 100 | | 12.129.209.68 - 0 | 780 | 780 | 99 | 125 | 272 | 146 | |________________________________________________|______|______|______|______|______|______| WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider |
|
|
Belmire
Anon
2014-Oct-19 1:13 pm
Yep, I'm on 30mbps cable Acanac (Distributel) in Montreal (St. Leonard) and it's been pretty bad for a few weeks. Latency is horrible. Seems like straight forward congestion because before then, it was a very solid connection. I guess more and more people are hopping on for their unlimited plan. Hope you guys can resolve it soon. |
|
|
to jessegr
|
|
|
to jessegr
UPDATE
I got my FTTN setup today and the congestion problems are completely gone (as expected).
I recommend that anyone who has FTTN available at their address switch over. |
|