Archive for January, 2010

[RESOLVED] Grid Restart 10pm PST 19 January 2010

Wednesday, January 20th, 2010

[9:33AM PST][RESOLVED] The grid rolling restart is finished.

At approximately 10pm PST, we will begin a rolling restart of the grid for some hardware moves.  This should last approximately 8 hours and should not affect logins or other resident activities outside of the restarting regions.

[RESOLVED] Log In and Registraton Failures

Wednesday, January 20th, 2010

[9:03 AM PST][RESOLVED] The equipment has been fixed. Log ins and registrations should be back to normal.

[8:41 AM PST]  We are currently experiencing an equipment failure. It will affect many log ins and new registrations. We will post updates here as we have them.

[RESOLVED] Brief Service Portal Outage at 9 p.m. Pacific Tonight

Tuesday, January 19th, 2010

[Resolved} Our support system vendor will be restarting the system at 9 p.m. Pacific this evening. Support tickets and chat will be unavailable for about five minutes.

As always, if the scope or scheduling of the work changes, we'll update here.

[Resolved] Stipends may be delayed for some residents.

Tuesday, January 19th, 2010

[Resolved @ 7:13 am PST] Stipend payments are now back on track and should be completed. Thank you for your patience.

Some residents may experience their stipends being paid out slightly later than usual. We are aware of this and working towards a resolution. We apologize for any inconvenience caused. Thank you for your understanding.

Support Portal Maintenance

Friday, January 15th, 2010

[POSTED Jan. 15th 3:20 PM PST] We will be conducting support portal maintenance this evening starting at 10:00 PM PST.  This will be an approximately 30 minute maintenance update.  During this time, residents will not be able to create tickets or speak to a live chat agent.  For abuse issues, please continue to use our abuse report system.  We apologize for any inconvenience this may cause.  Please follow this blog for any updates.

[Resolved] Server Maintenance has Commenced

Thursday, January 14th, 2010

[Resolved] Maintenance has been completed. Thank you for your patience.

We will be conducting some routine server maintenance that may briefly affect some regions and residents.  We apologize for any inconvenience this may cause.  Please watch this blog for any new updates as they become available.

[Resolved] Login/Registration Temporarily Offline Today at 6 a.m.

Thursday, January 14th, 2010

[Resolved @ 6:21am PST] The maintenance has completed. Logins and registrations have been re-enabled. Thank you for your patience.

Starting at 6 a.m. PST, all login and registrations will be offline due to maintenance.  Logins will not be available during that time. This will not affect our residents currently in-world.  Maintenance should take approximately 30 minutes.  We apologize for any inconvenience.

[RESOLVED] Voice Experiencing Intermittent Failures

Tuesday, January 12th, 2010

[1:48 PM PST]  [RESOLVED] Vivox has informed us that this issue has been resolved and log ins to voice have returned to normal.

[1:28 PM PST]  At this time Vivox is investigating an issue with the SIP proxy system.  This is causing intermittent failure to log into voice.  Residents in voice in a given location will continue to have voice service, but they may experience voice failures if they attempt to teleport or switch between spatial voice and group voice. We will post further updates as we get them.

[RESOLVED] Stipends

Tuesday, January 12th, 2010

[11:38 AM PST] [Resolved]  Stipends have completed the run for this week.

[07:41 AM PST] There may be a delay for some residents receiving their stipends today.   Please check this page for more updates.

[RESOLVED] Limited Support

Monday, January 11th, 2010

[Resolved 4:55pm PST] All services have returned to normal. Thank you for your patience.

[Posted 3:20pm PST] Our billing, technical, and outworld support teams are limited at the moment due to a power outage. Concierge phone and live chat and premium live chat support is still available. We will post an update here when this issue is resolved.