So for those of us who have been screwed over for 3 weeks, reporting this issue and getting no feedback, we're still stuck waiting until tuesday?

We have a timer on monday, we're going to be attacked, again, for the 3rd week, as we wait patiently on Sunday night for the timers to roll over, just to see nothing change.

We nearly lost our citadel today due to these timers.

I want CCP to manually update our timers in reparation for this issue, at the standard time that they should be changed. My alliance is sick and tired of having to deal with this for nearly a month now.

Hello Players

We are planning to deploy a fix to resolve an issue where citadel vulnerability timers were unable to be changed. This fix is not being deployed immediately so as to give players advance warning of a non-standard timing of a vulnerability window change.
.

Hello Players

We are planning to deploy a fix to resolve an issue where citadel vulnerability timers were unable to be changed. This fix is not being deployed immediately so as to give players advance warning of a non-standard timing of a vulnerability window change.

This change will be deployed with the May release on Tuesday, May 31 2016, during downtime (11:00UTC). Once this fix has been deployed, any vulnerability timer changed before 00:00UTC on Monday, May 30 2016, will take immediate effect during that downtime deployment. Any changes made to vulnerability timers after 00:00UTC on Monday, May 30 2016, will take effect at the regular time of 00:00UTC on Monday, June 6 2016.

More details on Citadel vulnerability windows can be found this help center article: https://support.eveonline.com/hc/en-us/articles/208289385-Citadel-Vulnerability-States

UPDATE

Previously we announced a fix for changing Citadel vulnerability timers. After further testing, a few details of the handling of vulnerability timers during this fixGÇÖs deployment have changed.

Now, any and all pending vulnerability timers as of downtime (11:00UTC) on Tuesday, May 31 2016, will take effect during that downtime. This includes any changes made to vulnerability windows made after 00:00UTC on Monday, 30 May 2016, but before the deployment downtime. Any changes made after this downtime will take effect at 00:00UTC on Monday, 6 June 2016, as normal.

Hello Players

We are planning to deploy a fix to resolve an issue where citadel vulnerability timers were unable to be changed. This fix is not being deployed immediately so as to give players advance warning of a non-standard timing of a vulnerability window change.

This change will be deployed with the May release on Tuesday, May 31 2016, during downtime (11:00UTC). Once this fix has been deployed, any vulnerability timer changed before 00:00UTC on Monday, May 30 2016, will take immediate effect during that downtime deployment. Any changes made to vulnerability timers after 00:00UTC on Monday, May 30 2016, will take effect at the regular time of 00:00UTC on Monday, June 6 2016.

More details on Citadel vulnerability windows can be found this help center article: https://support.eveonline.com/hc/en-us/articles/208289385-Citadel-Vulnerability-States

UPDATE

Previously we announced a fix for changing Citadel vulnerability timers. After further testing, a few details of the handling of vulnerability timers during this fixGÇÖs deployment have changed.

Now, any and all pending vulnerability timers as of downtime (11:00UTC) on Tuesday, May 31 2016, will take effect during that downtime. This includes any changes made to vulnerability windows made after 00:00UTC on Monday, 30 May 2016, but before the deployment downtime. Any changes made after this downtime will take effect at 00:00UTC on Monday, 6 June 2016, as normal.

Hello Players

We are planning to deploy a fix to resolve an issue where citadel vulnerability timers were unable to be changed. This fix is not being deployed immediately so as to give players advance warning of a non-standard timing of a vulnerability window change.

This change will be deployed with the May release on Tuesday, May 31 2016, during downtime (11:00UTC). Once this fix has been deployed, any vulnerability timer changed before 00:00UTC on Monday, May 30 2016, will take immediate effect during that downtime deployment. Any changes made to vulnerability timers after 00:00UTC on Monday, May 30 2016, will take effect at the regular time of 00:00UTC on Monday, June 6 2016.

More details on Citadel vulnerability windows can be found this help center article: https://support.eveonline.com/hc/en-us/articles/208289385-Citadel-Vulnerability-States

UPDATE

Previously we announced a fix for changing Citadel vulnerability timers. After further testing, a few details of the handling of vulnerability timers during this fixGÇÖs deployment have changed.

Now, any and all pending vulnerability timers as of downtime (11:00UTC) on Tuesday, May 31 2016, will take effect during that downtime. This includes any changes made to vulnerability windows made after 00:00UTC on Monday, 30 May 2016, but before the deployment downtime. Any changes made after this downtime will take effect at 00:00UTC on Monday, 6 June 2016, as normal.

yeah i swear ive seen those new citadel things burn near 3 times already now lol i was like lol that citadel getting some as i passed by

btw is this the same logi bro i saw on dust forums lol do you remember that dev invasion event in dust where we had the like 300 clone ambush matches i made it into 2 of those lol i heard there were only 2 matches tho.... how many of those matches actually ran lol?