Well...after digging through the dumps, did find some signs of congestion getting through Atlanta to a Charter subscriber in Sikeston, MO (St. Louis area by the looks of the DNS names along the route). But that is a common thing lately. We've got several tickets going already for the Atlanta area, so hopefully that kind of thing will get resolved eventually. Otherwise, the ones that matched were good for the most part, with a few failed attempts that were really odd, and not sure why they were even attempted. Some really positive things showed up. Was interesting to see how many sessions were peering directly with end-user ISP's through regions we spent a lot of time looking at with Tier3 support over the years---places that used to use TATA/Cogent/Level3 were now going directly from TWC/RR and into Verizon, Comcast, Hurricane Electric, etc. Quite rewarding to see the efforts finally taking root and making the difference. I mean... 58ms ping into Toronto from South Carolina. Just amazing how much an improvement that is from the 100+ we were seeing about two years ago. Also picked up Amazon web services in the Woodbine, NJ; Ashburn, VA; and Seattle, WA areas. Seen the PS4 connect to AWS a lot on it's own....but this was via UDP port 3074, which is in the UDP player assignment for the game. Perhaps they are in fact trying to use the Amazon Cloud to streamline things a bit more? This idea has come up in discussions in the past in relation to how Microsoft consoles seem to get a helping hand sometimes from their own cloud structure. Maybe Bungie is actually working on a similar structure with PS4 after all? Or maybe it is Sony's arrangement with Amazon for cloud services, and Destiny is piggy backing? Would explain a lot about the PS+ requirement if it is indeed tied into Sony's stuff like that. But that also means we could periodically find ourselves at the mercy of that Sony/Amazon arrangement. As in, Bungie could be virtually helpless to resolve issues occurring within Sony's arrangement with Amazon...have to wait for those two groups to hash it out. And now for a few eyebrow raising things that showed up: Two hosts were reporting addresses that are in the reserved private spaces: 192.168.0.11, and 10.2.172.236. Rightfully though, they stalled out and got booted as they should. But still...this kind of announcement should not be happening. Something is up either with those end-user networks, or their ISP's networks. Bungie needs to be capturing oddball exceptions better, especially when you look at this next one, which may have 3074 blocked (and was the only valid address that appeared unreachable via 3074 during the matching/launching): 189.216.59.78 The last ping responsive hop in it's route had 96-124 response times (average 123) over 25 pings. Peering is through Telia/Bestel to..... CHIHUAHUA, MEXICO OK... now that is a real "What the French Toast?" moment for Bungie right there. I am in South Carolina. While the pool wasn't more centralized to the Carolinas like I often saw it in the past, it was the right half of the continent: MO, IL, IN, WI, NC, GA, NY, NJ, PA, and two in the Toronto area----and it attempted to match me with one down in Chihuahua, Mexico...south and west of Texas. Forget the fact it was trying to reach out to Mexico from South Carolina....but the PING should have been a dead giveaway to not try putting us in the same pool. All other pings were averaging under 80ms by the same 25 ping test (even the Missouri one with bad spikes)---and this guy's gateway average was pegging just over 120ms....and was the only one that may have port 3074 blocked. Thankfully, that was a connection that also didn't appear to make the cut. but DAYUMN.... that is messed up if they are trying to reach out like that when there should be better options closer by.

