| Month |
Measured
Availability |
Planned Outages |
Notes: |
 |
| 6/2008 |
99.998% |
0.002% |
Some customers experienced intermittent connectivity when the new AT&T circuit was brought online. |
| 5/2008 |
100% |
0% |
None |
| 4/2008 |
100% |
0% |
None |
| 2/2008 |
100% |
0% |
Data Center DNS servers failed and caused connectivity / resolution issues for some customers. |
| 1/2008 |
100% |
0% |
None |
| 12/2007 |
100% |
0% |
None |
| 11/2007 |
100% |
0% |
None |
| 10/2007 |
100% |
0% |
None |
| 9/2007 |
100% |
0% |
None |
| 8/2007 |
99.989% |
.011% |
Scheduled maintenance to replace primary router. |
| 7/2007 |
100% |
0% |
None |
| 6/2007 |
100% |
0% |
None |
| 5/2007 |
99.98% |
0% |
Upstream Provider had routing issue for 9 Minutes. Partial loss of connectivity. |
| 4/2007 |
99.97% |
0% |
24 min outage caused by a border switch which stopped passing packets until restarted. |
| 3/2007 |
100% |
0% |
None |
| 2/2007 |
100% |
0% |
None |
| 1/2007 |
100% |
0% |
None |
| 12/2006 |
100% |
0% |
None |
| 11/2006 |
99.857% |
0% |
Denial of Service attack against a customer affected performance and availability intermittently over the course of 1hr. A policy change has been made which will prevent this same event from happening again. A correponding firewall change has been implimented to enforce this policy change. |
| 10/2006 |
100% |
0% |
None |
| 9/2006 |
99.86% |
0% |
At 4:06am PDT Sunday 9/10/06, our border firewall stopped passing packets for an as yet undetermined reason. This event caused a 1hr 5min outage for discovery, recovery and investigation. |
| 8/2006 |
100% |
0% |
None |
| 7/2006 |
99.879% |
0% |
1) A new customer was the victim of a massive Denial of Service attack for 14min which also affected most of our customers with high packet loss. 2) The Denial of Service attack returned for two blasts during a 40min period. The customer was removed from network permanently and we are making further improvements to our network. |
| 6/2006 |
99.9977% |
0% |
1) Upgraded to HSRP connection to Data Center core. This required a brief cable change (15 seconds). 2) Some routing issues caused by a corrupt CEF (Cisco Express Forwarding) table in one router caused some customers to have intermittent routing issues to specific Internet addresses. Not all customers were affected, and not all destinations were affected. However, some customers may have been affected for hours. Resolution of this issue required a reboot of one of the aggregation routers. With the HSRP connection, this affected connectivity for about 15 seconds. |
| 5/2006 |
100% |
0% |
None |
| 4/2006 |
100% |
0% |
None |
| 3/2006 |
100% |
0% |
None |
| 2/2006 |
99.993% |
0% |
During a major power upgrade of the Data Center facility on 2/23/06, there was an unplanned 90 second power outage on some circuits. This caused some customers servers to reboot. See the Data Center CEO's explanation (published shortly). The uptime recorded includes 3min downtime for system reboots. |
| 1/2006 |
99.505% |
0% |
During an upgrade of collocation space two power circuits were tripped due to uneven load. |
|
Reference: 1 month = 43,829.0639 minutes
How is network uptime calculated ?
Network Uptime or availability is calculated by subtracting the reported down time in minutes from 43,829.0639 then dividing that number by 43,829.0639. This will give us a percentage of uptime.
|
