[Resolved 11:51AM PST] Services should now be returning to normal.
[Update 11:45AM PST] Logins have been re-enabled.
Logins to Second Life have just been disabled, and residents who are in Second Life at present are advised not to rez any no-copy objects or make any important transactions, while we work on quickly resolving an issue with our database. We will keep this post updated until this problem is resolved.
Hi Everybody!!
In our effort to provide the highest quality Second Life experience possible we must occasionally make sure we are addressing the correct issues. It has come to our attention that we may be spending to much time and resources on a product no longer relevant to our residents.
Today we’d like to let you know we’re seriously considering whether Linden Lab should continue supporting Windows 2000. Our tracking shows that very few of you, about 1/10th of 1 percent of all of you that have logged in within the past two months, are still using Windows 2000 when logging into Second Life. That is approximately 2,000 out of 1,407,581 residents who have logged in to Second Life within the past 60 days.
We’d like to let the Linden engineers stop working on supporting an operating system released in 2000, and instead move on to other work which will benefit a much larger group of Residents.
If we do stop supporting that version of the OS, it would not be until 60 days from now, to make sure there is plenty of time for the news to spread.
To briefly review the last eight years of Windows OS: Windows 2000, was first released in February 2000, and updated with SP4 Rollup 1 v2 in 2005. Microsoft has followed Win2k with two more recent versions of the OS, Windows XP which was released in October 2001 and Windows Vista released in January 2007 and updated February 2008.
What would it mean to “stop support”? Eventually we would stop developing for the SDK (software development kit ) of that operating system, and we would also stop doing QA testing on Win2k. Also our support team would no longer be able to offer solutions to every issue related to or caused by the support of Windows 2000 ceasing.
What would you notice? If you are one of the few logging in with that OS, you would still be able to do so the day we stop supporting it for some time. Exactly how long we couldn’t guarantee, because we would no longer be testing and developing to make sure it does work.
What say you citizens? Thumbs up? Thumbs down? Please direct any comments to this forum thread. (Lindens will be reading your comments and responding periodically over the next few days.)
[Resolved 8:35 PM PDT] Teleports and Logins should now be behaving normally.
Due to a problem with our network, residents might experience a slightly decreased teleport success rate at the moment, and logins will also be affected. We are aware of this and our Ops team is already working to fix it.
[17:25PM Pacific] All vioce IM’s are back up now. Thank you for your patience.
[12:20AM Pacific] The problem appears to be intermittent and is being looked into. For the time being, we do not have any additional information.
[9:20PM Pacific] We have received scattered reports that voice IM is down within the Burning Life 2009 Estate. Our vendor is working to resolve this issue. Spatial (Local) and Group voice chat are both functional within the estate. We will update this post once the situation has been resolved.
[All Clear 22:40 PDT] The Public Issue Tracker and the Wiki are both back up and running. We anticipate no further outages related to this issue.
[Reopened 21:20 PDT] The Issue Tracker (jira.secondlife.com) and the Wiki (wiki.secondlife.com) are experiencing performance issues due to a hardware failure, and may be completely unavailable at times. The issue is being worked on, but no eta for a resolution is available at this time. Please watch this post for further updates.
[Resolved 2:05pm PDT] - The Issue Tracker and Wiki are both back up and running. While they are fully operational, it is possible there may be some intermittent outages while the hardware is further updated.
The Issue Tracker (jira.secondlife.com) and the Wiki (wiki.secondlife.com) are temporarily unavailable due to a hardware failure. We are currently investigating, but do not have an estimated resolution time yet. Please watch this blog for further updates.
[RESOLVED July 12 2008 09:01 AM PST] The repairs of the password recovery page are done, and it is back to full working order.
[3:37 PM Pacific] Thank you for your patience whilst we continue to investigate.
Our Website’s password recovery page is under repair. We’ll have it functional again as soon as possible. In the meantime, password recovery assistance is available via phone at 866-476-9763. Please note this hotline should only be used for requesting assistance with password recoveries.
[Resolved 21:52] The DNS issue is once again resolved and inworld services are restored. Ops will continue to monitor the situation throughout the night, and any changes in the situation will be posted here.
[Re-Opened 23:10] We are again experiencing DNS issues which may result in failures to teleport, rez, and complete in-world transactions. We ask that residents refrain from rezzing or transacting anything important in world until we’ve cleared this issue. We are working on resolving this issue quickly and will keep you updated.
[Resolved 21:35] The DNS issue is once again resolved; the land store has been reopened and inworld services are restored. Ops will continue to monitor the situation throughout the night, and any changes in the situation will be posted here. We now return you to your regularly scheduled weekend, already in progress.
[Re-Opened 20:45] We are again experiencing DNS issues which may result in failures to teleport, rez, and complete in-world transactions. Additionally, the land store is offline for the duration of the problem. We ask that residents refrain from rezzing or transacting anything important in world until we’ve cleared this issue. We are working on resolving this issue quickly and will keep you updated.
[Resolved 5:03 PM PDT] This problem has be taken care of by our ops and services have been restored.
We are currently experiencing DNS issues which may result in failures to teleport, rez, and complete in-world transactions. We ask that residents refrain from rezzing or transacting anything important in world until we’ve cleared this issue. We are working on resolving this issue quickly and will keep you updated.
[UPDATE 12:30pm Pacific] Logins are open and in-world services are restored.
[UPDATE 12:22 pm Pacific] Logins are temporarily closed.
[UPDATE 12:18pm Pacific] Some residents are unable to login.
Operations is diagnosing current reports of stale L$ transactions and TPs timing out. Please refrain from operating on valuable assets until an ALL-CLEAR is given. We’ll keep you posted.
[Resolved 9:55pm PDT] - The routing failure has been resolved and the ~500 regions should either be available now, or will be within a few minutes.
[Update 9:30am PDT] - Inventory database work has completed and logins for that database have been restored.
The ~500 regions affected by the routing failure remain inaccessible at this point, but work continues and we expect it to be resolved soon. If you are unable to login, please try logging in to a different region.
Update 8:59 a.m. PDT We are working on one of our inventory databases. This will cause the database to be down for approximately 30 minutes. Residents on this database will not be able to login. Residents in-world on this database will have restricted services.
A routing failure has rendered about 500 regions inaccessible. We expect resolution to take 30-60 minutes.
All-Clear 9:56 p.m. PDT We have identified and corrected the routing issue. It is all-clear to conduct transactions and issues stemming from this routing problem should be resolved.
Some residents are reporting problems with appearance and inventory. Operations is tracing potential routing issues. Please do not attempt valuable transactions until an all-clear is given.
Grab this RSS feed