TacTicToe wrote:Hmm I wonder if a class action lawsuit from GSP's and server operators would light a fire under their butts?
There is no guarantee. EA/Dice could always fall back to using the providers they use for console. Yes, they would have millions of angry people but they could do it.
We would also waste a lot of money in the process and any GSP involved would most likely be unable to host any future EA games which would be a big blow.
Now on the other hand, if thousands of 'regular' players got together and did that it would probably have a better result. Kind of like what happened on Reddit a few months ago when the BF3 crashing exploit was at its peak.
@Kraze^NFo> Juski has a very valid point
@Juski> Got my new signature, thanks!
@Kraze^NFo> Out of context!
@Juski> Doesn't matter!
@Juski> You said I had a valid point! You can't take it back now! It's out there!
Edge100x wrote:EA told us today that they found and believe they resolved a problem within Blaze that caused some of these recent drops.
Some other drops have been due to problems with NSPs and the ISP hosting Blaze (DDoS attacks, for instance), and these may continue. We also still believe that there is an in-game exploit of some sort which causes players to time out.
Will it require a server patch? Cause our just did it again... had been doing good since the PB update you all did.
Yep, something happened to my CTF server at exactly the same time something happened to yours. And now my Conquest server dropped. Grrrr!
jaythegreat1 wrote:Not sure if it's coincedence... always seems like ours happens around 9:30PM - 10:00PM EST.
Nope, mine keeps doing it at around the same time. I'm always in game, seeding and asleep at the same time only to wake up and find my guys have been disconnected. I look at the logs and everyone that was in game booted at around the time you mentioned. WTH is going on?!
TimSad, if you have a specific event that you want me to investigate, please contact us through the support system so that I can look at your server's log. This thread contains mostly your posts at this point, and most posts have the same content (with the same responses from us), so there's not much more to be said here.
I don't see any global or machine-specific events at the time of your post -- just the standard random Blaze problems for individual servers. Starting a little after 3pm PDT, though, there has been a more global issue that has led to widespread drops and an across-the-board decline in player counts. I don't know if it was related to your earlier problem, and I don't know whether it's a problem with Blaze, Battlelog, or PB.
As a follow-up, that EA BF3 issue starting at 3pm was something to do with their back-end, definitely. We saw servers steadily dropping players until around 4:10pm PDT, when it started to recover. It is possible that there was another DDoS attack on the ISP hosting Blaze/Battlelog.
.=QUACK=.Major.Pain wrote:You mention it seems to happen around the same time.
Maybe it's a daily restart happening and ignoring that people are on the server.
Nope... cause the server doesn't go offline, nor does the uptime reset as if you restart the server. Plus the auto-restarts aren't supposed to occuring until 3AM...ish.