Boards›Report a Bug

Cincinnati Bell Ping Issues Patch 9.1

Renegadz·1/12/2019, 10:56:28 PM·5 votes·3,074 views

Yo. So I don't know if this post is allowed here, but I'm desperate at this point.

So ever since the most recent patch, I have been getting around 101ms ping.

I used to get around mid 40's ping last patch.

And since the server move, to several months back, I would get around 18-19ms ping.

My Specs:

  • Live in Cincinnati, OH
  • Have Cincinnati Bell Fioptics(Fiber)
  • Have a plan with 750mbps down, 200mbps up
  • Using a Cat 6 ethernet cable directly to my router, which then passes through another Cat6 ethernet cable directly to my ONT.
  • Speedtest result

So in an effort to remedy my issue, I

  • completely factory reset my router.
  • I flushed and changed my DNS to several different providers, from cloudflare to Google
  • I reinstalled my network drives
  • used Riots Hextech Repair Tool
  • Made sure I wasn't using a VPN/Proxy
  • and nothing changed. Still 101ms ping.

So i ran a tracert using the command line, and a software called Visual Traceroute. I used Riots suggested IP address for the game server as of the server move,
104.160.131.1 and 104.160.131.3 Here's my results

For some reason it's routing me to California. Had a couple of my friends use the tool, and it routed them there too. But that seems to not be the issue. My friends ping is still hanging in the mid 40's, and they live in Akron Ohio and have similar internet plans through spectrum. It seems that when their internet hit's riot servers it pings them back at around 46-48ms ping. When my internet hits Riot it pings me back at 98-101ms ping.

So following more of Riots advice, I used their"lag report" tool.

Here are the results According to Riots tool:

  • 30 days ago my ping or latency was 28ms
  • The last 7 days my ping has been around 42ms
  • Today, my ping is around 87ms
  • So, it would seem that somewhere along the way, a patch created an issue where my latency or ping went from 28 to 42, and then the most recent patch 9.1 spiked my ping to 87ms(101ms real time).

So just to make sure it wasn't on my end, or my isp's end, I contacted my ISP. The online contact referred my case to a Network Supervisor who called me. We had a nice chat, and the guy said that they have gotten an influx in calls recently about league of legends ping spikes. He said that they have looked into it, and it was on Riots end with the most recent patch. He said that everything is fine up until it hits Riots servers, in which the latency/ping spikes and lags before being sent back to my computer. This makes sense with the tracert I did, because the ping only spikes once it hits Riot's servers.

Can a red flair please help, or at least have someone look into it? I can't be the only one having issues with it, and I have literally done everything I possibly could on my end, except wait and pray that the next patch fixes the issue.

Thanks for taking the time to read my post!

7 Comments

BigEKnows1/13/2019, 5:06:10 AM4 votes

We also live in Cinci and use Bell Fioptics. This issue has popped up as well. We used to get 14 in game ping and then it gradually started raising up to an average of 34 the last few months. While we enjoyed the low 14 ping the raise to 34 was not an issue but now since the last week or 2 it has been constant 101 in game ping as well. This is for sure a Cincinnati bell routing issue that needs to be resolved by the network admins at Cincinnati Bell. An update to the league client should have no impact on networking like this. Cincinnati Bell has been known to pull these shenanigans in the past and it usually takes a month or so to get resolved.

Inigo Monteemo1/13/2019, 12:23:15 AM3 votes

I've had a similar issue post 9.1. My ping averaged 17-18ms around a month ago and then began to average around 45ms. After the patch, when playable, my ping is over 100ms. The last couple of days I have gotten an error after champ select that says I am unable to connect and to check my internet connection. When I opened a ticket with Riot's Support team, they said that it seems like it is an issue with my ISP (Cincinnati Bell). I called Cincinnati Bell and they said that they "refreshed some stuff". The error went away for a couple of days, but returned today and now the game is unplayable. I have friends that live close to me that also use Cincinnati Bell and have the same issue. Spectrum users in my area do not have this issue and their ping is around 25ms.

BRICKH0USE1/13/2019, 3:02:21 AM2 votes

For what it's worth, I am also having this issue and can trace the server ping similarly. I was already on the brink of switching off Cinci bell so unless this gets resolved I'll probably be moving over to spectrum.

WhatUpImTopher1/13/2019, 7:09:18 PM2 votes

I just google searched "cincinnati bell riot games" and came across this. Glad I'm not the only one, although I feel for you all. I am also living in Cinci and use Cincinnati Bell Fioptics. Starting on Friday (1/11) my ping went from 17ms to 101ms. This sucks. Make sure you guys contact their support. Hopefully if enough of us do, they will get his issue resolved quickly. Feelsbadman.

Here's a response I received from a member of the support team at Riot Games, in case you guys want more information when reaching out to Cincinnati Bell:

"Hey there man! Romulus is out on his weekend so I hope you don't mind me stepping in here! What he mentioned was right and seems to be pretty on par with what we have been seeing with Cincinnati Bell. On all three tests our connection jumps up to 370 ping right when it starts hitting their servers. Unfortunately there isnt to much we can do about it as they are privately owned servers"... "I will leave the information for you to reach out to Cincinnati Bell with!

We are seeing increased ping whenever our connection to the servers in Chicago hit node ph-esr1-72-49-203-1.fuse.net. This node is showing ping of 370+ consistency and showing packet loss from 0% to 93% in some cases. This node being the first node hit by the player means the connection is showing this packet loss and ping throughout the entire route.

Platypus Player Support"

BigEKnows1/14/2019, 3:09:40 AM2 votes

Just an Update, We now can no longer connect at all to the actual game server. The client lets us but once we start a game we get the error connecting to game service. We now must vpn to our campus in order to play the game. I will be calling them tomorrow asking them why our traffic is being routed to DC before heading ATL before heading to Denver before heading to Chicago. Its hard to believe a T1 ISP can be this incompetent at resolving routing issues.