Hey folks we’re looking into this issue. Apologies for the hassle, we’ll post more information in this thread once we have it.
Hey folks we’re looking into this issue. Apologies for the hassle, we’ll post more information in this thread once we have it.
Hey there thanks for the awesome visual post for this. I’m not sure what the design intent is here so I’ll make sure our hero designers check this out tomorrow.
Cheers, hope everyone had a great weekend.
Hey there. We’re not aware of any server issues right now. I’ll dig into our network quality data and see if I can find any details. Perhaps a regional or isp issue.
This is awesome. I’m on the wrong coast or I’d be there. Cheers!
Hey everyone, this is a bug we're aware of and we have it fixed for the next stage. Unfortunately it's not something we can fix now during Stage 3. Cheers!
Really awesome experience thanks for sharing. It makes my day to read posts like this because people coming together and having fun is why I love gaming.
As an aside I’m sorry you hit a significantly lopsided match. If the OP can DM me some details (gamertag and when the match happened) I’ll dig into it a bit to see if there’s something we can do.
Cheers!
Awesome screenshot, that brings back so many memories.
Just before we went live our QA team noticed a data issue. Jesse, our lead server engineer, knew he could fix the issue in about 10 minutes. We delayed the launch to let him run off and do that work quickly, but during that time there was a massive amount of people trying to login. Everyone repeating that login flow is very demanding on the Battle.net infrastructure. Just as Jesse was finishing up his work, engineers from that team were on the conference bridge asking us to go live as soon as we could. I'll never forget the tone in their voice, the sense of urgency was very pronounced!
Cheers
Oh he’s so cute. _^
One of our gameplay programmers was looking at this the other day. We hope to have this in 1.38.
Cheers
What an awesome experience, thanks for sharing it! Cheers <3
I think my comment came off WAY more condescending than I meant it too, I was only trying to say I think they read a lot of feedback from here
Yep! I’m here almost every day. Hope everyone is having a great weekend! <3
Hey there, our PS4 community is going strong! Taking a quick peak at our matchmaking data it looks like the average queue time for PS4 players in the past week fluctuates between about 60 to 80 seconds.
Cheers
Hey there, the current target is for this coming week.
I’ll pass this along to our compatibility QA team. Sorry you’re having issues. Cheers.
edit: I posted a follow up but as an edit here, our compatibility team was unable to reproduce the issue with the same model. Check drivers?
Hey there we tracked down this issue and have resolved it. Sorry for the hassle. Cheers
Hey folks we identified the issue and have resolved it. Apologies for the hassle. Cheers
Hey folks, we’ve researched this issue and believe the problem is due to packet filtering or connectivity between customer ISPs in Iran and Amazon AWS. Overwatch leverages Amazon AWS infrastructure in Europe region when necessary, this is usually during new content updates.
In addition to having reported the issue here, we recommend players report this issue directly to their ISP support as well.
Hey folks, engineers who support our voice platform found an issue that is now resolved. Thank you for the reports, sorry for the hassle.
Cheers
Hey folks we had a server issue that caused this to happen for some players. We’ve resolved the issues and we’re monitoring to watch for any additional issues.
Sorry for the hassle
Hey folks, this is a bug and we’re working on a fix. Apologies for the confusion here, cheers.
edit: For clarity, Ashe should generate ultimate charge while B.O.B. is active after we fix this bug.