Second Life Grid Status Reports

We are seeing a slight delay in our support phone calls being connected to an agent. If you experience a slightly longer waiting time than usual, please bear with us, the call will be picked up.

[Resolved 11:20am PDT] - The issues with voice connectivity have been resolved and should be working as normal once again.

We are getting reports of voice connecting very slowly or not at all. The issue is being looked into, and we will update you as soon as we have any news.

[DONE 03:03 am PDT] The maintenance work is finished, and the Public Issue Tracker is back online.

[Oktober 13, 2008 at 02:31 am PDT] Our Public Issue Tracker is currently offline for about 30 minutes of scheduled downtime. We will let you know here as soon as it’s back online.

To protect SLurl visitors from potential exploits, we’ve disabled the iframe option for custom-built SLURLs at slurl.com.

This may result in cosmetic degradation of previously generated SLURLs using the iframe option. Graphical elements such as the “Visit” and “Teleport” links will still display and work properly, but remote content within the iframe will not be displayed.

[FINAL 10/8 4:58 pm Pacific] The system failure which has been spreading this annoying behavior to additional assets has been repaired.  We’ll be double-checking the support tickets we’ve received on this issue as quickly and thoroughly as possible.  If you discover another asset in your inventory which will rez in some regions but not others (allowing for rez privileges on the parcel where you try), please file a support ticket with at least the region name, and the object’s UUID if you can capture it from inventory. 

[UPDATE 10/8 00:40] Our technicians are continuing their work to correct this issue. If you are still encountering failures to rez, please file a support ticket with the time of the failure (in PDT, please), the region name and asset UUID that failed to rez so the information may be passed on to the developers.

[Update 3:36pm PDT] - Our technicians are continuing to work on the solution. We will keep you updated as we get more information on this matter.

[Update 2:36pm PDT] - We believe we have found the cause of this issue and are working to resolve it as quickly as possible. Please be aware that along with some people experiencing an issue with rezzing items, there may be some who cannot properly attach items either. We will continue to update this blog as information becomes available.

We are experiencing difficulties with the ability to rez items at this time. We will keep you posted as to when this problem is resolved.

[02:07 AM Pacfic]  The Public Issues Tracker is back online.

[01:54 AM Pacific]  Our Public Issues Tracker at http://jira.secondlife.com is offline at present.

[02:17 AM Pacific - RESOLVED]  The database problems have been rectified and in-world services should be back to normal now.

[01:42 AM Pacific]  We are experiencing a database problem at this time which may lead to various in-world difficulties, including teleporting. Please be aware of this before rezzing objects or making in-world transactions meantime.

The issue is being worked on by our engineers and we will update you here as soon as we can.

Today, we released an important update that improves the security of the Second Life viewer for all Residents. This update eliminates a recently discovered issue, and we’re requiring that all Residents download and install it to ensure that everyone remains secure while using Second Life. You will be prompted to download and install the update when you log-in, or you can get it from the Downloads page.

More details about the improvements included in this update are available below.

Linden Lab has released a Security Update to the Second Life viewer software today to address a potential security issue. This Security Update includes an additional security patch related to the Security Update issued on 26-Sept-2008.

Available for:

Second Life Viewer 1.20.15 / 1.20.16
Second Life Release Candidate Viewer 1.21.4

Description:

We recently updated the Second Life server and viewers to enhance the communications code. All transfer operations are now restricted to files that the user has expressly chosen, and specific directories that the viewer uses for transferring data. For the safety of all Second Life users, we are releasing this updated viewer to all Residents.

Potential vulnerabilities had been identified in those message communications directed at a Second Life viewer over the previous protocol. By taking advantage of this vulnerability, while extremely difficult technically, a malicious user could potentially use the viewer to access files on the victim’s computer. We currently have no evidence of this vulnerability ever being exploited.

This Security Update 2008-10-06 is required to continue to log-in to Second Life. By downloading the update, you will upgrade the software on your computer to version 1.20.17:

• Second Life Release Viewer 1.20.17

For Residents who use the Release Candidate viewer, you are required to update to RC5, which also includes other latest bug fixes:

• Second Life Release Candidate Viewer 1.21 RC5

Earlier versions of Second Life (1.19.1, 1.19, and before) include the serious vulnerabilities and are no longer supported. You will be prompted to upgrade to the latest version on your next login.

For any Residents who prefer / have been using earlier versions that do not include WindLight rendering, we have created a page on the Second Life Wiki that explains how to turn all related graphics settings to “Low,” effectively turning off WindLight in the current official viewer.

The source code for these new 1.20 and 1.21 RC5 viewers will be made available via the usual open source channels.

For discussion about the issue, please visit this thread in the SL Forums.

[Resolved 11:28a PDT] - The website is functioning properly again, please feel free to access the site as normal.

The Second Life website is currently unreachable. We are working to restore the site as quickly as possible. Please watch this blog for information as it becomes available.

There is a Rolling Restart in progress.  We expect this to complete within 6-7 hours.  This will begin in 10-15 minutes.  Please watch the Status Blog for detailed information, which will be posted after the Rolling Restart has completed.