Forums / Support / Halo 5: Guardians Support

[Locked] Halo 5 Multiple Lag Issue

OP The Muff1n Mon

  1. 1
  2. ...
  3. 48
  4. 49
  5. 50
  6. 51
  7. 52
  8. ...
  9. 68
IM BACK!!!!!

After having around 10 days of solid play time I am again plagued with the same issue.

here are my stats again:
ISP: PLUSNET UK
Line Stats: 70Mbs Down 10Mbs Up
Latency to google.co.uk:15MS
Latency to xbox servers (within xbox settings) 160MS

After applying the port forward and disabling DMZ/UpNp/Game Mode/IDS on my previous router Technicolour TG584 - I had 10 days of solid playtime.

STUPIDLY whilst trying to reboot my router three days ago I clicked RESET. Life hasn't been the same.
After updating the MTU forwarding correct ports on this router - nothing worked.

I decided to use my own router (Linksys WRT54GS with DD-WRT) last night - Same issue.

Im going to go ahead and update the MTU and Port Triggers as described to see how things play out tonight.

I just rang my ISP PLUSNET and they have stated no traffic shaping p2p blocking is going on, interleaving is off and they placed all the blame on Xbox Servers (they even googled and found this thread).

343i haven't inputted anything to this thread to help out the gamers with the issue.

All credit to Bullet / Jlong and others who have spent time looking into this issue.

Guys please private message me, I am no network expert but I could help in any way shape or form in my capacity.
Bullet Lee wrote:
Pyroteq wrote:
It is not the modem, there is no consistency or pattern with the issues and modems. I personally have tried 3 different modems without any success. 343 responded a few days ago that they were actively working with TWC, insert the information they were looking for with some clips to help them out.
Apart from the fact that I actually work in networking and I haven't had a single lag spike in 3 days of testing and the only thing that has changed was my modem...

Perhaps the TWC issue is different but I was having the exact same symptoms as others and a new modem has fixed the issue for me.

What model modems have you tried?
Pyroteq wrote:
Bullet Lee wrote:
Pyroteq wrote:
It is not the modem, there is no consistency or pattern with the issues and modems. I personally have tried 3 different modems without any success. 343 responded a few days ago that they were actively working with TWC, insert the information they were looking for with some clips to help them out.
Apart from the fact that I actually work in networking and I haven't had a single lag spike in 3 days of testing and the only thing that has changed was my modem...

Perhaps the TWC issue is different but I was having the exact same symptoms as others and a new modem has fixed the issue for me.

