The terrain server that hosted sector 100, which contains Duda Beach, experienced a hardware failure that required failing the sector over to different hardware, at about 7pm on Tuesday the 11th.

In the course of failing it over to different hardware, a server that had previously been hosting sector 100 was used. While we are still sorting out the details, that server somehow remembered its layout, something we had previously thought was impossible. This layout was applied to the world when the server came online, and this old layout was synched back to the avatar servers. As a result of this, the following situations have resulted as reported to us by members:

1) Portazones out in sector 100 (aka duda beach) may have had their time settings corrupted and nulled. Members will see the portazones in their inventory and with zero time left on them.

2) Portazones which had been out in sector 100 on or around February 26th (a few weeks ago) and then removed or moved may have been brought back out into sector 100 again.

3) Portazones which were out in sector 100 around February 26, but were later changed to a different layout of pieces, may have been returned to the old layout they had as of February 26th.

We are still investigating how this happened.

If you have a portazone which was affected, please click on "Help" on There Central and then "Ask a Question" and indicate that you had a duda beach portazone which was affected. In your ticket, please give:

1) the name of the portazone or its doid number
2) the details of how your portazone was affected
3) what you remember the state of your portazone as being

Failing over a sector to a new server is something that, while not a common occurance, has been done many times before over the years, and a situation such as this has never occurred previously. Operations will be working with engineering to determine how this came to be and how to prevent it from occuring in the future.

We apologize for any inconvenience this may cause.

-There Customer Support