We updated the service to ExtremePlanner 3.2 over the weekend of April 13th, 2008. This update went smooth and with little interruption to service. The monitoring service reported about 3 minutes of downtime during the update.
You can see the list of changes in version 3.2 by visiting the ExtremePlanner Web Site.
During the upgrade we made configuration changes to our application server. These changes inadvertently broke compatibility with the Eclipse plugin. Compatibility has been restored as of April 16th, 2008.
We hope that you enjoy the updated version of the planner. If you find any bugs or usability problems with this release, please send us email.
Thursday, April 17, 2008
Monday, April 7, 2008
Cisco IOS Failure
Many of you already know that we had two outages in March, one that was about an hour long, and another that was 4 hours long. These outages, at first, appeared to be the result of administrative incompetence. When the second attack occured, though, we soon realized that this was the result of a sophisticated exploit on a bug in the Cisco IOS used to manage our BGP routers.
CERT issued a vulnerability notice on March 27, 2008. You can read it here (VU936177).
Since this IOS update release, the attacks have been successfully managed and we are regaining our confidence in our colocation partners.
This type of attack can affect any ISP in any part of the world. For that reason, we are carefully screening our backup ISP providers to ensure that they have the proper updates applied to their infrastructure. We can't afford to subject our customers to another one of these attacks when it can be prevented with a bug fix to software.
We are working to expand our reliability infrastructure and provide outstanding service to all of our customers. Our screening process does take time, though, and we need to make sure that our decision does not adversely affect the distributed information sharing that all of our customers require.
CERT issued a vulnerability notice on March 27, 2008. You can read it here (VU936177).
Since this IOS update release, the attacks have been successfully managed and we are regaining our confidence in our colocation partners.
This type of attack can affect any ISP in any part of the world. For that reason, we are carefully screening our backup ISP providers to ensure that they have the proper updates applied to their infrastructure. We can't afford to subject our customers to another one of these attacks when it can be prevented with a bug fix to software.
We are working to expand our reliability infrastructure and provide outstanding service to all of our customers. Our screening process does take time, though, and we need to make sure that our decision does not adversely affect the distributed information sharing that all of our customers require.
24/7 Monitoring
We have implemented 24/7 monitoring and early outage reporting through SiteUptime (www.siteuptime.com). The connectivity issues we had in March made us realize that our current local monitoring startegy did not allow us to react to the failures adequately.
The SiteUptime monitoring service will be monitoring from San Francisco and London. If necessary, we'll expand that monitoring to include other key Internet relay hubs that represent more of our global customer base.
XPLive is dedicated to keeping your service operational 24/7. We can not guarantee 100% availability because we are at the mercy of our vendors, such as Cisco. More changes to our reliability infrastructure are coming.
The SiteUptime monitoring service will be monitoring from San Francisco and London. If necessary, we'll expand that monitoring to include other key Internet relay hubs that represent more of our global customer base.
XPLive is dedicated to keeping your service operational 24/7. We can not guarantee 100% availability because we are at the mercy of our vendors, such as Cisco. More changes to our reliability infrastructure are coming.
Subscribe to:
Posts (Atom)