- 17-10-24ECOFED wint ICT Innovatieprijs Regio Foodvalley 2024
- 01-08-24BIT geeft kaarten weg voor F1 in Zandvoort
- 24-04-24Status.bit.nl in nieuw jasje!
- 12-04-24Nieuw bij BIT: GPU hosting
- 25-03-24BIT breidt netwerkconnectiviteit uit met aansluiting op NL-ix^2
- 13-03-24No More Leaks: Samenwerken tegen cybercriminaliteit
- 03-03-24Geen verandering twee jaar na invoering sancties tegen Russische media: FOIC roept (wederom) op tot einde van ondemocratische censuur
- 29-01-24Onzichtbare upgrades
- 16-01-24BIT's Wido Potters wint Felipe Rodriquez Award voor inzet voor privacy
- 10-01-24BIT en partners zetten de koers voor een gedecentraliseerde Europese cloud met ECOFED-project
Disturbance DNS and network
04-03-2015 13:30:00
- 04-03-2015 16:00:00
Status:
opgelost
We have noticed a disturbance on DNS.
The underlying cause is being investigated by our engineers.
Follow the incident on our website for updates concerning this incident.
Update placed on 03/04/2015, 15:32
Our network is also (partially) impacted by this disturbance.
Update placed on 03/04/2015, 16:00
A problem was found on a router in London, we have shut the traffic from and to this router. This has isolated the problem.
The incident is 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 placed on 05/04/2015, 00:43
The incident report can be found here.
The underlying cause is being investigated by our engineers.
Follow the incident on our website for updates concerning this incident.
Update placed on 03/04/2015, 15:32
Our network is also (partially) impacted by this disturbance.
Update placed on 03/04/2015, 16:00
A problem was found on a router in London, we have shut the traffic from and to this router. This has isolated the problem.
The incident is 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 placed on 05/04/2015, 00:43
The incident report can be found here.