Databases offline tonight
At midnight we had 2 databases go offline because of a SAN storage issue. The downtime lasted 29 minutes, ending at 12:29 AM Pacific time. We apologize for the downtime.
At midnight we had 2 databases go offline because of a SAN storage issue. The downtime lasted 29 minutes, ending at 12:29 AM Pacific time. We apologize for the downtime.
This morning from 3:30 to 8:00 AM Pacific time our eCards site was experiencing issues, which caused failures in sending eCards, as well as a temporary complete outage of the site. The problem has been remedied and measures have been taken to ensure the symptom behind the outage will not occur again. Sorry for any inconvenience.
At 10:30 AM PST on Tuesday (5/9/06) we'll be upgrading our forums site. We expect downtime of about 6-8 hours. Sorry for the inconvenience.
At 4:00PM PST on April 4th we started experiencing issues with one of our user databases. We are working to resolve this issue, and expect a recovery within 1 hour.
This user database has been brought back online, and should be fully operational, as of 5:20 PM PST.
Please talk with support@plaxo.com if you continue to notice any issues.
At 4:00PM PST on April 4th we started experiencing issues with one of our user databases. We are working to resolve this issue, and expect a recovery within 1 hour.
Please reference the following FAQ for more details on how this will affect users on that system.
http://support.plaxo.com/bin/answer.py?answer=1224
Between 9:45 AM and 11:00 AM PST we were expieriencing instability with some networking equipment, which caused either slow or no access to certain portions of our site. This problem has been resolved.
We were able to restore all systems affected by the service outage around 12:45pm PST. During the outage, some users may have experienced problems accessing their Plaxo Online account and some new users were unable to sign up. We apologize for the inconvenience and we are still investigating the root cause of the outage. If you continue to experience difficulties accessing your Plaxo Online account, please contact Plaxo Support
Some users may experience problems accessing their Plaxo Online account due to an outage located in our datacenter. The operations team is currently investigating the outage and working to restore access to those affected users as soon as possible.
We are working to replace the hardware that houses this database, and have an ETA of mid-tomorrow before this problem is fully resolved.While we're working hard to get the replacement system into place, we're being very cautious with this migration as we want to ensure there is no data loss. Because of this it looks like the migration to the new hardware, which will close out this issue, won't happen until late tomorrow. Sorry for the inconvenience.
We've finalized the migration to our new hardware late yesterday. Sorry for the delay, but we were able to provide some additional stability to the current system, so took that time to perform some heavier data validation on the new system. Please contact support@plaxo.com if you continue to have any problems.
We are working to replace the hardware that houses this database, and have an ETA of mid-tomorrow before this problem is fully resolved.
While we're working hard to get the replacement system into place, we're being very cautious with this migration as we want to ensure there is no data loss. Because of this it looks like the migration to the new hardware, which will close out this issue, won't happen until late tomorrow. Sorry for the inconvenience.
At 06:30 PST on March 16th we started experiencing issues with one of our user databases. We are working to replace the hardware that houses this database, and have an ETA of mid-tomorrow before this problem is fully resolved. This should be affecting ~3% of users, that will see periodic failures.
Please reference the following FAQ for more details on how this will affect those users.
http://support.plaxo.com/bin/answer.py?answer=1224
One of our backend database servers has recently been experiencing corruption. This corruption has caused us to failover to our secondary system, which isn't as powerful. The switch, while providing stable performance, proved to be an issue because it caused a seemingly never ending string of slow requests and timeouts for those affected users.
Yesterday morning (around 9AM PST) we swapped back to our primary system after a restore and those users were once again online. We are making changes to that back-end server pair to provide better redundancy and a more stable environment.