SingleHop

1. 141 - 10:17 (February 5, 2010)

   There was an issue with smtp connections trying to perform lookups on outgoing mail and failing. This was due to one of our resolvers failing. Some may have had trouble with smtp alerts and using leap.

   The problem has been taken care of and everything is back in order.

1. 139 - 04:38 (January 25, 2010)

   An issue in an upstream network caused increased packetloss and latency to a portion of customers. Network staff temporarily disabled links to the upstream until they reported the issue resolved.

   An official RFO will be provided as soon as possible.

No comments

1. 137 - 03:23 (January 16, 2010)

   The Access switch in Cab 207.25 has failed and is in the process of being replaced. Service will be restored shortly.
2. 137 - 03:43 (January 16, 2010)

   Full service has been restored as of 2:36AM CST. If you continue to experience technical difficulties please let us know by opening a support ticket.

   An offical RFO will be provided as soon as possible.

   Thank you for your continued patience in this matter.

1. 135 - 02:47 (January 15, 2010)

   The issue is completely resolved and was associated with one of our upstream providers. Our network recovered as designed and contained any domino effects from taking place. We will provide more information as soon as we can get more details from the upstream provider.

   Thanks!
2. 135 - 10:54 (January 15, 2010)

   All services have returned to normal operation at this time. We will update this post with an RFO shortly.
3. 135 - 11:06 (January 15, 2010)

   SingleHop Connectivity Issues Report-

   We experienced network issues last night due to emergency maintenance being performed by one of our upstream service providers, Abovenet. The emergency maintenance was unexpected, and although our systems responded as designed by self stabilizing and re-routing traffic through our secondary service provider, there was some packet loss of about 2 minutes during the upstream providers unexpected maintenance.

   Thanks for your patience.

1. 132 - 21:30 (December 27, 2009)

   Everything is back up again, thanks for your patience.

1. 131 - 06:55 (December 27, 2009)

   The fire department has informed us that the fire has been contained, but they may still turn off power to the entire building- which would most probably mean that the diesel generator would not be allowed to go on and the datacenter would go offline temporarily.
2. 131 - 07:18 (December 27, 2009)

   Fire containted, not affecting SingleHop operations. Fire occurred inside a non-SingleHop datacenter that is located in the same building as our datacenter. Fire department may still cut power but it is less probable now that the fire has been contained and ascertained as having started and stayed at the other non-SingleHop datacenter.

1. 130 - 07:56 (December 27, 2009)

   All clear. Fire extinguished. Chicago Fire Department has completed their work in the building, and left the building. SingleHop datacenter 1 was not affected in the fire in any way. Slight possibility that power may be pulled to inspect electrical damage, but it should not affect SingleHop.

   Thanks for your patience.

   SingleHop Team.

1. 129 - 17:46 (December 21, 2009)

   Maintenance Completed Without any Issues.

   Thanks.

1. 128 - 17:29 (December 16, 2009)

   The connectivity issues have been resolved. We will update on the details of the outage as soon as possible.
2. 128 - 18:19 (December 16, 2009)

   The issues experienced this afternoon are related to the link between our two datacenters being disrupted upstream, and some of our systems not reacting to the situation fast enough. We are awaiting more information from our upstream providers. A maintenance will need to be scheduled in the near future to ensure a quicker reaction from our systems.