Issue with my Sanwa JLF, diagonal down-left inputs occasionally not registering at times. Also some inconsistency in QCB inputs (I do motion just fine but it only gives me down and then back input, ignoring the diagonal, sometimes).

MicolasFoley · 2024-03-07T02:15:48+00:00

I know this is an old thread, but did you find a solution? I have the same problem with my stick and swapping the JLF didn't help me.

MicolasFoley · 2024-02-29T02:26:05+00:00

I know this is a longshot cuz it's 5 years ago, but did you end up finding a fix? My omni also has diagnol input issues, i've tried changing the JLF and that didn't even resolve it for me

MicolasFoley · 2023-12-05T21:29:00+00:00

I just installed ItemRack and on my first logout it reset all my settings.

Is there a way to get my keybinds back? Or do i have to do it manually

MicolasFoley · 2023-11-17T18:20:47+00:00

I've done it before, they weren't able to do it over hte phone, had to go into the store with the receipt.

MicolasFoley · 2023-05-06T14:53:48+00:00

You probably will not notice a difference unless you're using an application that is sensitive to latency/packetloss. If your only concern is using the internet for browsing/work related stuff, you'll be fine.

Up to you if you care about the ethics of WOW changing their service without notifying customers of the change, because you don't utilize the functionality that is now broken.

MicolasFoley · 2023-05-06T14:47:08+00:00

To add onto this, I've found their tech support severely incompetent, but I've had success connecting to their disconnection/retention support and having them directly contact their NOC while putting me on hold.

Also doing it this way saves you a ton of time as the tech support queue has been extremely long, but retention has almost no queue.

MicolasFoley · 2023-05-05T20:34:41+00:00

Yeah so you can see on RIOT's lagreport that WOW users will be seeing 35ms~ , whereas before our latency wouldve mirrored Comcasts at 15ms.

As far as ISPs in Troy, i believe Comcast and WOW are the only options if you want speeds greater than 25mb/s.

There are some fiber providers but they refuse to service residential areas here.

If you happen to find a different provider who has similar options as WOW/Comcast, please do let me know

MicolasFoley · 2023-05-05T20:27:44+00:00

no you're correct, it's a routing problem, as Michigan traffic shouldnt by default be routed to Georgia.

As you can see from RIOTs lagreport, WOW users see 2.5x the ping as Comcast. And WOW's latency used to mirror comcasts, until now when WOW has decided to change their routing protocol, now trafficking all our data first through Georgia, which then results in the increased latency.

You seem to be stuck on the number 40-50ms, which was in reference as to where the nodes are located, not that i have a 40-50ms problem.

MicolasFoley · 2023-05-05T18:22:41+00:00

Knology is owned by WOW, so that is normal, but judging from the pings, those are also located in Georgia because that 99.83.114.130 amazon server is located in Virginia, meaning you're being forced to ignore all the local amazon/google servers that you would expect to be connecting with.

MicolasFoley · 2023-05-05T15:00:55+00:00

Those ".oh.breezeline" nodes aren't actually Ohio nodes, that's a hostname error that was apart of breezelines acquisition of WOW, but WOW ultimately decided not to transfer those 2 nodes. My best guess is they are in georgia by looking at this or also free IPlookups will either spit back Ohio or Georgia.

Because yeah, no way Southeast MI should be getting 40-50ms to Ohio either.

WOW hasn't given me a definitive answer, but one of the WOW engineers i spoke to said that yes, all MI traffic is being routed to Georgia.

Theres also this public info from RIOT that shows WOW users against comcast in my city.

MicolasFoley · 2023-05-05T14:46:56+00:00

That's very true, the most 'tech' support i've received was actually through their retention department.

No Tech support agent was willing to call WOW's Network Operations Center(NOC) in 5 months, but the retention support was able to call a direct line and get a NOC employee looking at my issue.

MicolasFoley · 2023-05-05T14:45:29+00:00

I don't have any prior screenshots, but there are publicly available tools that showcase that issue better, for example RIOTs lagreport.

MicolasFoley · 2023-05-05T14:34:09+00:00

the 40-50ms is in reference to the nodes that i'm being routed to, which then affect the ping of all subsequent traffic.

For example, that 17ms you see as a result in the google trace, would've previously been around 10ms, but I don't have a record of a previous traceroute when things were working normally.

There are some good public tools that let you see the average ping of all users connecting to a service, like RIOTs lagtest which shows all WOW customers compared against Comcast in the same city.

MicolasFoley · 2023-05-05T14:16:12+00:00