Got back in tonight to check out the changes...was every bit a grind in Control as ever. Actually a bit rougher on the edges. Still only took me 7 matches to complete the weekly bounty, but it was down to the wire to get those advantage kills caught up on the last two matches. That mode is still plagued with people not playing to the objective so was spending half the match with just one flag capped....or NONE! Lag was popping up for sure... more so then I was accustomed to seeing. Reported 5 or 6 people for it. That usually would only happened across hours upon hours of play (like getting to rank 5 in IB kind of time frame). Wasn't an issue when I queued strikes for the weekly bounty, but it was pretty rough at times in Crucible. Noticed the skill gap seemed to be spreading out thinner too, which wasn't helping much. Generally it was bouncing around a 200-300 or so gap on the ELO scale. But there was one poor guy that got stuck with us for a few matches that was just getting hammered. A 910 ELO score against players with 1300+ and 1400+ ELO rating. I'm right at 1150 and they were giving me a good beating....felt bad for the lower level guy. He/she kept spiking on the latency too, which unfortunately wasn't always to his/her advantage either. Was clocking in at 0.4's through 0.6's against players getting between 2's and 4's. Can't imagine it was a lot of "fun" for that player. Took a snapshot of connections for one roster and dumped the text so I can go through it. Wanted to look up the geodata and run some ping/traces out of curiosity. See if there may be another Level3 or XO.net issue in play again, just to rule that out. Don't wan't to be all about calling foul on the changes until I can verify it wasn't the peering issue we've been wrangling with. I can get my ISP working on the peering if that's the case. But if it's Bungie's matchmaking knackering it up, not much I can do about that.

Your internet then

I don't know what you're on about. That game wath BEAUTIMUTH.

It doesn't matter what settings they change. ..it's still the same Ole shitty p2p network

Clearly lag switching...that's all... Not really out the ordinary in crucible

I said it before in many posts...peer to peer connectivity for PVP sucks!! Nice double kill btw, that must have sucked for them lol

I have a totally different experience post mm changes. Very little red bars. Don't see many teleporting guardians anymore. Still very competitive matches with solid connections.

I saw almost no lag during IB but haven't played much since then. A few people were red bar but they were the only ones.

They loosened the restriction on skill right? So it still grabs people from across the world just less skilled to fill the match. It will still take a 1.4 from Guam over a 1.0 next door to me.. lol

Eh, this new matchmaking has been working fine for me. If I'm green, I face other green bars. If I'm red/yellow, i face red/yellow bars. [spoiler]the pubstomping is real[/spoiler]

I am seeing red bars also but not as many as usual especially for it being IB. Usually by Friday it is a lag fest. The consistent thing with the red bars that I am seeing is that they usually are on the top of the score board.

just been in ib and i did ok then me and this german player kept running into each other , no matter where i went there he was then i worked his game out the next times we met up he was toast time after time after time as i worked out which way he was running round the map and where he was gonna head to for a lil camping when he got a kicking and decided to bow out for a bit. guess what out of the blue he is knocking me over before i could see him i spawn he is round a corner and im headshotted then he is on a 10 kill streak then a 15 streak , now when i die i look at the card after i see who has killed me and with what , big suprise this guy is now red barring he isnt teleporting just a red bar and he is killing me before i even see him i run through a doorway its him im dead he was finally killed (tbh i dont know if i killed him or someone else) but when i died next i checked and he is a green bar again the next game he is green then i saw him getting a 10 streak and guess what he is red again ten i jumped him and shut him down only for his connection to go green. i reported him for cheating and bad connection and told him i had , the next game he was green all the way and didnt get any streaks , ok he got some kills on me and tea bagged me (cough , he may of eaten the salty ones when i killed him) so its a fair shout but guess what when the game finished i was top in the match mainly as i went for the spark not kills. the point of this post is that if he can cheat like that how is cbmm working how can they claim its working , we have all seen more red bars since the patch and more lag so clearly the patch/cbmm isnt working and the body of evidence on the forum kinda proves this. a mate who hasnt played destiny since bf1 came out played the ib and his words were after a few games this looks more like sbmm gone haywire as theres no consistancy for this to be cbmm and to much lag.

My games have been better overall and having easy games mixed in with sweat my balls off games keeps me more interested than non stop "you have to be at your best constantly and stick 100% to the meta or you'll go .1" like it was for harder sbmm. At least that was my experience and really when you get into the realm of Destiny netcode and networking it's all anecdotal since one person's nice game is another's rubberbanding lag fest.