Thanks Anet, you had just 1 job.

[Sleepwalker.1398]

https://ibb.co/1XW14vG

[Zamiel.2130]

Had the same. Ended up traveling to Lions Arch to get the WvW window and by then, the queues were already going up. Joined one, was 6th in the queue. It popped. Clicked Travel and B000M! 81 in the queue. I don't believe they should have done this during the WvW Rush Event. 

[Sleepwalker.1398]

The error only disappear once when everyone got in and i changed maps.

I tried few map changes before but that didn't work.

[Kayowin.9217]

In addition to that, booted out of the game twice as well.    Whoever is in charge of managing the EC2 instances should be put on notice.   Same for whoever is in charge of making a BETA and WVW RUSH event happen simultaneously without having approval for the resource ceilings to be raised on said EC2 and associated resources if that is what happened....

Edited January 13 by Kayowin.9217

[Ronin.4501]

2 hours ago, Zamiel.2130 said:

I don't believe they should have done this during the WvW Rush Event. 

Except they make the same poor decision over and over; there's either been a WvW-type event OR they decide to have these beta events during one of the PvE festivals, both of which are going to put extra strain on the servers due to excess population. If these guys were firemen, they'd be the ones bringing gasoline to put the fire out.

[Gotejjeken.1267]

1 hour ago, Ronin.4501 said:

Except they make the same poor decision over and over; there's either been a WvW-type event OR they decide to have these beta events during one of the PvE festivals, both of which are going to put extra strain on the servers due to excess population. If these guys were firemen, they'd be the ones bringing gasoline to put the fire out.

Guessing that is on purpose, both from a PR standpoint and a load test one.