·EBOX
|
to ggShikun
Re: [Cable] can't game during off-peak?from what I read lol servers are unpingable. They won't respond to ping requests. from this topic : » forums.na.leagueoflegend ··· ghlight=you can try to ping : 208.76.153.129 |
|
|
ggShikun
Anon
2014-Sep-9 7:15 pm
here are 3 tests i did with WinMTR. the first one was laggy, but it went away and i could play again. the second 2 were to the point where the game was done for me and there was no getting back into the game cus the lag was not going away. |
|
ggShikun |
ggShikun to Hyrules
Anon
2014-Sep-10 5:59 pm
to Hyrules
ICSI Netalyzer Results
IPv6 TCP connectivity (?): Note Direct TCP connections to remote FTP servers (port 21) failed. This is commonly due to how a NAT or firewall handles FTP traffic, as FTP causes unique problems when developing NATs and firewalls. Direct TCP access to remote SSH servers (port 22) is blocked. Direct TCP access to remote SMTP servers (port 25) is prohibited. This means you cannot send email via SMTP to arbitrary mail servers. Such blocking is a common countermeasure against malware abusing infected machines for generating spam. Your ISP likely provides a specific mail server that is permitted. Also, webmail services remain unaffected. Direct TCP access to remote POP3 servers (port 110) is blocked. Direct TCP access to remote RPC servers (port 135) is blocked. This is probably for security reasons, as this protocol is generally not designed for use outside the local network. Direct TCP access to remote NetBIOS servers (port 139) is blocked. This is probably for security reasons, as this protocol is generally not designed for use outside the local network. Direct TCP access to remote IMAP servers (port 143) is blocked. Direct TCP access to remote SNMP servers (port 161) is blocked. This is probably for security reasons, as this protocol is generally not designed for use outside the local network. Direct TCP access to remote HTTPS servers (port 443) is blocked. Direct TCP access to remote SMB servers (port 445) is blocked. This is probably for security reasons, as this protocol is generally not designed for use outside the local network. Direct TCP access to remote SMTP/SSL servers (port 465) is blocked. Direct TCP access to remote secure IMAP servers (port 585) is blocked. Direct TCP access to remote authenticated SMTP servers (port 587) is blocked. Direct TCP access to remote IMAP/SSL servers (port 993) is blocked. Direct TCP access to remote POP/SSL servers (port 995) is blocked. Direct TCP access to remote OpenVPN servers (port 1194) is blocked. Direct TCP access to remote PPTP Control servers (port 1723) is blocked. Direct TCP access to remote SIP servers (port 5060) is allowed. Direct TCP access to remote BitTorrent servers (port 6881) is allowed. Direct TCP access to remote TOR servers (port 9001) is allowed. |
|
|
LoL issues
Anon
2014-Sep-10 9:43 pm
Hi,
I'm also having huge issues with connecting to LoL. Many of my games are also extremely laggy. The issue is restricted to LoL and no other game (or anything that uses the internet. My connection works fine).
I think these problems are very common in Quebec. I've checked on the official forums and it seems that many Quebecers are having issues. My friends are also experiencing these, but all the other random people in my games aren't having any.
I'm not asking for a specific fix, but does anybody know why there seems to be a connection issue between e-box or videotron and the LoL servers? |
|
|
|
ggShikun
Anon
2014-Sep-11 12:33 am
|---------------------------------------------------------------------------------- --------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | router.dlink.com - 0 | 747 | 747 | 0 | 0 | 1 | 0 | | 7.223.115.1 - 0 | 748 | 748 | 2 | 7 | 36 | 7 | | 209.148.245.149 - 0 | 748 | 748 | 5 | 12 | 46 | 14 | |so-4-2-2.gw02.ym.phub.net.cable.rogers.com - 0 | 748 | 748 | 5 | 11 | 24 | 12 | |te0-5-0-6.ccr21.ymq02.atlas.cogentco.com - 0 | 748 | 748 | 11 | 18 | 42 | 17 | | be2088.ccr21.alb02.atlas.cogentco.com - 0 | 748 | 748 | 17 | 23 | 42 | 23 | | be2109.mpd22.jfk02.atlas.cogentco.com - 1 | 744 | 743 | 21 | 27 | 46 | 26 | | be2151.mpd22.dca01.atlas.cogentco.com - 1 | 744 | 743 | 26 | 33 | 55 | 31 | | be2171.ccr42.atl01.atlas.cogentco.com - 0 | 748 | 748 | 38 | 44 | 63 | 46 | | be2173.ccr22.iah01.atlas.cogentco.com - 0 | 748 | 748 | 52 | 59 | 91 | 62 | | be2068.mpd22.lax01.atlas.cogentco.com - 0 | 748 | 748 | 87 | 94 | 110 | 95 | | te8-1.mag02.lax01.atlas.cogentco.com - 1 | 720 | 713 | 90 | 110 | 310 | 147 | | 154.24.22.122 - 1 | 744 | 743 | 87 | 94 | 111 | 94 | | 38.88.244.2 - 0 | 748 | 748 | 90 | 94 | 110 | 95 | | border1.po2-40g-bbnet2.lax010.pnap.net - 0 | 748 | 748 | 90 | 97 | 286 | 96 | | No response from host - 100 | 150 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 150 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 150 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 150 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 150 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 150 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 150 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 150 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 150 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 150 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 150 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 150 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 150 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 150 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 150 | 0 | 0 | 0 | 0 | 0 | |________________________________________________|______|______|______|______|______|______| WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
It goes from an almost perfect connection everywhere to a complete dead zone after border1.po2-40g-bbnet2.lax010.pnap.net. Many other reports cut off exactly where mine does too. |
|
ggShikun |
to LoL issues
I got the IP from LoL netlogs.
Tracing route to 192.64.171.137 over a maximum of 30 hops
1 1 ms 1 ms 1 ms router.dlink.com [192.168.0.1] 2 6 ms 7 ms 7 ms 7.223.115.1 3 15 ms 10 ms 11 ms 209.148.245.149 4 11 ms 11 ms 11 ms so-4-2-2.gw02.ym.phub.net.cable.rogers.com [64.7 1.240.185] 5 15 ms 24 ms 24 ms 10ge3-1.core1.ymq1.he.net [216.66.50.109] 6 28 ms 39 ms 33 ms 10ge14-4.core1.nyc4.he.net [184.105.222.97] 7 28 ms 27 ms 25 ms above.net [198.32.118.25] 8 28 ms 27 ms 27 ms ae5.cr2.lga5.us.above.net [64.125.21.82] 9 43 ms 40 ms 41 ms ae6.cr2.ord2.us.above.net [64.125.24.30] 10 42 ms 42 ms 42 ms ae11.cr1.ord2.us.above.net [64.125.20.245] 11 94 ms 90 ms 89 ms ae16.mpr1.sea1.us.above.net [64.125.21.138] 12 92 ms 93 ms 91 ms ae8.mpr1.pdx1.us.above.net [64.125.30.26] 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. 23 * * * Request timed out. 24 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out.
Trace complete. |
|
Nitra join:2011-09-15 Montreal |
Nitra
Member
2014-Sep-11 8:17 am
Clear as day, issue is well outside of ebox control. It's not anywhere close to their network. |
|
|
LoL issues to ggShikun
Anon
2014-Sep-11 11:12 am
to ggShikun
By the way, I forgot to add that this isn't caused by off-peak. The issue happens at any time of the day. |
|
|
|
ggShikun to Nitra
Anon
2014-Sep-11 2:57 pm
to Nitra
assuming the riot server is supposed to be the final hop, it doesn't seem like it's riot's issue either. so am i just shit out of luck? or is there a way to get rerouted or something? |
|
·EBOX
|
said by ggShikun :assuming the riot server is supposed to be the final hop, it doesn't seem like it's riot's issue either. so am i just shit out of luck? or is there a way to get rerouted or something? Routing for the path isn't Ebox's job. Telling you right now. |
|
|
ggShikun
Anon
2014-Sep-11 11:28 pm
said by Lebon14:said by ggShikun :assuming the riot server is supposed to be the final hop, it doesn't seem like it's riot's issue either. so am i just shit out of luck? or is there a way to get rerouted or something? Routing for the path isn't Ebox's job. Telling you right now. I never said it was. I just want to know if there is a solution and how to attain it. |
|
|
LoL issues
Anon
2014-Sep-13 12:19 am
Found a solution.
You need a VPN. I started using "WTFast" yesterday and it solved all the problems. It has a 30 days free trial. I use the Chicago servers, but I haven't tried using others, so maybe there are better ones. |
|
·EBOX
|
said by LoL issues :Found a solution.
You need a VPN. I started using "WTFast" yesterday and it solved all the problems. It has a 30 days free trial. I use the Chicago servers, but I haven't tried using others, so maybe there are better ones. So, you are forcing youself through another route to the server. Unfortunately, that cost you something... |
|