Today, from 1:41pm until shortly before 3p pacific time, we had an unscheduled and unplanned outage due to a denial of service (DoS) http://en.wikipedia.org/wiki/Denial-of-service_attack attack on our core load-balancing servers. That basically means that we were flooded with malicious amounts traffic our upstream providers were unable to handle, and we couldn’t respond to the requests of real users. During this time, all Posterous-hosted sites were out.
Since that time, we have brought up a new load balancer on a new address to try to evade the attack. For most people who use a .posterous.com address for their site, this means that your site should be back up shortly, if it’s not already. However, if you use a custom domain for your Posterous site, you are still pointed to our old address, which remains under attack.
If your site uses a custom domain and is still down, please accept our most sincere apology. There are two options for you at this point:
1. Do nothing. At some point, the DoS attack will cease, and we will again be responding to our primary address. This could be several minutes from now, several hours, or several days. There’s no way of knowing, but your site will once again work properly as soon as the attack is over.
2. Change your domain to point to our new address. As mentioned, we have set up a new address that can successfully accept traffic. If you want to point your server to this address, you may do so, and we’ll allow traffic on both addresses for the forseeable future. To change servers, follow the instructions on this page http://posterous.com/help/custom_domain , removing the old address, and adding an A record with our new address: 209.20.70.130 No data was lost during this outage, and if you sent in a post via e-mail, while it may not post immediately, it should come through and post in the coming hours. Again, we deeply regret the outage, and want to assure you that we’re doing everything we can to get the original address back up and mitigate these types of situations in the future.
Thanks for your patience, and do let us know if you have any questions.
View this post http://blog.posterous.com/todays-outage-and-changes-for-custom-domains#comment
Sent from my BlackBerry® powered by Virgin Mobile.
Since that time, we have brought up a new load balancer on a new address to try to evade the attack. For most people who use a .posterous.com address for their site, this means that your site should be back up shortly, if it’s not already. However, if you use a custom domain for your Posterous site, you are still pointed to our old address, which remains under attack.
If your site uses a custom domain and is still down, please accept our most sincere apology. There are two options for you at this point:
1. Do nothing. At some point, the DoS attack will cease, and we will again be responding to our primary address. This could be several minutes from now, several hours, or several days. There’s no way of knowing, but your site will once again work properly as soon as the attack is over.
2. Change your domain to point to our new address. As mentioned, we have set up a new address that can successfully accept traffic. If you want to point your server to this address, you may do so, and we’ll allow traffic on both addresses for the forseeable future. To change servers, follow the instructions on this page http://posterous.com/help/custom_domain , removing the old address, and adding an A record with our new address: 209.20.70.130 No data was lost during this outage, and if you sent in a post via e-mail, while it may not post immediately, it should come through and post in the coming hours. Again, we deeply regret the outage, and want to assure you that we’re doing everything we can to get the original address back up and mitigate these types of situations in the future.
Thanks for your patience, and do let us know if you have any questions.
View this post http://blog.posterous.com/todays-outage-and-changes-for-custom-domains#comment
Sent from my BlackBerry® powered by Virgin Mobile.
No comments:
Post a Comment