[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.
[CANCELLED] The Support Portal will remain online tonight. Please disregard the previous notice.
The Support Portal will be offline for approximately ten minutes tonight, begining at 23:10 PDT. Residents will not be able to submit Support Tickets or engage in Live Chat support during this time. Please monitor this post for updates.
[RESOLVED May 16 @ 11:55 p.m.] Thanks everyone for your patience, the Map of Second Life has been updated and this issue has been resolved. - Frontier
[UPDATE 5/15 13:58] Map data was updated for half of the grid this morning. The other half will be updated with the rolling restart scheduled for tomorrow morning.
The Map is currently showing an earlier version of the Second Life grid. This is only affecting the Map - all inworld locations remain unchanged. We are aware of the issue, and the Map data is in the process of updating, which we anticipate being completed overnight.
[10:40 a.m. Pacific] Full grid interconnectivity has been restored. In world transactions are safe again. There may be a couple of minutes of slow logins. If you’ve been having trouble getting in, please be patient and try to ride a login all the way through, rather than disconnecting and retrying.
[10:08 a.m. Pacific] Two of our server facilities have abruptly lost interconnection. We’re investigating as quickly as possible. Meantime, symptoms include login failure for some residents, and some transaction failures in world. Please do not rez or transfer valuable (no-copy) assets until we give an all-clear.
[RESOLVED 07:10 AM PDT] These regions are now happily reunited with the rest of Second Life.
[6:45AM PDT] We currently have a networking issue that is affecting many regions. Anyone in these regions will be able to move and interact normally, except they will be essentially cut off from communicating with the rest of world until the problem is fixed. That means items will not rez, IM’s may not work, L$ transactions may fail, teleporting will not be possible and items will not be able to be saved to inventory.
We are working to fix the faulty component and should have things back up and running soon. We will post updates along with an estimate on how long this will take as soon as we can. -Chiyo
[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.
We have received information from our network providers of planned maintenance which will make approximately 2700 regions unreachable for approximately 3 minutes this evening, Wednesday 30th April at 11pm PDT.
There will be two such events; the next outage will occur on Monday 5th May at 11pm PDT for the same length of time and will affect a similar number of regions.
We cannot list all of the regions that may be affected but if yours is one of these please accept our apologies for what we anticipate to be a few minutes lack of connectivity.
[Resolved at 10:50pm Pacific] Our Support Portal is back online!
[Updated at 10:10pm Pacific] Maintenance is in progress. — Frontier
As reported earlier this week, our support portal will be offline for system maintenance tonight, Saturday, 26th April.
Our software supplier has reduced the length of the downtime from six hours to three, from 9:00pm-Midnight PDT.
During that time, the support portal will be unavailable for chat or ticketing services.
Apologies for any inconvenience this may cause to you.
[Updated Saturday @ 09:10am] The rolling restart of the rest of the grid is now complete.
[Updated Saturday @ 8:40am] The rolling restart of the rest of the grid is now in progress. It began at 5:10am, and is now 93% complete. As usual, each region will be down for ~5 minutes. if your region is down for more than 20 minutes, please contact support.
[Updated Saturday @ 7:06am] The rolling restart of the rest of the grid is now in progress. It began at 5:10am, and is now 46% complete. As usual, each region will be down for ~5 minutes. if your region is down for more than 20 minutes, please contact support.
[Updated Saturday @ 6:05am] The rolling restart of the rest of the grid is now in progress. It began at 5:10am, and is now 16% complete. As usual, each region will be down for ~5 minutes. if your region is down for more than 20 minutes, please contact support.
[Updated Saturday @ 5:10am] The rolling restart of the rest of the grid is now in progress. It began at 5:10am; we will post hourly updates with a percentage completed. As usual, each region will be down for ~5 minutes. if your region is down for more than 20 minutes, please contact support.
[Updated Friday @ 8:39am] The rolling restart to half of the grid is now complete but for 7 hosts that needed to be manually updated; those will be completed within a few minutes. The rest of the grid will be updated tomorrow morning.
[Updated Thursday @ 7:10pm] We are beginning have completed the deploy of 1.21 to 3 racks (632 regions). Here is a list of regions that as of now are on version 1.21.0.85745.
[Updated Thursday at 12:47pm] We will shortly be deploying have deployed 1.21 to 1 rack (about 170 regions) again. If all goes well, we will continue with the tenative timeline listed in the Wednesday at 8:10pm update below.
[Update Wednesday @ 9:15pm] A slight and subtle wrinkle during the deploy left some object-to-object emails non-functional. The responsible systems have gotten a stern talking to, and this service should be operational again.
[Update Wednesday @ 8:10pm] Another bug was found after we rolled out to one rack. That bug has been found and fixed. We will evaluate exactly what we’re going to do with this deploy after testing tomorrow, but it will likely shift the timeline forward by one day. Meanwhile, we are rolling back the 170 regions that had previously received a 1.21 deploy so that for all simulators are once again running on version 1.20.1 of the server code.
The central updates to 1.21 are complete and things seem “nominal” at the moment, but of course we’ll be watching closely.
[Update Wednesday @ 10:25am]
The bug in the 1.21 Server code identified last night during an initial rollout to 1 rack has been found, fixed, and verified. We’d planning to proceed with the rollout to avoid delaying the code update another week. On the table for today are the central services updates and limited rolling restarts.
What’s Changed in 1.21 Server
The most notable fixes will be physics-related, and have been in testing in the Beta Preview for several days. No new viewer is required.
Read on for more information…
[16 April 2008, 2052] These issues have been resolved. Thank you for your patience.
Currently, we are seeing issues with in-world presence, object e-mails, group chats, logging, and other things related to the deployment. Please watch here for updates as they become available.
Grab this RSS feed