There's a huge outage in the US North Eastern area that may affect traffic routing. I do believe DB servers are hosted on the west coast though. This is not a DB issue, but a general internet traffic issue
Odd, I was able to stream YouTube and Netflix this morning. Game is back up (for now), lost 1500 places during my 1 1/2 hr outage. Hopefully the outage stays away for the next couple hours
There's a huge outage in the US North Eastern area that may affect traffic routing. I do believe DB servers are hosted on the west coast though. This is not a DB issue, but a general internet traffic issue
I'm at work noticing lots of my usual websites are either slow or just not working.
Thanks for the heads-up.
Looking forward to all the threads about the event getting screwed up!
If it is the players internet that is screwed then that is not DBs fault. (which appears to be the case this time)
If it's DBs internet that is screwed up and not the players then that is DBs fault via their choice of third party. (Which was the case about seven months ago, which I believe you're alluding to)
We had this debate months ago so I'll not go into it too deeply again.
Working fine here in Asia. I don't know that I'm on the same server, but I would guess that I am.
And that is the main problem. It gives an advantage to the ones not affected by the outage. Whether it is a DB issue or not.......
It does, but DB cannot be held liable for a situation that affects how you access the game. If there's a natural disaster that causes the internet to go down in your area, DB wouldn't be expected to compensate, and this is no different.
Looking forward to all the threads about the event getting screwed up!
If it is the players internet that is screwed then that is not DBs fault. (which appears to be the case this time)
If it's DBs internet that is screwed up and not the players then that is DBs fault via their choice of third party. (Which was the case about seven months ago, which I believe you're alluding to)
We had this debate months ago so I'll not go into it too deeply again.
It is next to impossible to call something the player's internet or DB's internet. There are so many companies involved. Unless it's the players local provider (Comcast, AT&T, Spectrum, etc...) it's not the players internet, it's the generic cloud of connectivity. With DB running servers on AWS and AWS being responsible for the internet access to its machines, DB has no local provider for it to be their internet.
What happens in all these cases is a problem somewhere between the local players provider and AWS. Neither the player nor DB has any control over the routes your data takes going between the two.
Agree that this is not DB's "fault" - this was a wider internet outage issue that only affected a subset of sites/services/locales
But this does highlight a fault in DB's event structure: some players are allowed to continue playing while others are shut out. And it's not good enough to say "well they had all weekend to play."
I hope DB looks into how to structure their events so that players don't get penalized due to internet outages instead of turning a blind eye and saying, "the internet is not our concern."
No one is asking DB to fix the internet. People are asking for a level playing field when there are severe outages like this.
Working fine here in Asia. I don't know that I'm on the same server, but I would guess that I am.
And that is the main problem. It gives an advantage to the ones not affected by the outage. Whether it is a DB issue or not.......
It does, but DB cannot be held liable for a situation that affects how you access the game. If there's a natural disaster that causes the internet to go down in your area, DB wouldn't be expected to compensate, and this is no different.
Db's fault. Local Provider's fault. No one's fault. Still affects the playability for some. There is a lot you can tell about a company {just saying} by how often they go to the "It's not our fault" well......
"The truth is like a lion; you don't have to defend it. Let it loose; it will defend itself."
Agree that this is not DB's "fault" - this was a wider internet outage issue that only affected a subset of sites/services/locales
But this does highlight a fault in DB's event structure: some players are allowed to continue playing while others are shut out. And it's not good enough to say "well they had all weekend to play."
I hope DB looks into how to structure their events so that players don't get penalized due to internet outages instead of turning a blind eye and saying, "the internet is not our concern."
No one is asking DB to fix the internet. People are asking for a level playing field when there are severe outages like this.
Sorry, but that's how life works. Things outside your control or anyone else’s happen and people are affected in different ways. It stinks, but if we were to take your position to its logical conclusion we’d have a situation where a tornado knocks down all of the houses in a village except one and the rest of the villagers decide to knock down the surviving house with a bulldozer so everyone can suffer equally.
That may be an extreme example, of course. It’s meant to highlight the problem with solutions to force a level playing field on people - would you have DB roll back the event scores to right before the outage and then continue it for six hours or so tomorrow? Would the event stop at the roll-back point? What about people whose Internet access wasn’t affected but intended to make a late push for a particular rank due to their personal schedule? Now you have people suffering directly because of a hypothetical action by DB instead of something that is out of their control...would you dismiss their concerns in the name of “fairness” for others?
Agree that this is not DB's "fault" - this was a wider internet outage issue that only affected a subset of sites/services/locales
But this does highlight a fault in DB's event structure: some players are allowed to continue playing while others are shut out. And it's not good enough to say "well they had all weekend to play."
I hope DB looks into how to structure their events so that players don't get penalized due to internet outages instead of turning a blind eye and saying, "the internet is not our concern."
No one is asking DB to fix the internet. People are asking for a level playing field when there are severe outages like this.
Sorry, but that's how life works. Things outside your control or anyone else’s happen and people are affected in different ways. It stinks, but if we were to take your position to its logical conclusion we’d have a situation where a tornado knocks down all of the houses in a village except one and the rest of the villagers decide to knock down the surviving house with a bulldozer so everyone can suffer equally.
That may be an extreme example, of course. It’s meant to highlight the problem with solutions to force a level playing field on people - would you have DB roll back the event scores to right before the outage and then continue it for six hours or so tomorrow? Would the event stop at the roll-back point? What about people whose Internet access wasn’t affected but intended to make a late push for a particular rank due to their personal schedule? Now you have people suffering directly because of a hypothetical action by DB instead of something that is out of their control...would you dismiss their concerns in the name of “fairness” for others?
Agreed. I'm a socialist by nature, but there's a limit. When DB had a consistent problem with Galaxy events crashing at the last minute or going slow at the start of Faction events, they fixed their issues. I can't remember if compensation was given or not, tbh, but it would have been justifiable as it was well within their control. But we can't expect DB to adjust the event every time a server in New York, Barcelona or Tokyo goes down. At a certain point you're punishing people more than evening the playing field.
I would not mind though if DB rotated the start and end times for events to level the playing field. Some people have to get up in the middle of the night each event when it begins and ends.
Agree that this is not DB's "fault" - this was a wider internet outage issue that only affected a subset of sites/services/locales
But this does highlight a fault in DB's event structure: some players are allowed to continue playing while others are shut out. And it's not good enough to say "well they had all weekend to play."
I hope DB looks into how to structure their events so that players don't get penalized due to internet outages instead of turning a blind eye and saying, "the internet is not our concern."
No one is asking DB to fix the internet. People are asking for a level playing field when there are severe outages like this.
Sorry, but that's how life works. Things outside your control or anyone else’s happen and people are affected in different ways. It stinks, but if we were to take your position to its logical conclusion we’d have a situation where a tornado knocks down all of the houses in a village except one and the rest of the villagers decide to knock down the surviving house with a bulldozer so everyone can suffer equally.
That may be an extreme example, of course. It’s meant to highlight the problem with solutions to force a level playing field on people - would you have DB roll back the event scores to right before the outage and then continue it for six hours or so tomorrow? Would the event stop at the roll-back point? What about people whose Internet access wasn’t affected but intended to make a late push for a particular rank due to their personal schedule? Now you have people suffering directly because of a hypothetical action by DB instead of something that is out of their control...would you dismiss their concerns in the name of “fairness” for others?
It's curious why you go straight to bulldozing the survivors house instead of looking to help others.
Games/competitions frequently have concessions for lack of playability due to external conditions. Think rain delays, change of venue due to scheduling conflicts, etc. Even to your example, game 3 of the 1989 world series was postponed due to an earthquake. They didn't let some of the players play and other players stay home.
All I'm saying is that dB should reconsider the fixed date/time nature of events for both local timezone considerations and for significant internet outages.
Event times are already "timezoneist" against players in Asia. It's time to reconsider these event timings again.
Maybe it's localized events (smaller pools with smaller reward tiers), maybe it's something ticket based instead of time-grinding based so that people aren't tapping more than they "need" to (although that still doesn't solve the problem of what if a player chose to spend their tickets at 7am est). There's multiple ways of doing this besides hard-and-fast set-in-stone (except when the coders forget to set it correctly) start and end times.
All I'm saying is that dB should reconsider the fixed date/time nature of events for both local timezone considerations and for significant internet outages.
easiest fix would be to get rid of ranked rewards completely, only fixed threshold rewards. But people would complain about that too...
Captain Lvl 99; Vip0; 552 Unique Immortals; Fleet: Omega Molecules; Base Lvl 134 (MAX); Playing Since March 2016.
Games/competitions frequently have concessions for lack of playability due to external conditions. Think rain delays, change of venue due to scheduling conflicts, etc. Even to your example, game 3 of the 1989 world series was postponed due to an earthquake. They didn't let some of the players play and other players stay home.
That’s not really an apt comparison. The earthquake happened before the game even started - if there were a major internet outage right before an event were to start, I think could indeed be fair to push the event start back to Friday (trading one weekday for another shouldn’t inconvenience too many people).
Even if the quake happened in the middle of the game, it’s still not an appropriate comparison because everyone in that stadium is in the same time zone; if you stop in the middle and resume play where they left off days or weeks later, everyone is still on the same playing field (pun sort of intended). With people from all over the world playing this game, a rollback/postponement would result in certain people getting an advantage over others...you could argue that play should resume at the originally scheduled times a day or two later but then DB is taking rewards away from people who earned them through legitimate play. Why again would DB incense some players with intentional actions in order to appease others angered by something out of DB’s control?
It's curious why you go straight to bulldozing the survivors house instead of looking to help others.
That was a metaphor, and an apt one by my estimation. It was intentionally extreme because that is very often what is required to demonstrate the point at hand.
Games/competitions frequently have concessions for lack of playability due to external conditions. Think rain delays, change of venue due to scheduling conflicts, etc. Even to your example, game 3 of the 1989 world series was postponed due to an earthquake. They didn't let some of the players play and other players stay home.
This is not even close to a fair, apples-to-apples comparison. Your example here would be like if the entire internet worldwide went down for 24 hours. Sticking with your baseball analogy, what is being discussed in this thread would be more like having 13 games scheduled for a single day and having one of those games rained out. MLB tries to find a makeup date to have that game resumed/replayed, but as is sometimes the case, if the game in question is not always replayed unless it is required to determine playoff seeding. MLB does not require the other 12 games in progress to also be postponed; sometimes life/events happen outside of human control and it is just understood that nothing can be done about it.
All I'm saying is that dB should reconsider the fixed date/time nature of events for both local timezone considerations and for significant internet outages.
Event times are already "timezoneist" against players in Asia. It's time to reconsider these event timings again.
IMO, that would be a complete disaster, and I quite frankly reject your premise. The company has stated QUITE CLEARLY at the outset what the rules and expectations are, it is up to each individual consumer to decide if those terms are agreeable. Trying to move the goalposts after the fact to accommodate people who failed to properly vet the rules/expectations is IMO the definition of unfairness to the community at large, and would be extremely damaging.
And I speak from experience here. Yes, I live on the west coast of the U.S., but I work nights, meaning the timing for pretty much everything in this game is HORRIBLE for me! On faction event weeks I have to stay up late when I get home from work in the morning well passed my normal bed time to share an event crew with my squad, I'm always asleep Monday morning when the events end, and several other weekly in-game features like Gauntlet usually end before I wake up in the afternoon. But I knew ALL of this when I started playing, and it was up to me to decide if it was worth living with these hardships; it would never in a million years occur to me to complain about this or have the unmitigated gall to demand that the company change the game to suit my needs.
It's curious why you go straight to bulldozing the survivors house instead of looking to help others.
That was a metaphor, and an apt one by my estimation. It was intentionally extreme because that is very often what is required to demonstrate the point at hand.
Games/competitions frequently have concessions for lack of playability due to external conditions. Think rain delays, change of venue due to scheduling conflicts, etc. Even to your example, game 3 of the 1989 world series was postponed due to an earthquake. They didn't let some of the players play and other players stay home.
This is not even close to a fair, apples-to-apples comparison. Your example here would be like if the entire internet worldwide went down for 24 hours. Sticking with your baseball analogy, what is being discussed in this thread would be more like having 13 games scheduled for a single day and having one of those games rained out. MLB tries to find a makeup date to have that game resumed/replayed, but as is sometimes the case, if the game in question is not always replayed unless it is required to determine playoff seeding. MLB does not require the other 12 games in progress to also be postponed; sometimes life/events happen outside of human control and it is just understood that nothing can be done about it.
All I'm saying is that dB should reconsider the fixed date/time nature of events for both local timezone considerations and for significant internet outages.
Event times are already "timezoneist" against players in Asia. It's time to reconsider these event timings again.
IMO, that would be a complete disaster, and I quite frankly reject your premise. The company has stated QUITE CLEARLY at the outset what the rules and expectations are, it is up to each individual consumer to decide if those terms are agreeable. Trying to move the goalposts after the fact to accommodate people who failed to properly vet the rules/expectations is IMO the definition of unfairness to the community at large, and would be extremely damaging.
And I speak from experience here. Yes, I live on the west coast of the U.S., but I work nights, meaning the timing for pretty much everything in this game is HORRIBLE for me! On faction event weeks I have to stay up late when I get home from work in the morning well passed my normal bed time to share an event crew with my squad, I'm always asleep Monday morning when the events end, and several other weekly in-game features like Gauntlet usually end before I wake up in the afternoon. But I knew ALL of this when I started playing, and it was up to me to decide if it was worth living with these hardships; it would never in a million years occur to me to complain about this or have the unmitigated gall to demand that the company change the game to suit my needs.
I was in the same boat as you until a few months ago but I made it work. I’m with you. I don’t complain about the world needing to adjust to me, I realize that it is I that must adjust to the world.
Working fine here in Asia. I don't know that I'm on the same server, but I would guess that I am.
And that is the main problem. It gives an advantage to the ones not affected by the outage. Whether it is a DB issue or not.......
Actually, my time zone gives me a major disadvantage in several areas of the game. Most noteably in these events because I go to sleep a few hours before the event finishes and can lose up to 3000 places in that time. Having a little extra connectivity for a few hours makes very little difference after 2 years gameplay. Please don't use the "this is unfair" card just because my game is working.
Edit: I posted the above before reading other comments. I have now seen that the conversation went in this direction already, but I feel that my point still stands.
![[DB-DO BETTER] [7TW] Captain plim123](https://us.v-cdn.net/6030345/uploads/defaultavatar/nL5515UJH9DYJ.jpg)
Comments
Second Star to the Right - Join Today!
And that is the main problem. It gives an advantage to the ones not affected by the outage. Whether it is a DB issue or not.......
I'm at work noticing lots of my usual websites are either slow or just not working.
Thanks for the heads-up.
If it is the players internet that is screwed then that is not DBs fault. (which appears to be the case this time)
If it's DBs internet that is screwed up and not the players then that is DBs fault via their choice of third party. (Which was the case about seven months ago, which I believe you're alluding to)
We had this debate months ago so I'll not go into it too deeply again.
It does, but DB cannot be held liable for a situation that affects how you access the game. If there's a natural disaster that causes the internet to go down in your area, DB wouldn't be expected to compensate, and this is no different.
It is next to impossible to call something the player's internet or DB's internet. There are so many companies involved. Unless it's the players local provider (Comcast, AT&T, Spectrum, etc...) it's not the players internet, it's the generic cloud of connectivity. With DB running servers on AWS and AWS being responsible for the internet access to its machines, DB has no local provider for it to be their internet.
What happens in all these cases is a problem somewhere between the local players provider and AWS. Neither the player nor DB has any control over the routes your data takes going between the two.
But this does highlight a fault in DB's event structure: some players are allowed to continue playing while others are shut out. And it's not good enough to say "well they had all weekend to play."
I hope DB looks into how to structure their events so that players don't get penalized due to internet outages instead of turning a blind eye and saying, "the internet is not our concern."
No one is asking DB to fix the internet. People are asking for a level playing field when there are severe outages like this.
Db's fault. Local Provider's fault. No one's fault. Still affects the playability for some. There is a lot you can tell about a company {just saying} by how often they go to the "It's not our fault" well......
https://news.yahoo.com/no-not-just-half-internet-125115356.html
You should seriously consider updating your signature, @Flemming.
Sorry, but that's how life works. Things outside your control or anyone else’s happen and people are affected in different ways. It stinks, but if we were to take your position to its logical conclusion we’d have a situation where a tornado knocks down all of the houses in a village except one and the rest of the villagers decide to knock down the surviving house with a bulldozer so everyone can suffer equally.
That may be an extreme example, of course. It’s meant to highlight the problem with solutions to force a level playing field on people - would you have DB roll back the event scores to right before the outage and then continue it for six hours or so tomorrow? Would the event stop at the roll-back point? What about people whose Internet access wasn’t affected but intended to make a late push for a particular rank due to their personal schedule? Now you have people suffering directly because of a hypothetical action by DB instead of something that is out of their control...would you dismiss their concerns in the name of “fairness” for others?
Agreed. I'm a socialist by nature, but there's a limit. When DB had a consistent problem with Galaxy events crashing at the last minute or going slow at the start of Faction events, they fixed their issues. I can't remember if compensation was given or not, tbh, but it would have been justifiable as it was well within their control. But we can't expect DB to adjust the event every time a server in New York, Barcelona or Tokyo goes down. At a certain point you're punishing people more than evening the playing field.
It's curious why you go straight to bulldozing the survivors house instead of looking to help others.
Games/competitions frequently have concessions for lack of playability due to external conditions. Think rain delays, change of venue due to scheduling conflicts, etc. Even to your example, game 3 of the 1989 world series was postponed due to an earthquake. They didn't let some of the players play and other players stay home.
All I'm saying is that dB should reconsider the fixed date/time nature of events for both local timezone considerations and for significant internet outages.
Event times are already "timezoneist" against players in Asia. It's time to reconsider these event timings again.
Maybe it's localized events (smaller pools with smaller reward tiers), maybe it's something ticket based instead of time-grinding based so that people aren't tapping more than they "need" to (although that still doesn't solve the problem of what if a player chose to spend their tickets at 7am est). There's multiple ways of doing this besides hard-and-fast set-in-stone (except when the coders forget to set it correctly) start and end times.
easiest fix would be to get rid of ranked rewards completely, only fixed threshold rewards. But people would complain about that too...
That’s not really an apt comparison. The earthquake happened before the game even started - if there were a major internet outage right before an event were to start, I think could indeed be fair to push the event start back to Friday (trading one weekday for another shouldn’t inconvenience too many people).
Even if the quake happened in the middle of the game, it’s still not an appropriate comparison because everyone in that stadium is in the same time zone; if you stop in the middle and resume play where they left off days or weeks later, everyone is still on the same playing field (pun sort of intended). With people from all over the world playing this game, a rollback/postponement would result in certain people getting an advantage over others...you could argue that play should resume at the originally scheduled times a day or two later but then DB is taking rewards away from people who earned them through legitimate play. Why again would DB incense some players with intentional actions in order to appease others angered by something out of DB’s control?
That was a metaphor, and an apt one by my estimation. It was intentionally extreme because that is very often what is required to demonstrate the point at hand.
This is not even close to a fair, apples-to-apples comparison. Your example here would be like if the entire internet worldwide went down for 24 hours. Sticking with your baseball analogy, what is being discussed in this thread would be more like having 13 games scheduled for a single day and having one of those games rained out. MLB tries to find a makeup date to have that game resumed/replayed, but as is sometimes the case, if the game in question is not always replayed unless it is required to determine playoff seeding. MLB does not require the other 12 games in progress to also be postponed; sometimes life/events happen outside of human control and it is just understood that nothing can be done about it.
IMO, that would be a complete disaster, and I quite frankly reject your premise. The company has stated QUITE CLEARLY at the outset what the rules and expectations are, it is up to each individual consumer to decide if those terms are agreeable. Trying to move the goalposts after the fact to accommodate people who failed to properly vet the rules/expectations is IMO the definition of unfairness to the community at large, and would be extremely damaging.
And I speak from experience here. Yes, I live on the west coast of the U.S., but I work nights, meaning the timing for pretty much everything in this game is HORRIBLE for me! On faction event weeks I have to stay up late when I get home from work in the morning well passed my normal bed time to share an event crew with my squad, I'm always asleep Monday morning when the events end, and several other weekly in-game features like Gauntlet usually end before I wake up in the afternoon. But I knew ALL of this when I started playing, and it was up to me to decide if it was worth living with these hardships; it would never in a million years occur to me to complain about this or have the unmitigated gall to demand that the company change the game to suit my needs.
I was in the same boat as you until a few months ago but I made it work. I’m with you. I don’t complain about the world needing to adjust to me, I realize that it is I that must adjust to the world.
Actually, my time zone gives me a major disadvantage in several areas of the game. Most noteably in these events because I go to sleep a few hours before the event finishes and can lose up to 3000 places in that time. Having a little extra connectivity for a few hours makes very little difference after 2 years gameplay. Please don't use the "this is unfair" card just because my game is working.
Edit: I posted the above before reading other comments. I have now seen that the conversation went in this direction already, but I feel that my point still stands.