- 05-02-24VDC and VM management environment briefly offline (solved)
- 11-10-23interruption of BIT-HOST4
- 17-09-23CephFS storage issue
- 26-07-23Load balancer failure
- 04-07-23One of the shared mysql servers temporarily unavailable
- 13-04-23Short, limited temperature increase
- 06-04-23Short interruption webmail.bit.nl
- 01-03-23Network interruption leaf-sw5.bit-2a
- 22-02-23Malfunction email platform
- 21-02-23Disruption IMAP email services
Network interruption
21-01-2018 17:56:41
- 21-01-2018 18:15:25
Status:
resolved
Part of our network are unreachable. The cause of this incident is under investigation. We are working on resolving this problem. The moment more info is available it will be published on our website.
Update 18:10h
The problem has been identified and taken care of. More investigations will be done to identify the trigger of the problem. This incident has been resolved.
If you have any questions regarding this incident, please contact the Customer Care department by phone on +31 (0)318 648 688 or by email on support@bit.nl.
Update 22-01-2018, 13:00
This disruption was caused by a human error during a config change which was being made for one specific customer who was experiencing an outage. Due to miscommunication an incorrect configuration was applied, which resulted in a loop in parts of the network. This caused network links to be saturated, redering parts of our network unreachable. This was immediately observed by the engineer involved, who shut down one of the links causing the loop to break. As a result, the required configuration change has not been performed.
Update 18:10h
The problem has been identified and taken care of. More investigations will be done to identify the trigger of the problem. This incident has been resolved.
If you have any questions regarding this incident, please contact the Customer Care department by phone on +31 (0)318 648 688 or by email on support@bit.nl.
Update 22-01-2018, 13:00
This disruption was caused by a human error during a config change which was being made for one specific customer who was experiencing an outage. Due to miscommunication an incorrect configuration was applied, which resulted in a loop in parts of the network. This caused network links to be saturated, redering parts of our network unreachable. This was immediately observed by the engineer involved, who shut down one of the links causing the loop to break. As a result, the required configuration change has not been performed.