Second Life Grid Status Reports

[12:31 a.m. Pacific ] The reporting databases are all in synch now, so all Webservers should provide full and up-to-date transaction histories.

[9:41 a.m Pacific] One of the databases responsible for sending transaction histories to our Webserver cluster has fallen behind on synchronization. Until it catches up, only some of the Webservers will be showing up-to-date histories.

If you log in to secondlife.com, try to pull your transaction history, and come up empty, a temporary workaround (once you’re logged in) is to manually edit the leftmost portion of your browser’s URL bar. Past the double slash, it’ll look something like: secure-webXX, where ‘XX’ is some number. Try editing that to ’secure-web3′ and resubmitting to hit an up-to-date server.

The laggy database should be caught up by about noon Pacific.

[UPDATE 8:30 p.m. Pacific]: The issue is resolved. We apologize for any inconvenience this has caused. Thank you!

We’re currently aware of a problem with regions not coming up or not allowing residents in. We are investigating and will post updates as needed. Thank you for your patience.

For more information please see the announcement on the Official Linden Lab Blog.

A new Release Candidate (RC) viewer has been made available on the Test Software page for connecting to the Second Life Grid. This viewer contains the latest round of bug fixes and/or soon-to-be-released new features. Release Candidate viewers are optional and can be installed side by side with the primary viewer.

Please remember: try the RC viewer only if you want to participate in the bug reporting process and identify issues before it becomes the default viewer.

[Resolved 4:53 p.m. PDT] Our phone support system is now fully functional.

[UPDATE 2:29] The reboot is over. The service is still not at 100% however; callers may occasionally get busy signals when they shouldn’t. We’re working with the vendor to track that last gremlin down.

[UPDATE 2:04] This should take about 15 more minutes.

[UPDATE 1:40 p.m. Pacific] A full restart of the phone systems is underway. All phone support will be disrupted for the next several minutes, but this should clear the remaining issues once the system is rebooted.

[UPDATE 12:20 p.m. Pacific] The vendor’s still working on a full restoration of services. We’ll keep updating as often as they report to us.

[UPDATE 11:50 a.m. Pacific] Still not at 100% health points. We can take calls, but our ability to transfer them internally is limited. We’re waiting on another status update within half an hour.

[UPDATE 10:45 a.m. Pacific] We’re not out of the woods yet, unfortunately. The vendor has partially restored service, but not entirely. We’re expecting our next update in about half an hour, unless we get an all-clear first.

[UPDATE 10:09 a.m. Pacific] The vendor’s aiming for a fix within 20 minutes. We regret the inconvenience, and we’ll keep you posted.

[UPDATE 9:41 a.m. Pacific] The fix is in progress; the vendor will report back to us within the next 15 minutes or so.

Phone lines into support are suffering a partial disruption. We’ve escalated to the vendor, and expect to hear back within 10 minutes.

[UPDATE @ 1:26 PM PDT]  These issues have been resolved. Thank you for your patience.

The database is currently experiencing an excessive load, causing some inworld service failures. While this is being looked into, please avoid activities such as inworld transactions and rezzing of no-copy items.

[1:10 a.m.] The all-clear has been given! You may now review your Transaction History as needed. Thanks and have a good morning! — Frontier

We are currently investigating an issue that prevents residents from being able to review their Transaction History.