: Still having issues with Ping. I am using ATT and I have 100-240 ping each game and it really makes it hard to play. The lag is very real and yeah @_@! Oh I live in Califorina so yeah. Are you guys still trying to talk to ATT or working with them?
> [{quoted}](name=GoddessLuna,realm=NA,application-id=osqw6G4M,discussion-id=PZclbVoE,comment-id=041a,timestamp=2015-08-28T17:07:55.841+0000) > > Still having issues with Ping. I am using ATT and I have 100-240 ping each game and it really makes it hard to play. The lag is very real and yeah @_@! Oh I live in Califorina so yeah. Are you guys still trying to talk to ATT or working with them? We're not far away - technical documents are starting to arrive from AT&T.
: Chicago Connection Clinic Megathread [Closed]
Shaw turned up Chicago peering - should see some improvements as of an hour or so ago. Let us know!
: Is there a reason everything was going swimmingly for the first day? On the test day (I think) and immediately after the server move I was sitting at 76ping, now it's sitting at 86-89, which is really unfortunate. I don't understand why everything was going great, then (you or shaw?) messed up and now I get a nice 10ping tacked on... Hopefully Shaw gets it together and this is resolved soon, going from 42-76 is bad enough, I really don't want to be sitting at 86-89 all the time. :/
> [{quoted}](name=The Soup Kitchen,realm=NA,application-id=osqw6G4M,discussion-id=PZclbVoE,comment-id=03530015,timestamp=2015-08-28T11:05:19.831+0000) > > Is there a reason everything was going swimmingly for the first day? On the test day (I think) and immediately after the server move I was sitting at 76ping, now it's sitting at 86-89, which is really unfortunate. > > I don't understand why everything was going great, then (you or shaw?) messed up and now I get a nice 10ping tacked on... > > Hopefully Shaw gets it together and this is resolved soon, going from 42-76 is bad enough, I really don't want to be sitting at 86-89 all the time. :/ It got worse as we tried to make it better D: Sometimes these things happen - everyone has their own idea about what the best way to route is. Shaw's is somewhat different to ours. The high Shaw latency outside of BC is something we identified a) wrong and b) should be relatively quick to fix - if Shaw were to help us. We've been on our own at the moment in trying to make things better, and in attempting to remove Shaw's routing decisions out of the way, we uncovered another routing decision of theirs which is even worse. When I tried to re-establish the Seattle peering session to put it back to at least how it was the day of the move, it didn't come up on Shaw's end. I let them know immediately - no response yet. This is very visible on their side of things now, hoping this will be addressed in business hours tomorrow.
Carsten (NA)
: Location: Southern Ontario ISP: Wightman Telecom Old Ping: 90-95 New Ping: 99-120 Riot Please! I know many, many players in my area with this same problem. We would love to see Riot to be peered with Wightman Telecom! Thank you Riot!
> [{quoted}](name=Carsten,realm=NA,application-id=osqw6G4M,discussion-id=PZclbVoE,comment-id=03eb,timestamp=2015-08-28T05:01:45.678+0000) > > Location: Southern Ontario > ISP: Wightman Telecom > > Old Ping: 90-95 > New Ping: 99-120 > > Riot Please! I know many, many players in my area with this same problem. We would love to see Riot to be peered with Wightman Telecom! Thank you Riot! Hi there! Sadly, I can't find any public information about how to peer with your ISP - the usual places are empty and I can only see transit providers when I look at routing. It may be beneficial for your to reach out to them with the info (What can I do to help?) linked in the very first post of this thread.
Eravel (NA)
: Location: Saskatoon, Saskatchewan, Canada ISP: Rogers Old Ping: 40-50 New Ping: 100-110 Saskatoon to Chicago: 1,318 miles (according to Google) Saskatoon to Seattle: 1,040 miles (according to Google again) ...What happened? According to that little gif showing ping numbers, it should have stayed (relatively) unchanged, rather than doubling. Thanks in advance. Edit: Is there anything I can possibly do to help streamline the connection a bit more, bring it down to 80-90 ping?
> [{quoted}](name=Eravel,realm=NA,application-id=osqw6G4M,discussion-id=PZclbVoE,comment-id=03ea,timestamp=2015-08-28T04:56:57.334+0000) > > Location: Saskatoon, Saskatchewan, Canada > ISP: Rogers > > Old Ping: 40-50 > New Ping: 100-110 > > Saskatoon to Chicago: 1,318 miles (according to Google) > Saskatoon to Seattle: 1,040 miles (according to Google again) > > ...What happened? According to that little gif showing ping numbers, it should have stayed (relatively) unchanged, rather than doubling. Thanks in advance. Similar situation with Shaw - you're being routed in the wrong direction. We're waiting for Rogers to upgrade their equipment in the Chicago area - they'll be able to peer with us there shortly.
Martyy (NA)
: Does this mean that they will not be rerouting the connection at all? Or that they have not done so?
> [{quoted}](name=Martyy,realm=NA,application-id=osqw6G4M,discussion-id=PZclbVoE,comment-id=03e10001,timestamp=2015-08-28T04:38:49.901+0000) > > Does this mean that they will not be rerouting the connection at all? Or that they have not done so? They said they would, so we can only take their word for it!
Arc Noir (NA)
: I'm still dealing with huge packet loss on each game I play.. I'm thinking of quitting and I can't figure out the solution OR get help.
> [{quoted}](name=Arkaia,realm=NA,application-id=osqw6G4M,discussion-id=PZclbVoE,comment-id=03e8,timestamp=2015-08-28T04:51:44.584+0000) > > I'm still dealing with huge packet loss on each game I play.. I'm thinking of quitting and I can't figure out the solution OR get help. Sorry about this! We're working with Charter to find and zap the issue.
: Chicago Connection Clinic Megathread [Closed]
Hey Shaw players, Since I've disabled peering, our mutual upstream are sending the traffic to Washington DC to meet Shaw. Gross. Sorry about this - I'm trying every little tweak I have available to me, but it looks like we're going to have to wait for Shaw to assist on this one. [e] I re-established peering in Seattle - it's not ideal but at least it's more within my control.
: Chicago Connection Clinic Megathread [Closed]
Might take a little time for the changes to come in to effect - let me know over the next hour.
: Chicago Connection Clinic Megathread [Closed]
Hey Shaw peoples, I've turned down our peering session after the failed reroute. Let me know how your perfomance is over the next hour. Will try to get this resolved as soon as possible, hopefully Shaw get back to us tomorrow.
: "August 27 @ 18:51 PDT: We have made some change Shaw, that should improve routing. Make sure to test out and reply back in this thread if our changes have or haven't improved your ping!" Shaw Communications customer, living in Ontario. Pre-migration my ping was steady at 80ms, post it is a constant 115ms even after the Aug 27 18:51 PDT update it is still 115ms. I've sent logs in after each Shaw update has been posted hoping to get this resolved asap. Looks like I'm still being routed to across the country and back.
> [{quoted}](name=Moist Sloth PhD,realm=NA,application-id=osqw6G4M,discussion-id=PZclbVoE,comment-id=03e0,timestamp=2015-08-28T03:37:56.310+0000) > > "August 27 @ 18:51 PDT: We have made some change Shaw, that should improve routing. Make sure to test out and reply back in this thread if our changes have or haven't improved your ping!" > > Shaw Communications customer, living in Ontario. > Pre-migration my ping was steady at 80ms, post it is a constant 115ms even after the Aug 27 18:51 PDT update it is still 115ms. > I've sent logs in after each Shaw update has been posted hoping to get this resolved asap. > Looks like I'm still being routed to across the country and back. Let me know if this changes in the next game - I'll be sitting here in the forums.
Orazzz (NA)
: How about Shaw users in Ontario? Will we be routed to Seattle and then to Chicago as well? As of now, as a result of the server transfer my ping has climbed from 79 (prior to transfer) to 115-117 (post-move to Chicago) and more unstable. I'm concerned that my ping would benefit more from being Public than peered :( Thanks for taking the time to address the issues with Shaw - a follow-up to my question would be awesome. Cheers
> Will we be routed to Seattle and then to Chicago as well? This is currently the case - and it should go away when Shaw have configured their side of their Chicago peering session with us.
: Is Sasktel being looked at as well? If not - could you disable peering until you get in touch with them? It seems to be the exact same problem.
Have reached out to Sasktel to see what we can do - stick tight!
: Can you tell me if there is anything going on with AT&T. Are you guys waiting for them or do i need to peer??? please help please
AT&T should be coming online in a few weeks, deal is being finalized. Apologies - they have taken quite some time to come to the table.
: Does this include Alaska players? Please don't forget about us.
We're working with our Alaskan partners are best as we can to optimise the route to Chicago, but the increased distance to the servers is the main issue at play here.
: > [{quoted}](name=Riot Foro,realm=NA,application-id=osqw6G4M,discussion-id=PZclbVoE,comment-id=0353,timestamp=2015-08-27T00:32:31.347+0000) > > Currently, we peer with Shaw in Seattle, which routes all Shaw traffic there first before going on Riot’s dedicated network - even if that isn’t the shortest path possible. We’ve heard from a lot of players in Alberta who are being directed to Seattle and then being directed to Chicago. Check out the image below: > > http://i.imgur.com/5YHRVXl.jpg > Will these be just fixes for Shaw consumers within Alberta or will areas of Shaw consumers within Winnipeg,MB be fixed as well?
This should help Shaw users everywhere (yep, including you!) - was just using Calgary as an example.
: Hi, is 80 ping from Arizona with CenturyLink/Qwest DSL normal? I noticed that Pobelter has 65 ping from LA, and I imagine (although I might be wrong) that my ping should be lower or at least similar to Pobelter's considering that Arizona is closer to Chicago. I would just like to know if I can expect my ping to lower in the future. :) I submitted my logs through the tool if that helps at all.
> [{quoted}](name=BABYSTEALER420,realm=NA,application-id=osqw6G4M,discussion-id=PZclbVoE,comment-id=0361,timestamp=2015-08-27T01:44:20.482+0000) > > Hi, is 80 ping from Arizona with CenturyLink/Qwest DSL normal? I noticed that Pobelter has 65 ping from LA, and I imagine (although I might be wrong) that my ping should be lower or at least similar to Pobelter's considering that Arizona is closer to Chicago. I would just like to know if I can expect my ping to lower in the future. :) > I submitted my logs through the tool if that helps at all. Arizona is a tricky one - even though you're physically closer to Chicago than Los Angeles where Pobelter is, ISPs like to route their traffic to Los Angeles to reach the greater Internet rather than to the east. This is what's happening to you and many others in Nevada/Arizona etc. We're working with ISPs in the area to try and get you guys to our Denver or Dallas locations instead.
: Hey guys I have suddenlink in amarillo, texas. My ping has increased from 67 to 122 with this move which I know isn't right. I submitted your network log and it's routing me through phoenix and san jose then over to chicago? Any idea why?
We're looking into routing issues with Suddenlink - they're being a bit slow to respond. Did you send a support email to Suddenlink? This may help them engage us. We have a peering session with Suddenlink in Dallas, you should be routing through here.
: Is Charter Communications an ISP you are taking a look at? I know you are peered with them but I'm getting 80+ ping from DFW in Texas while people with Verizon are getting 30-40.
Will look in to this - was not aware. ty
: Hey RiotForo, thanks for the update! I know a lot of people are in the same boat as me and play on the NA server from England, due to having mostly American online friends. After the server change, ping has decreased for a number of people. However one of the biggest ISPs, Virgin Media, has had no ping decrease to any of its users across the country, as far as I'm aware, which must mean their path hasn't changed. Would I also be able to contact my ISP and reccomend peering with you? I know this isn't a high priority for Riot NA, yet is there a possibility to contact Virgin Media?
This isn't a direct priority of what we're trying to here in NA, so we didn't take into account the potential fallout from UK ISPs other than "well, servers are getting closer, so...". I'll have a look what we can do for you.
C9 Sheep (NA)
: > [{quoted}](name=Riot Foro,realm=NA,application-id=osqw6G4M,discussion-id=PZclbVoE,comment-id=0353,timestamp=2015-08-27T00:32:31.347+0000) > > Hey all, > > We’re constantly working with ISPs to ensure that you have the most optimized path possible to our game servers through peering. Even though we have peering agreements with ISPs, there can be issues where the ISP doesn’t enable peering on their end or the peering becomes inefficient. A relevant example is Shaw, whom we’ll focus on for this post. > > Currently, we peer with Shaw in Seattle, which routes all Shaw traffic there first before going on Riot’s dedicated network - even if that isn’t the shortest path possible We’ve heard from a lot of players in Alberta who are being directed to Seattle and then being directed to Chicago. Check out the image below. > > http://i.imgur.com/5YHRVXl.jpg > > We contact all peered ISPs (including Shaw) in an attempt to ensure that they’re correctly routing to Chicago before the move. However, it can sometimes take time for ISPs to respond back to us (anywhere from 20 minutes to days or even weeks). > > In the case of Shaw, players were actually having a more negative experience on our peering network than they would on public internet. In situations such as this, we will consider disabling peering with that ISP if we determine this will improve the experience for players on that ISP overall. We will continue reaching out to these ISPs to hopefully enable peering again. > > ***Fortunately, Shaw has responded to us and are actively working with us to resolve any peering/routing issues.*** If all goes according to plan, this should be resolved shortly, and should look like this: > > http://i.imgur.com/xYoDxur.jpg > > If we experience a similar issue with another ISP, and have to remove our peering with them, here is what all of you can do to help us get a resolution ASAP. > > Call your ISP or send them a support ticket and let them know the following: > > * You are having a poor experience playing League (Riot Games) from your geographic location. > > * Make sure to attach the file created from the Log Gathering Tool that shows your routing > > * Ask them to peer with us, and provide our [peering policy](http://www.riotgames.com/peering-policy) (this is especially crucial for smaller ISPs who may not have heard of Riot Games/League of Legends) > > We’re also contacting ISPs on a constant basis, so this will help us get the attention of ISPs from both ends. I'm in Alberta as well but on Telus and I'm being routed through Santa Monica first instead of Seattle I'm pretty sure. This exact thing happened to me a couple months ago even before the servers moved (wonky routing) and after contacting a Rioter in networking it was resolved within almost 24 hours so I'm just curious how hard exactly is it to fix a problem like this ?
The hard part is gathering evidence and identifying the problem, the fixes are usually quite simple. Telus (we've reached out to btw) I believe is suffering the same issue as Shaw, Sasktel, even Rogers in some cases. I'm sure there are other ISPs with these kinds of issues too that we will be able to identify in the coming days. As I highlighted above, these Riot <> ISP communications can sometimes be very speedy, but sometimes there are delays. We'll do our best to keep everyone updated as we identify more issues and fixes.
: This sounds like great news. Will this solution also be come to players in Manitoba? We're having the same issue here.
Yep - we're working with all of our Canadian partners to ensure your game traffic is flowing the right way. Takes a little time for our data to come through to highlight these problems, but once we have all the data we're getting in touch with your ISPs immediately.
: Chicago Connection Clinic Megathread [Closed]
Hey all, We’re constantly working with ISPs to ensure that you have the most optimized path possible to our game servers through peering. Even though we have peering agreements with ISPs, there can be issues where the ISP doesn’t enable peering on their end or the peering becomes inefficient. A relevant example is Shaw, whom we’ll focus on for this post. Currently, we peer with Shaw in Seattle, which routes all Shaw traffic there first before going on Riot’s dedicated network - even if that isn’t the shortest path possible. We’ve heard from a lot of players in Alberta who are being directed to Seattle and then being directed to Chicago. Check out the image below: http://i.imgur.com/5YHRVXl.jpg We contact all peered ISPs (including Shaw) in an attempt to ensure that they’re correctly routing to Chicago before the move. However, it can sometimes take time for ISPs to respond back to us (anywhere from 20 minutes to days or even weeks). In the case of Shaw, players were actually having a more negative experience on our peering network than they would on public internet. In situations such as this, we will consider disabling peering with that ISP if we determine this will improve the experience for players on that ISP overall. We will continue reaching out to these ISPs to hopefully enable peering again. ***Fortunately, Shaw has responded to us and are actively working with us to resolve any peering/routing issues.*** If all goes according to plan, this should be resolved shortly, and should look like this: http://i.imgur.com/xYoDxur.jpg If we experience a similar issue with another ISP, and have to remove our peering with them, here is what all of you can do to help us get a resolution ASAP. Call your ISP or send them a support ticket and let them know the following: * You are having a poor experience playing League (Riot Games) from your geographic location. * Make sure to attach the file created from the [Log Gathering Tool](http://na.leagueoflegends.com/tools/network-logs) that shows your routing * Ask them to peer with us, and provide our [peering policy](http://www.riotgames.com/peering-policy) (this is especially crucial for smaller ISPs who may not have heard of Riot Games/League of Legends) We’re also contacting ISPs on a constant basis, so this will help us get the attention of ISPs from both ends.
Zundur (NA)
: Just wondering if anyone can explain to me what's happening in this tracert. I ran it 3 times for consistency. It seem's like everything is going fine. Then it times out and the ping sky rockets.
We're receiving your ISPs traffic in Seattle! Let me work out why and try to fix that.
: > [{quoted}](name=Riot Foro,realm=NA,application-id=osqw6G4M,discussion-id=PZclbVoE,comment-id=00400001,timestamp=2015-08-25T16:31:52.132+0000) > > Looking in to this - are you able to supply me your Verizon support ticket? > > A traceroute to 192.64.131.3 would be awesome too, if you're able to supply. > > Can you post your info and results here? http://boards.na.leagueoflegends.com/en/c/help-support/hx1zPjTg-verizon-east-coast-reports-of-packet-losshigh-latency I should just post the support ticket # and the traceroute in the thread?
If you're still reading - can you test now? Have found and isolated a possible issue.
: So I submitted a ticket to verizon tech support and what they told me is that Verizon Fios East coast packet loss is all on your guys end Aleem(12:14:52): We have received many customers with the same issue. Aleem(12:15:07): We have already checked upon this with our network team. Aleem(12:15:27): There is no issues with Verizon network, this is something to do with the Game servers. Aleem(12:15:52): We also have information that there was a server switched through game server admin. Aleem(12:16:02): So this could be an issue with the server change that has happened. Aleem(12:16:23): Would suggest you to check upon this with Game server administrator. What do I do Riot? I was getting packet loss prior to the patch already with Fios but the game is now unplayable even with 30 ping. My guy is skipping around like he's on ice skates every 5-10 seconds
Looking in to this - are you able to supply me your Verizon support ticket? A traceroute to 192.64.131.3 would be awesome too, if you're able to supply. ~~Can you post your info and results here? http://boards.na.leagueoflegends.com/en/c/help-support/hx1zPjTg-verizon-east-coast-reports-of-packet-losshigh-latency~~ **Deleted the thread - think I've fixed it. Please confirm if so!**
Dravia (NA)
: What IP prefixes (CIDR) do you guys use for your severs? I need them so I can add them to my routing table and bypass my server in Kansas City. This will automatically fix some of the issues I am having with the current routing. Edit: Considering current routing gives me 120~ ms and bypassing would give me 45~ this is significant. Especially since routing through Kansas City for some reason goes through Seattle, WA.
192.64.170/24 192.64.171/24 192.64.172/24 192.64.173/24
: What about ISP peering with Surewest/Consolidated Communications? I've asked on previous thread and sent in a support ticket and still no answer.
Hey there, Investigated - Can't find a location to peer with them (perhaps they do not peer). They do use Level3 and Cogent as upstreams, which we share peering with. Are you able to reach out to your ISP support team and ask if they are capable of peering with us? Our public information is on PeeringDB. http://www.peeringdb.com/private/participant_view.php?id=5918
Dravia (NA)
: The ISP I have is NuLink, if you want I could show you a tracert. Edit: Though if it's possible for you guys to see my connection from your end then it will look strange, but the issues rises with the routing.
Can you paste your traceroute results here? Direct peering doesn't look possible with your ISP, however this should be something we can steer to a better point for you and other players on your ISP.
: I have been in a support ticket asking about my ISP in Michigan. And figured I would ask and maybe be lucky to find others. But doubt it. So my ISP is D&P Communications in south Michigan. For me, this is the only cable company that we are allowed because no one else wants to pay them to run their lines through D&P's lines. So we are stuck with them besides satellite. And right now I get roughly the same ping to Chicago servers that I do to Portland. Roughly 74-80ish. So helping me in my support ticket is/was Azreal. I did everything she wanted me to try out/do to try to help fix my ping to the Chicago servers. But nothing really helped decrease my ping. Switching DNS, disabling IP Helper, and a couple other things. So I contacted my ISP to see if they could do something about it. They pinged the servers and got the same as me. Then one of their tech guys did it from his house. Same ping. So then got told that it is roughly 38ish to the servers and same for it to come back to me. So it's roughly the 74/76 ping. They said there were quite a few others not happy about it. But didn't give me a number. I know no one probably cares, but what else can I do? I've been trying everything I can on my end. Have the highest speeds from my ISP, I am directly plugged into my router, I did everything support told me to do. Like I just want to know what else I can do.
Hi there! After some investigation, I can give you a brief rundown. - Your ISP doesn't appear to have a peering presence anywhere that Riot can connect with them - D&P appear to use Hurricane Electric as their sole upstream, who we do selectively peer with at some points - Can you reply with a traceroute to 104.160.131.3? I might be able to tweak some things once I see your path. Thanks!
: Wait, so I live in Topeka KS (~500 miles away from Chicago (~1800 miles from Portland)) and when I use the cmd ping to the new server it says I have 83 ms. But when playing in game on the Portland servers it says I have 95 ms. Am I really only going to go down 12 ping? When I do a speedtest to any Chicago server/ISP it says I have 25-50 ping?
Can you provide me a traceroute to 104.160.131.3? I'll be able to see your path and work out what's going on. How-to Traceroute: https://support.riotgames.com/hc/en-us/articles/201752674-Network-System-and-League-of-Legends-Logs#wq2
: as for Cox, Verizon and other companies that are not peer with Riot Games, will those people who have those companies will be affected in any such way?
Players on ISPs that we don't currently peer with will still feel the effects of the physical server location move to Chicago (if you're getting closer, your latency should become lower). The main thing we lose is the full control to steer and optimise the traffic flow from those ISPs to the same extent that we are able to with ISPs that we do have peering agreements with.
: how long will it take to peer with the rest of the internet companies?. On my opinion the move was to make the game play better for everyone why make the move if you are not done peering with the rest of the internet companies seems a bit unprofessional in that sense.
To put this in context - we've gone from peering with zero ISPs a year ago, to the list we have today. Each little bit has been an attempt at improvement from that point. Some agreements have taken longer than others, and while the excuse "it's just business" is a really lame one, it's the one we're getting from some of these hard-to-get ISPs.
: ***
Can you provide a traceroute to 104.160.131.3?
Nahara (NA)
: Out of curiosity, is the Portland location gonna be a hot, warm, or cold site? Took a class in disaster recovery recently, so I'm curious.
Warmish. Lights are on, will require some emergency routing work if Chicago fell off the map for some reason - though if that happened, I think the world would have bigger problems!
Strux (NA)
: I look at your ISP's list and you have 3 different bell's for ISP'S im with bell canada which it says has currently hit a snag will that affect me in any way?
You'll be able to play just fine! We just don't have a direct peering agreement with Bell at this stage. Your "test" latency to the new location will be a fairly accurate representation of what you'll get in game.
pnilly (NA)
: what ms should i expect in San Diego on cox in a couple weeks?
It's difficult to say until we've turned the port up - we can't say for sure right now.
: Still a little bit bummed that Verizon is being put into effect later on...
Us too - we've been pushing Verizon for months. Almost there.
Quality (NA)
: Question about at&t, if I'm pinging around 52-53 to the new server location, how much higher is it going to be in the actual game? Like is it still going to be in the 100s if I currently am getting 110-120?
To further add to this - what you're pinging to the new location is going to give you the best indication what your in-game latency will be. (52-53ish is your future)
: City/State/Location: Selkirk/Manitoba/Canada ISP: Manitoba Telecom Services (MTS) Type of connection: Broadband Approx date when you first started seeing an increase in ping: a couple weeks ago, been searching aimlessly for a reason couldn't find one
> [{quoted}](name=Tuskcrusher,realm=NA,application-id=osqw6G4M,discussion-id=0KkE1dFw,comment-id=00e2,timestamp=2015-08-12T16:08:12.375+0000) > > City/State/Location: Selkirk/Manitoba/Canada > ISP: Manitoba Telecom Services (MTS) > Type of connection: Broadband > Approx date when you first started seeing an increase in ping: a couple weeks ago, been searching aimlessly for a reason couldn't find one Still working on a way to make MTS happen - bear with us.
: Suddenlink was fixed for me and my ping is lower than my previous average before this recent peering hiccup. Good shiet.
> [{quoted}](name=1 800 TILTING,realm=NA,application-id=osqw6G4M,discussion-id=0KkE1dFw,comment-id=00d5,timestamp=2015-08-12T05:20:59.717+0000) > > Suddenlink was fixed for me and my ping is lower than my previous average before this recent peering hiccup. Good shiet. Glad it helped - Suddenlink in the south came online late last night, and it appears it had the desired effect instantly.
: Any update on suddenlink yet? Still having horrible routing issues with them? Please respond
> [{quoted}](name=Azir Mid Plz,realm=NA,application-id=osqw6G4M,discussion-id=0KkE1dFw,comment-id=00ba,timestamp=2015-08-11T22:18:37.460+0000) > > Any update on suddenlink yet? Still having horrible routing issues with them? Please respond Just waiting for them to turn up their end in Dallas - hold tight!
: Hi Riot, with Frontier buying the Verizon FiOS connections in Cali and Florida earlier this year, shouldn't we have been connected to your POPs at these locations due to your agreement with them? Right now they have us running our connections in Tampa Bay from Miami to DC to Georgia and then out into the distance. Any reply would be nice!
> [{quoted}](name=CraCkWaCk,realm=NA,application-id=osqw6G4M,discussion-id=0KkE1dFw,comment-id=0083,timestamp=2015-08-08T17:37:55.741+0000) > > Hi Riot, with Frontier buying the Verizon FiOS connections in Cali and Florida earlier this year, shouldn't we have been connected to your POPs at these locations due to your agreement with them? Right now they have us running our connections in Tampa Bay from Miami to DC to Georgia and then out into the distance. Any reply would be nice! I don't believe the deal is 100% through yet - but both companies expect it to be cleared sometime early 2016, with the networks merging shortly after. Prior to that, our Verizon circuits should help once they come online.
: City: Boulder, Colorado ISP: Comcast Type of connection: Broadband? It is a wired connection and I get 105 down 10 up. Approx date: 5 months ago. I always got 59 ping for all of last year. However I noticed that in March or April (can't remember exactly when), Comcast decided to double my speeds for no reason and for free. Obviously I was ecstatic about it however the side effect of it I noticed is that my ping went up to a stable 70 where it has been for the past couple of months. That is until 2 days ago when I noticed I was getting 43 ping. That was awesome. I think that you guys just finished a PoP in the Denver area and Boulder is roughly 30 minutes away so it helped a lot. Now however ever since around 1 AM 8/7/15 I noticed that my ping is back up to 59. Do you have any idea why that could be? Me and my friend are both on comcast and live about 15 minutes away and noticed the same thing. Down to 43 ping, now back to 59 ping. I just ran a tracert to one of the ip addresses someone used to do a tracert (192.64.170.252) and I noticed that it hops from me to denver, but instead of getting in the stream there, it directs to dallas, tx and then goes to the riot direct line. http://i.imgur.com/yqEerHB.png
> [{quoted}](name=An Okay Player,realm=NA,application-id=osqw6G4M,discussion-id=0KkE1dFw,comment-id=007e,timestamp=2015-08-08T07:10:45.414+0000) > > City: Boulder, Colorado > ISP: Comcast > Type of connection: Broadband? It is a wired connection and I get 105 down 10 up. > Approx date: 5 months ago. > > I always got 59 ping for all of last year. However I noticed that in March or April (can't remember exactly when), Comcast decided to double my speeds for no reason and for free. Obviously I was ecstatic about it however the side effect of it I noticed is that my ping went up to a stable 70 where it has been for the past couple of months. > > That is until 2 days ago when I noticed I was getting 43 ping. That was awesome. I think that you guys just finished a PoP in the Denver area and Boulder is roughly 30 minutes away so it helped a lot. > > Now however ever since around 1 AM 8/7/15 I noticed that my ping is back up to 59. Do you have any idea why that could be? Me and my friend are both on comcast and live about 15 minutes away and noticed the same thing. Down to 43 ping, now back to 59 ping. > > > I just ran a tracert to one of the ip addresses someone used to do a tracert (192.64.170.252) and I noticed that it hops from me to denver, but instead of getting in the stream there, it directs to dallas, tx and then goes to the riot direct line. > > http://i.imgur.com/yqEerHB.png Hey there - have a quick answer for this one! We indeed did turn our Comcast port up in Denver, however soon afterwards we noticed there was a serious issue with this new service. Comcast were able to identify a problem with their equipment, and we have shut our port down until they've fixed it. Should be back up in the coming week or two!
: NA Server Roadmap Update: Chicago, Here We Come
Quick update regarding Suddenlink: We've turned up our connectivity with Suddenlink, however we have two more mutual sites (Dallas and Ashburn) that should be coming on line some time next week!
: Amarillo, Texas, USA Suddenlink Broadband Just started the increase in ping today. Has shot up from a steady 67 to a steady 94 now? Any Idea what's going on since last night and why it changed so much?
> [{quoted}](name=Azir Mid Plz,realm=NA,application-id=osqw6G4M,discussion-id=0KkE1dFw,comment-id=004d,timestamp=2015-08-07T16:11:05.524+0000) > > Amarillo, Texas, USA > Suddenlink > Broadband > Just started the increase in ping today. Has shot up from a steady 67 to a steady 94 now? > Any Idea what's going on since last night and why it changed so much? We actually turned up peering with Suddenlink yesterday evening - it appears they're doing something unorthodox with their routing. Can see your problem - reaching out to them to let them know.
: City/State/Location: Winnipeg, Manitoba, Canada ISP: MTS (Manitoba Telecom Services) Type of connection: Broadband Approx date when you first started seeing an increase in ping: 3 months ago Are you going to have talks with MTS for better connection? please answer. i have been asking since yesterday.
> [{quoted}](name=1nd Place,realm=NA,application-id=osqw6G4M,discussion-id=0KkE1dFw,comment-id=004c,timestamp=2015-08-07T15:35:45.160+0000) > > City/State/Location: Winnipeg, Manitoba, Canada > ISP: MTS (Manitoba Telecom Services) > Type of connection: Broadband > Approx date when you first started seeing an increase in ping: 3 months ago > > Are you going to have talks with MTS for better connection? > > please answer. i have been asking since yesterday. Hey there, Sorry for not getting back to you! We're attempting to reach out to MTS to see if they'd like to peer with us; they don't have a lot of publicly available info out there for us to contact them it seems. We'll keep trying!
: Think this is it
> [{quoted}](name=bunny1102,realm=NA,application-id=osqw6G4M,discussion-id=0KkE1dFw,comment-id=000300000001000000000000,timestamp=2015-08-07T00:22:15.267+0000) > > Think this is it Hey there - this log appears to be a year old. Do you have anything in the same folder with the filename starting in 2015-06-08 or similar?
StableW (NA)
: So since my ISP is AT&T and you're not currently partnered with them, does that mean that when you do partner with them my ping will be better? Or what exactly does that mean?
> [{quoted}](name=StableW,realm=NA,application-id=osqw6G4M,discussion-id=ZwVkoboV,comment-id=0069,timestamp=2015-08-07T00:15:16.042+0000) > > So since my ISP is AT&T and you're not currently partnered with them, does that mean that when you do partner with them my ping will be better? Or what exactly does that mean? By peering with ISPs we aim to both optimise latency, and minimise packet loss and variance. When your ISP partners with us, you should see these benefits.
Delílah (NA)
: > [{quoted}](name=Preeti,realm=NA,application-id=osqw6G4M,discussion-id=ZwVkoboV,comment-id=00050000,timestamp=2015-08-06T22:06:53.503+0000) > > Who's your ISP? Windstream. I've given up hope of anything positive happening with this company so if there is no partnership then I won't be surprised in the least.
> [{quoted}](name=PineAway,realm=NA,application-id=osqw6G4M,discussion-id=ZwVkoboV,comment-id=000500000001,timestamp=2015-08-06T22:37:52.741+0000) > > Windstream. I've given up hope of anything positive happening with this company so if there is no partnership then I won't be surprised in the least. Hi Pineaway, We've been in discussion with Windstream trying to make the deal agreeable, but we've had no recent response from them. It may be beneficial if you and other Windstream players email Windstream support highlighting issues playing LoL, so we have a two-pronged approach.
Show more

Riot Foro

Level 30 (NA)
Lifetime Upvotes
Create a Discussion