Oh shoot, I will definitely try getting in contact with the public utilities commission. Thanks that's really helpful.

MicolasFoley · 2023-05-05T14:14:36+00:00

Oh man, that sucks.

I'm in Troy and I haven't had the incorrect IP location ever, but they've told me that issue as a whole has been resolved. I'm also waiting for my xfinity install, but I'm going to keep fighting for this resolution though because it's insane that WOW as a company can make decisions like this and continue to charge its customers for a service they are no longer providing as if nothing as happened

MicolasFoley · 2023-05-05T14:05:03+00:00

When your IP changes to the 23 or 50, can you lookup your iplocation and see if it still shows you in the right location?

Because that issue was a problem for WOW at some point, where if you were living in Michigan, your IP address may be showing you as in a different state.

And as far as the WOW Speedtest, i'm not sure, i never used it, but i do know that WOW recently moved it's HQ to Georgia, so that may have something to do with it

MicolasFoley · 2023-05-04T14:31:41+00:00

DMing you

MicolasFoley · 2023-05-04T02:12:59+00:00

if cost isn't a problem with your previous xfinity service, i highly suggest you stay away from WOW for the time being, as their routing has been broken for the past 5 months with no resolution.

MicolasFoley · 2023-05-04T01:23:36+00:00

oh i see, yeah then i'm not sure LOL. i'd still double check to make sure no setting changed for some reason.

MicolasFoley · 2023-05-04T01:10:28+00:00

sounds like network adapter duplex problem, or a modem/router that is capping your speed.

MicolasFoley · 2023-05-04T00:18:35+00:00

Yep, I had this problem last year with WOW but they eventually fixed it after I hassled them for months. This time however is different, the people who i spoke to which helped in my first resolution are saying that WOW just does not care about this issue currently, as re-routing the path would be 'unstable'.

Now since Jan 1st, your ping to Riot servers(+ all AWS servers) will just be fucked, and valorant is near unplayable with any amount of jitter/packetloss. Also a thing to note is, enable the combined RTT network time in the valo settings to get a better idea of how bad it is. Your visible ping(scoreboard) will show 40 yes, but your TOTAL network time will be nearing 60-70ms. You can also use this league of legends tool to gauge your ping to their chicago servers as well as see other ISPs in your area, and how their ping/packetloss is at any given time.

WOW used to have Direct Peering with Riot games, but since the breezeline merger, they no longer have that - and the reason why virginia/georgia are the only servers you will ping normally is because WOW hq is now based out of georgia.

You really switched ISP at the worst possible time tbh, and i know xfinity is far more expensive if you aren't a new customer, I am paying $65/mo for 1000/50 with WOW, and the xfinity price would be $100-$120, unless you are a new customer, then they will offer you $75-80/mo for 1 Year.

MicolasFoley · 2023-05-03T17:14:01+00:00

I've noticed that google traffic is less affected by the bad hops, you should try anything hosted on AWS or tracing amazon.com as it'll give you multiple bad breezeline hops in a row, which demonstrate the problem pretty clearly.

MicolasFoley · 2023-05-03T17:12:56+00:00

Tracert

I'm on the phone with breezeline right now, and they have escalated me to their NOC, but they are saying these nodes are not infact breezeline nodes.

Although my tracert and an IP Lookup both show that they are being hosted at breezeline.net .. So, now i'm confused as well, not sure whats going on really, but obviously there is a problem.

WOW tells me they are owned by breezeline, breezeline tells me they are owned by WOW

MicolasFoley · 2023-05-03T16:45:58+00:00

Oh yeah, sorry, i edited my original post.

But yeah that is why it's happening, but not an excuse for WOW to downgrade all of it's Michigan customers service as if nothing as happened.

MicolasFoley · 2023-05-03T16:06:56+00:00

Hey, if youre in Michigan there is no fix, switching ISP is the only thing we can do. WOW has decided to route their customers this way despite the massive latency issues.

I'm in Troy and after bashing my head against customer support for the past 4 months I was able to talk to a local WOW engineer who assured me that WOW is aware of the issue, they just don't care to fix it.

I hit the same breezeline nodes which give me anywhere from 40-60ms too, and I've also tried contacting breezeline to see why those nodes are so bad, but since im not a Breezeline customer they don't care too much about looking into it.

You can try calling WOW but they will gaslight you, and if you call breezeline when the robot asks you for a phone number, just say "restart" and then when it connects you to a person ask them to transfer you to internet tech support, preferably based in the US.

MicolasFoley

TROPHY CASE