Author: Texo [Steve]

11 December 2012 7:50PM

There is a problem with the server Chaucer which we’re investigating.

8:10 PM It appears to be a hardware problem, which a technician is troubleshooting.

8:38 PM We’re still waiting to hear from the technician

9:20PM No news yet, unfortunately.

9:30 PM A full hardware swap (motherboard etc) has to be done. Should not be too much longer, and then we’ll have to update a few bits of software before being able to bring the server back online.

01:10 AM Chaucer is back online, and running without any problems or data loss.

19 October 2012 10:45AM

There appears to be a connectivity problem in our Cape Town datacentres. We are investigating.

10:51AM

Everything appears to be back online, but we’re keeping a close eye on things, as always.

18 September 2012 3:50PM

We are currently seeing routing issues which are causing slowness and timeouts on some of our servers in London. DC engineers are investigating.

4:06PM The problem appears to have been fixed. If you’re having any issues, please submit a support ticket so that we can take a look.

13:40 There seems to be a peering issue which is affecting connectivity to some servers in Cape Town. Network engineers are investigating.

13:57 Unfortunately, there is no news yet. The DC engineers are still looking for the cause of the problem.

14:40 Frustratingly, they are still searching for the cause of the problem, which seems to be affecting all ISPs

15:15 MTN Business (who provide connectivity to the DC) have confirmed that they have a routing problem and are attending.

15:51 Looks like MTN Business has sorted their problems out, and everything’s back to normal. I am so sorry about this – we pay a premium for the best upstream providers and expect better service than this!

15 August 2012 2:45PM There is currently a problem at our Cape Town DC resulting in packet loss. This means that clients hosted in Cape Town will have problems (very slow, timeouts, inaccessible) accessing their websites and email.

The DC assures me that this will be fixed within 30-60 minutes.

3:00PM update from the datacentre: “We are currently investigating packetloss that is causing severe disruption to services hosted in Cape Town. At present, the cause is still unclear…”

4:10PM update from the datacentre: “Investigation has revealed that the Cape Town datacentre has been the target of a severe DDOS attack. Our network engineers are working to put a stop to the attack. Connectivity issues continue to persist intermittently.”

(Interested in finding out more? Wikipedia article on DDOS)

5:30PM Everything appears to be back to normal. If you’re having any problems, please submit a support ticket so that we can take a look.

15 July 2012 8PM

Routing problems in our London DC have made the servers Hegeley and Ratchet inaccessible. DC engineers are working on the problem.

8:40PM the problem has been resolved.

27 June 2012 01:18 The server Hegeley is offline. We’re busy working with DC engineers to determine the cause and fix it.

01:47 Server is back online. We’re investigating to find the cause so that this doesn’t happen again.

17 June 2012 00:10 we are aware of routing problems affecting servers in our London Datacentre and causing intermittent timeouts on some servers. DC engineers are working to trace and resolve the issue.

02:00 All routing issues have been resolved

Wed 06 June 2012 21:37 There is a problem with the connection to the Cape Town DC which has made all Texo servers in Cape Town inaccessible. DC engineers are attending to the problem.

21:55 It appears that MTN Business (which supplies bandwidth to the Cape Town DC) has had a complete network failure.

22:02 Everything appears to be back online again.

30 May 2012 19:47 We’re seeing routing issues affecting servers in our London DC, resulting in slow websites, timeouts and intermittent short outages.

The Datacentre’s network engineers are attending.

20:48 The routing issues have been isolated, and everything should be returning to normal shortly.

21:00 green lights across the board, but we’ll keep monitoring to be sure.