Limited support available due to connectivity issues in the office [update 3]

At around 11:30am CEST a machine from a nearby construction broke a cable that services all our communication lines in the Halle office.


For this reason we are currently unable to answer requests on our regular phone line but we are answering requests by email as usual.


Our services in the Oberhausen data center will experience a few limitations regarding system configuration updates and access to services that require live LDAP (such as web statistics access).


However, we expect regular application operations to continue without any further issues.

[Update 2011-05-09 6:42pm CEST]


Our ticket system is unfortunately currently also not available as email cannot be forwarded from our primary email server to the ticket system. If you need urgent assistance, please send an email to --- directly or call ---.


Our communications provider reviewed the situation at our premises around 5pm and hopes to start work on restoring connectivity by 7am tomorrow which would result in restored services at 8am.


We are also currently in the process of migrating our LDAP service to the data center to restore system configuration services and authentication.

[Update 2011-05-09 6:58pm CEST]

A few minutes ago a technician arrived and started repairing the broken cable. We thusly hope that services might be restored in a few hours already.

[Update 2011-05-09 8:54pm CEST]


The technician successfully repaired the broken cable. Connectivity to the office and thusly all services have been restored since around 7:30pm CEST.

Problems with IPv6 on 2011-04-14 [update 10:54am CEST]

We are currently experiencing problems with our IPv6 uplink. Users who access our services with IPv6 may experience outages. Our data center provider is informed and expects the problem to be resolved by 9:00am CEST.

[Update 10:07am]

Our provider is still working on the issue but has revoked the ETA for a solution. We'll provide another update as soon as we know more specifics or get another ETA.

[Update 10:54am]

IPv6 connectivity has been restored. Minor clean-up tasks are still being performed at the data center so currently as light chance remains for minor connectivity issues in the near future.

Infrastructure maintenance in the computing center, 2011-04-14 05:00 - 07:00 CEST

Our computing center operator announced that he will perform firmware updates on network components on 2011-04-14 05:00 - 07:00 CEST. Due to device restarts there will be short interruptions in network traffic.

If you have problems or questions, please send an email to support@gocept.com. We are also available via telephone: +49 345 12298890.

Unexpected downtime due to storage failure [update 3:48pm]

gocept.net is currently experiencing an infrastructure-wide downtime due to an error in the storage layer.

We are currently recovering the affected services and will provide further updates soon.

2011-04-12 2:58pm CEST


We identified an issue in the iSCSI server software which has a vendor-side patch available. After initial tests in our staging environment we are currently preparing a package to apply this patch in our production systems within the next 30 minutes.

2011-04-12 3:26pm CEST

The patch has been applied on the storage server that was currently hung and the VMs are being brought back into a working state now.

The other storage server that had the same issue but is currently working will receive this patch immediately as well, however, we do not expect further interruptions on VMs that are currently working as the patch applied cleanly in the staging systems while under load.

2011-04-12 3:48pm CEST

The patch was applied cleanly on all storage servers now. VMs that had a read-only filesystem have been rebooted and are back online now.

If you are affected, please check that your services are back online. Nagios still needs some time to get back to a complete green state and we'll go after any remaining issues in the next time.


We apologize for any inconvenience.

Comprehensive system update on Tuesday 2011-03-01 20:00 CET

On Tuesday next week we will perform a regular but comprehensive system update on all of our servers in the computing centre Oberhausen. Unfortunately we are not able to avoid downtime of services as the operating system updates will require a reboot of the systems.

Due to that, all services will be affected for periods during the time frame of 8pm CEST until midnight. CEST. We expect the interruptions of each individual service to be short.

We perform updates to sustain a secure, modern, and highly productive environment and to provide you with new features.

We apologize for any inconvenience caused by the update and will gladly respond to any questions you have. To contact us, send an email to support@gocept.com.

Update 2011-03-02 08:00

The update unfortunately required more fine-tuning than expected from the development and staging environments. We are currently in the process of rebooting the last servers and expect all services to be back to normal until 09:00 CET.

Storage server failure on 2011-02-17

Today we experienced a failure of the iSCSI storage server between 09:36 and 10:00 CET. This caused short service interruptions on some VMs. There was also a short outage of our mail server (mail.gocept.net), but no mails were lost.

We apologize for any inconvenience.

Short service interruption, yesterday, 2011-01-27 around 5:15pm CET [1. update]

On 2011-01-27 around 5:15pm we experienced a short outage in the data center where all of our services became unavailable for about 5 minutes.

The data center operator reported that a piece of their equipment rebooted itself thus causing the outage. They are still investigating the cause and will report to us when they are done. We will post an update at this place as soon as we get the report.

We apologize for any inconvenience cause by this outage.

Update 2011-01-28 1pm: We received news from the data center operator. The internet connection was down between 5:12pm and 5:19pm.

The outage was due to a router that presumably encountered a software error and thus stopped working. The data center NOC personnel responded to this immediately and restarted the router. They are currently communicating with the manufacturer of the router for further analysis and potentially applying a bug fix.