What model modems have you tried?
Originally I had an older DOCSIS 2 SB5101 that worked fine for a long time. I've had that beat since college and it has held strong. Once the issue cropped up I traded it in for an SBG6580 that drastically reduced my latency to around 20ms to Google and in matches for CS:GO as well as speedtests. Again the issue popped up again and I purchased a Zoom 5345 that is a single function, so no Wifi mumbo jumbo that TWC provided and a highly rated consumer modem. After a day or two it became apparent that it did not fix the problem. I also cultivate the switch farms during the day. I've done it all, its not the home user. I say, hey if you got it working get in as many good matches as you can. I was lucky enough to have a relatively lag free day and at least went from silver>gold. So that is a win.
Just to point out some numbers here, I went through the first ten pages of this thread and here are the numbers (bit fuzzy, was just kind of bored so I didn't go double-check everything):

TWC mentioned as a problem: 55 of 60 times
Comcast: 2
Local: 1
FIOS: 1
Optimum: 1

Gateways/Modems mentioned:
ARRIS/MOTOROLA SURFBOARD 6121, 6141, TG862, TG1672, DG860, TG882, TG852G, CM820
Unknown ARRIS/MOTOROLA SURFBOARD 9 add'l times
Ubee DDW365
Unknown Ubee 2x
Zoom 5345
Netgear CM500, CMD31T, CM400

Prevalence of ARRIS/MOTOROLA is probably due to them being stock for TWC.

Routers mentioned:
Netgear Nighthawk r7000, r7500
Netgear 6300AC
Unknown Netgear 2x
Google OnHub
Apple Wireless Extreme
ASUS RT-N56U

I should also note that several times people stated they "just went out and got X and [he/she/it] was fine forever after!" where X happens to be the very same problem child for several other people.

Locations:
N Virginia
New York
Ohio
Maine
San Diego, California
Kentucky
Washington
Savannah Georgia
Pennsylvania
Wisconsin
Virginia

And then there is also me
TWC
San Diego, California
MOTOROLA SBG6580, then ARRIS DG1670 now using an ARRIS/MOTOROLA SURFboard SB6183 w/ ASUS RT-AC68U.

While it is very possible that the cross linking to this thread occurs primarily in "TWC LAG OMG" threads and therefore it is self-fulfilling that all TWC complaints get piped through here, skewing the information, googling "Halo 5 lag" is entirely TWC threads. As a side note, I did really like how the guy from the UK that posted here said he was fine even with near 200 ping, and how the guy from Australia said his experience matches ours.

That's some killer good ol U.S. internet infrastructure right there.
The same issues apply to me. On MCC and H5.

343 needs to fix this ASAP, although I doubt they will.
More information! I am on a roll here!

I got a few good data grabs (because apparently I am no longer allowed to play Halo 5 at all and for the last three days at no time have I had a lag free game despite having been mostly fine up until Sunday, 01/10/2016).

My router's bandwidth monitoring showed this little gem (though I assume everyone could have just guessed this). You could set a watch to this now.

Traffic to my xbox during happy fun time:
50-300kb up (with random bursts of 600kb-1mb)
400-600kb down

Traffic to my xbox during clock freezing/wall-running spartan badtimes:
5-150kb up
30-50kb down

TL;DR my up and down bandwidth to my xbox seemed to drop by a freaking order of magnitude whenever "lag would happen."

I kept track of my router's active connections as well and they never changed state or anything.

Unfortunately now for me it has become every single match and not just a once or twice a day occurrence.
Here's some traceroutes to the udp connections that were running during the games I played tonight (I am so sorry, my BTB teams. In a 12 minute match I am not lagging for maybe 60 seconds interspersed over the entire duration).

udp HOST 23.96.253.49:30004 ASSURED
udp HOST 40.121.88.202:30001 ASSURED
udp HOST 65.55.158.118:3544 UNREPLIED

traceroute to 23.96.253.49:30004 (23.96.253.49), 30 hops max, 38 byte packets
1 cpe-76-176-176-1.san.res.rr.com (76.176.176.1) 43.066 ms 28.111 ms 27.276 ms
2 tge1-5.crlscaij02h.socal.rr.com (76.166.18.133) 40.742 ms 30.168 ms 45.682 ms
3 agg33.sndhcaax02r.socal.rr.com (72.129.3.98) 30.964 ms 26.827 ms 37.885 ms
4 agg22.tustcaft01r.socal.rr.com (72.129.1.2) 36.805 ms 36.318 ms 24.071 ms
5 bu-ether16.tustca4200w-bcr00.tbone.rr.com (66.109.6.64) 13.562 ms 41.352 ms 39.790 ms
6 bu-ether14.lsancarc0yw-bcr00.tbone.rr.com (66.109.6.4) 51.447 ms 52.017 ms 27.894 ms
7 bu-ether33.chctilwc00w-bcr00.tbone.rr.com (66.109.1.41) 19.470 ms 0.ae1.pr1.lax00.tbone.rr.com (107.14.17.250) 12.073 ms bu-ether33.chctilwc00w-bcr00.tbone.rr.com (66.109.1.41) 60.635 ms
8 66.109.7.134 (66.109.7.134) 12.452 ms 31.059 ms 18.084 ms
9 104.44.8.110 (104.44.8.110) 79.150 ms 98.747 ms 92.944 ms
10 be-2-0.ibr01.sn1.network.microsoft.com (104.44.4.5) 83.899 ms 70.589 ms 89.764 ms
11 104.44.4.204 (104.44.4.204) 76.124 ms 96.211 ms 73.647 ms
12 be-3-0.ibr02.dfw05.network.microsoft.com (104.44.4.89) 83.525 ms 95.898 ms 70.630 ms
13 be-1-0.ibr01.dfw05.network.microsoft.com (104.44.4.6) 70.731 ms 72.349 ms 71.600 ms
14 be-4-0.ibr02.dm2.network.microsoft.com (104.44.4.11) 87.655 ms 74.855 ms 76.601 ms
15 be-1-0.ibr01.dm2.network.microsoft.com (104.44.4.83) 72.906 ms 77.442 ms 72.566 ms
16 be-5-0.ibr02.ch1.network.microsoft.com (104.44.4.77) 73.853 ms 69.270 ms 70.727 ms
17 ae76-0.ch3-96cbe-1b.ntwk.msn.net (104.44.9.51) 74.969 ms 74.683 ms ae75-0.ch3-96cbe-1a.ntwk.msn.net (104.44.9.49) 73.909 ms
18-30 * * *

traceroute to 40.121.88.202:30001 (40.121.88.202), 30 hops max, 38 byte packets
1 cpe-76-176-176-1.san.res.rr.com (76.176.176.1) 35.594 ms 29.973 ms 21.946 ms
2 tge1-5.crlscaij02h.socal.rr.com (76.166.18.133) 21.823 ms 23.471 ms 17.427 ms
3 agg33.sndhcaax02r.socal.rr.com (72.129.3.98) 13.531 ms 11.146 ms 12.171 ms
4 agg22.tustcaft01r.socal.rr.com (72.129.1.2) 19.950 ms 24.230 ms 15.648 ms
5 bu-ether16.tustca4200w-bcr00.tbone.rr.com (66.109.6.64) 17.611 ms 14.370 ms 15.909 ms
6 bu-ether14.lsancarc0yw-bcr00.tbone.rr.com (66.109.6.4) 15.101 ms 25.661 ms 15.965 ms
7 0.ae0.pr1.lax00.tbone.rr.com (107.14.17.248) 13.489 ms bu-ether43.chctilwc00w-bcr00.tbone.rr.com (66.109.1.43) 13.878 ms 0.ae1.pr1.lax00.tbone.rr.com (107.14.17.250) 15.783 ms
8 66.109.7.134 (66.109.7.134) 13.310 ms 15.900 ms 13.205 ms
9 104.44.8.110 (104.44.8.110) 76.848 ms 76.834 ms 75.352 ms
10 be-2-0.ibr01.sn1.network.microsoft.com (104.44.4.5) 75.888 ms 75.164 ms 77.890 ms
11 104.44.4.204 (104.44.4.204) 74.231 ms 77.652 ms 79.186 ms
12 be-4-0.ibr01.atb.network.microsoft.com (104.44.4.46) 77.292 ms 78.087 ms 78.939 ms
13 be-3-0.ibr03.atb.network.microsoft.com (104.44.4.43) 78.199 ms be-1-0.ibr02.atb.network.microsoft.com (104.44.4.39) 79.149 ms be-3-0.ibr03.atb.network.microsoft.com (104.44.4.43) 76.973 ms
14 be-4-0.ibr01.was05.network.microsoft.com (104.44.4.22) 77.072 ms 79.853 ms be-3-0.ibr01.bn1.network.microsoft.com (104.44.4.49) 76.265 ms
15 ae63-0.bl4-96cbe-1a.ntwk.msn.net (104.44.9.27) 74.722 ms be-1-0.ibr02.was05.network.microsoft.com (104.44.4.19) 78.345 ms ae63-0.bl4-96cbe-1a.ntwk.msn.net (104.44.9.27) 77.689 ms
16 be-3-0.ibr02.was05.network.microsoft.com (104.44.4.26) 78.617 ms 79.695 ms ae73-0.bl4-96cbe-1b.ntwk.msn.net (104.44.9.31) 77.486 ms
17 * * ae73-0.bl4-96cbe-1b.ntwk.msn.net (104.44.9.31) 73.998 ms
18-30 * * *

traceroute to 65.55.158.118:3544 (65.55.158.118), 30 hops max, 38 byte packets
1 cpe-76-176-176-1.san.res.rr.com (76.176.176.1) 32.423 ms 24.216 ms 28.787 ms
2 tge1-5.crlscaij02h.socal.rr.com (76.166.18.133) 21.696 ms 26.086 ms 27.399 ms
3 agg33.sndhcaax02r.socal.rr.com (72.129.3.98) 12.510 ms 9.832 ms 11.741 ms
4 agg22.tustcaft01r.socal.rr.com (72.129.1.2) 16.967 ms 16.907 ms 16.346 ms
5 bu-ether16.tustca4200w-bcr00.tbone.rr.com (66.109.6.64) 15.185 ms 23.062 ms 15.639 ms
6 bu-ether14.lsancarc0yw-bcr00.tbone.rr.com (66.109.6.4) 17.946 ms 30.283 ms 9.862 ms
7 bu-ether33.chctilwc00w-bcr00.tbone.rr.com (66.109.1.41) 14.931 ms 15.897 ms bu-ether43.chctilwc00w-bcr00.tbone.rr.com (66.109.1.43) 64.687 ms
8 66.109.7.134 (66.109.7.134) 9.529 ms 12.057 ms 14.673 ms
9 104.44.8.106 (104.44.8.106) 23.543 ms 26.848 ms 27.294 ms
10 be-4-0.ibr01.by2.network.microsoft.com (104.44.4.3) 25.712 ms 25.884 ms 25.678 ms
11 ae85-0.by2-96c-1a.ntwk.msn.net (104.44.8.189) 23.790 ms ae86-0.by2-96c-1b.ntwk.msn.net (104.44.8.191) 22.025 ms 23.844 ms
12-30 * * *
Bullet Lee wrote:
Originally I had an older DOCSIS 2 SB5101 that worked fine for a long time. I've had that beat since college and it has held strong. Once the issue cropped up I traded it in for an SBG6580 that drastically reduced my latency to around 20ms to Google and in matches for CS:GO as well as speedtests. Again the issue popped up again and I purchased a Zoom 5345 that is a single function, so no Wifi mumbo jumbo that TWC provided and a highly rated consumer modem. After a day or two it became apparent that it did not fix the problem. I also cultivate the switch farms during the day. I've done it all, its not the home user. I say, hey if you got it working get in as many good matches as you can. I was lucky enough to have a relatively lag free day and at least went from silver>gold. So that is a win.
I agree, it's not the home user. The common denominator here is Halo 5 since everyone seems to have issues in Halo 5 and ONLY Halo 5.

My old modem worked fine for every other game, including the Halo 5 beta which I played a decent amount of. The entire freakin' point of the Halo 5 beta was to test the servers, wasn't it?

Pro tip: It wasn't. Modern betas are just a glorified demo designed to build hype for the product. It's obvious the beta didn't do a thing in regards to the netcode or the online play because it's WORSE than it was in the beta.

A developer, especially a AAA developer is also expected to test their game on a wide range of network hardware, ISP's and regions to make sure the netcode runs smoothly. Again, 343 obviously didn't do this.

My theory is that there's something messed up with the Halo 5 netcode. Some network equipment may be more tolerant to this than others. Some people perhaps can fix the issue by changing their modem/router, but perhaps other people are at the mercy of the equipment their ISP uses in their exchange.
Pyroteq wrote:
Bullet Lee wrote:
Originally I had an older DOCSIS 2 SB5101 that worked fine for a long time. I've had that beat since college and it has held strong. Once the issue cropped up I traded it in for an SBG6580 that drastically reduced my latency to around 20ms to Google and in matches for CS:GO as well as speedtests. Again the issue popped up again and I purchased a Zoom 5345 that is a single function, so no Wifi mumbo jumbo that TWC provided and a highly rated consumer modem. After a day or two it became apparent that it did not fix the problem. I also cultivate the switch farms during the day. I've done it all, its not the home user. I say, hey if you got it working get in as many good matches as you can. I was lucky enough to have a relatively lag free day and at least went from silver>gold. So that is a win.
I agree, it's not the home user. The common denominator here is Halo 5 since everyone seems to have issues in Halo 5 and ONLY Halo 5.

My old modem worked fine for every other game, including the Halo 5 beta which I played a decent amount of. The entire freakin' point of the Halo 5 beta was to test the servers, wasn't it?

Pro tip: It wasn't. Modern betas are just a glorified demo designed to build hype for the product. It's obvious the beta didn't do a thing in regards to the netcode or the online play because it's WORSE than it was in the beta.

A developer, especially a AAA developer is also expected to test their game on a wide range of network hardware, ISP's and regions to make sure the netcode runs smoothly. Again, 343 obviously didn't do this.

My theory is that there's something messed up with the Halo 5 netcode. Some network equipment may be more tolerant to this than others. Some people perhaps can fix the issue by changing their modem/router, but perhaps other people are at the mercy of the equipment their ISP uses in their exchange.
Burning the midnight oil man! Great data! This is exact same data in the mlabs report.

"What are the key study findings? Using Measurement Lab (M-Lab) data, and constraining our research to the United States, we observed sustained performance degradation experienced by customers of Access ISPs AT&T, Comcast, Centurylink, Time Warner Cable, and Verizon when their traffic passed over interconnections with Transit ISPs Cogent Communications (Cogent), Level 3 Communications (Level 3), and XO Communications (XO).

In a large number of cases we observed similar patterns of performance degradation whenever and wherever specific pairs of Access/Transit ISPs interconnected. From this we conclude that ISP interconnection has a substantial impact on consumer internet performance -- sometimes a severely negative impact -- and that business relationships between ISPs, and not major technical problems, are at the root of the problems we observed. Observed performance degradation was nearly always diurnal, such that performance for access ISP customers was significantly worse during peak use hours, defined by the Federal Communications Commission (FCC) as the hours between 7pm and 11pm local time. 6 This allows us to conclude that congestion and under-provisioning were causal factors in the observed degradation symptoms.

7 It is important to note that while we can infer that performance degradation is interconnection-related, we do not have the contractual details and histories of individual interconnection agreements. As such, we cannot conclude whether parties apart from the two we identify are also involved (e.g. in the case that an Access ISP shares an interconnection point with another, etc.). We leave this non-technical question open for further study by others and focus here on the impact of what we can observe on consumer performance through measurement "

I've never had issue with any Xbox game other than halo 5. I didn't have an issue withe the h5 beta (though there were far less players in the beta than the meta). Most games rely on a p2p system. Much less bandwidth intensive.

My guess is that it's a combination of netcode and the overwhelmed tier 3 connections.

I can play fine during the day, even in party chat. After 5pm central, my games continuously degrade.
I rage posted on the TWC forums earlier today. My post, followed by the response. All I can say is stop buying equipment. I made that mistake yet again today with another new modem.

"Does TWC and 343i have a timetable on the fix for this lag problem affecting countless players? This was posted directly on the halowaypoint.com forum.

https://www.halowaypoint.com/en-us/forums/e0d9938206f04a598ce84f2c8cadce02/topics/halo-5-multiple-la...

"Thank you all for the detailed reports! They have been extremely useful to our investigation of this matter.

We’re are working directly with Time Warner Cable to investigate this issue. Please continue to provide the following information with your reports in this thread:

What region are you located in?
How often are you experiencing this? (Every game, every other game?)

- Does this happen multiple times per game?
Description of your experience (Warping, delayed bullet registration, walking into walls etc.)

- Xbox DVR video proof is also extremely helpful
Make / Model of your router Firmware version of your router ISP & Bandwidth speeds (Up / Down)

Any additional information you can provide about your network / internet connection would also be of great help.

Thank you,
The Forum Team"

I just purchased my 3nd modem (after leaving the TWC issued one behind), in hopes that it would fix my issue. I activated it today with TWC telephone support. Side note, I'm also on my 2nd router.

I mentioned my issues to customer support and told them, this is my last try at making this work. "If my neighbor with at&t can play halo 5 lag free, why should I stay with Time Warner?" He didn't have anything to offer in return.

I've spent hours on the phone with Time Warner and Microsoft support.

After 5pm CST, the lag gets worse and worse. It's not what I'm paying for.

I've posted numerous times on the waypoint forum looking for solutions and proposing possible fixes.

A rep on this forum had posted this on 8/29, two days after the game release...

"Good afternoon,

The issue with Halo 5 was identified yesterday. As you may find with your connection, customers are reporting an issue with connecting to the Microsoft dedicated servers. This issue was determined to be a Microsoft issue, not a TWC issue. I know it may sound like a "it's not us, it's them" answer, but in this case it we are seeing the servers are having trouble keeping up with the demand, which is causing the lagging. Customers reporting this issue are only having an issue with Halo 5."

Why is there still an issue? Why is this mostly a TWC subscriber problem?

There also was the 343i studio head who tweeted that TWC was classifying halo 5 traffic as peer to peer.

What is the exact issue? When will this be fixed? There's hundreds, likely thousands of us experiencing the same issue."

A sincerely credible and historical helpful someone replied...

"Peer to peer traffic is being investigated as copyright piracy and is monitored by the cable companies and FBI.
This is indeed a TWC problema transport ISP issue and one at Microsoft, all 3 parties are involved and refuse to work together for a solution. Also, read the Mlabs report and pay attention to the words "Business decision"...
it's around page 28 or so...
http://www.measurementlab.net/static/observatory/M-Lab_Interconnection_Study_US.pdf
"

That's the same report I posted here yesterday.

The only thing I can say at this point is its time to raise some hell. Call your ISP, Microsoft, AT&T, Verizon, comcast tier 3.

This isn't getting solved without customer backlash.

http://www.level3.com/en/contact-level-3/
So, I just upgraded my FIOS and everything is great, except this game...of course my favorite. I guarantee you I have the best specs and cannot play this at all...here it is:
  • What region are you located in? US - Texas
  • How often are you experiencing this? (every game, every other game?) Every Lobby, Every Warzone. Connection Lost - Disconnected from local network
  • Does this happen multiple times per game? once per try to get in a multiplayer game, have not been able to play since upgrade of service.
  • Description of your experience (Warping, delayed registration, walking into walls, etc.) Matchmaking errors out, connection lost.
  • Xbox DVR / YouTube / Twitch VoD / etc is extremely helpful - No additional streaming, no broadcasting.
  • Make / model of your router - UI Version: v1.0.175
    Firmware Version 1.2.1.36.84
    Model Name: FiOS-G1100
    Hardware Version: 1.03
  • ISP & Bandwidth speeds (Up / Down) Verizon FIOS, 125 up 125 down
No good reason I can't connect.
So, I just upgraded my FIOS and everything is great, except this game...of course my favorite. I guarantee you I have the best specs and cannot play this at all...here it is:
  • What region are you located in? US - Texas
  • How often are you experiencing this? (every game, every other game?) Every Lobby, Every Warzone. Connection Lost - Disconnected from local network
  • Does this happen multiple times per game? once per try to get in a multiplayer game, have not been able to play since upgrade of service.
  • Description of your experience (Warping, delayed registration, walking into walls, etc.) Matchmaking errors out, connection lost.
  • Xbox DVR / YouTube / Twitch VoD / etc is extremely helpful - No additional streaming, no broadcasting.
  • Make / model of your router - UI Version: v1.0.175
    Firmware Version 1.2.1.36.84
    Model Name: FiOS-G1100
    Hardware Version: 1.03
  • ISP & Bandwidth speeds (Up / Down) Verizon FIOS, 125 up 125 down
No good reason I can't connect.
I know someone that runs off free wifi with a speed of 0.5 lmfao....AND HE DONT LAG IN HALO 5!!!! YET IM PAYING 0VER 200$ AND LAG... it really is a shame. The funny thing is the beta did not have a single problem for me, not 1 time was anyone walking in walls in the beta. im thinking the beta had dedicated servers turned off.... anyways xbox live only requires a speed of 1.25mbps to run ok. So no one should be laging like this. Its clearly 343i/microsofts main problem. I cant just blame TWC for this since its only happening in halo 5. if i can find 1 other game that was doing this...ok fine TWC is at fault all they way...but i cant! Its only halo 5.
Got back with my company tonigh after the outage. We we doing really well.

I played a full 4-5 before this with my company. No lag at all. My deaths were my fault, my shots were off when they were off.

Until...

Matchmaking...Spawn into instant death. Over and over and over. "where are you playing from," I asked. "El Salvador," was the response.

I'm from -Yoinking!- Wisconsin. Why is my fireteam being matchmade with folks that far away? Great nice dude, good player, but why?

There is no reason we should have been matched with those folks period.

Guess who finished first on our team? El Salvador, (again don't mean that in a negative way). Guess what team won? The team from his region.
Quote:
Thank you all for the detailed reports! They have been extremely useful to our investigation of this matter.

We’re are working directly with Time Warner Cable to investigate this issue. Please continue to provide the following information with your reports in this thread:
  • What region are you located in?
  • How often are you experiencing this? (Every game, every other game?)
    - Does this happen multiple times per game?
  • Description of your experience (Warping, delayed bullet registration, walking into walls etc.)
    - Xbox DVR video proof is also extremely helpful
  • Make / Model of your router Firmware version of your router ISP & Bandwidth speeds (Up / Down)
Any additional information you can provide about your network / internet connection would also be of great help.

Thank you,
The Forum Team
I'm from Ohio with TWC and I can't play an multiplayer at all, no co-op , area or war zone.

My time left in game clock is always frozen, my party continues to tell me I'm walking into walls, my respond clock is frozen and this is literally every game I play.

I actually thought this problem may be on my end so I just dropped 200 bucks on a brand new modem and router (Motorola SB6141/ASUS rt-n66u) I had the firmware updated after installing so it's the latest and greatest and updated.
i am currently paying for 50/5 but according to Xbox one I'm getting 60/6 with 90 ms latency.

all of my other devices run great on this internet, the only game I play is halo 5 and I've been down ever since the update
CLEARING POST FOR BAD DATA

Nevermind, cable swap didn't do squat. Lagging every game again. Fun.
Quote of the day... I ask, "what country are you from?" response to my teammate and I... "Scotland." Two central standard time gamers are being matchmade with Scotland at 3:30 pm.
jlongx83 wrote:
Quote of the day... I ask, "what country are you from?" response to my teammate and I... "Scotland." Two central standard time gamers are being matchmade with Scotland at 3:30 pm.
That's not so much a knock on matchmaking algorithms so much as it is more evidence that like every other country's internet infrastructure is way better than the U.S.'s
My friends (East coast) and I (West coast) sometimes hook up with whole groups of people playing from Europe and we have no latency issues.

Deliciously illogical anecdotal evidence conjecture here: I hilariously have yet to ever experience lagging out when queueing with full groups of European players. We sometimes run 10-20 warzone/warsault matches in a row. No problems. Running with only U.S. domestics though? It's like betting against the house.
Twist with my problem. I found a guy who had a theory about how xbox one changes its behavior if you have the setting instant on set up, which I did. I turned that off and went to power save as the setting and I have played 4 full warzones with no issues at all. Your mileage may vary, but it did the trick for me.
Twist with my problem. I found a guy who had a theory about how xbox one changes its behavior if you have the setting instant on set up, which I did. I turned that off and went to power save as the setting and I have played 4 full warzones with no issues at all. Your mileage may vary, but it did the trick for me.
I hope this is your fix, but it's likely coincidence. Always been on power saver here. Still lagging. BAD tonight.
Also, TWC responded on their forum...

"I can confirm that we are indeed working directly with 343 Industries, and we are aware of the post placed on their forums last night. At this point we don't have a time frame for a resolution, but both parties have been in frequent communication.
We've been asked to post a request for our customers to please provide (if they haven't already to 343) the same information here on our community:
What region are you located in?
  • How often are you experiencing this? (Every game, every other game?)
- Does this happen multiple times per game?
  • Description of your experience (Warping, delayed bullet registration, walking into walls etc.)
- Xbox DVR video proof is also extremely helpful
  • Make / Model of your router
- Firmware version of your router
And to reiterate, any other information you can provide about network/connection would be appreciated."

Just thought I'd share. Now we have 343i calling it out here and on reddit, acknowledging the problem, along with TWC stating they're working with 343i.

Direct link.

http://forums.timewarnercable.com/t5/Connectivity/TWC-Halo-5-343i/m-p/90906#M25986
  1. 1
  2. ...
  3. 48
  4. 49
  5. 50
  6. 51
  7. 52
  8. ...
  9. 68