Dear Colleagues, [We are sorry for any duplicate mails you might receive] This afternoon we experienced a problem with our IPv6 router. Problems started at 13:50, and we are still facing problem. None of our IPv4 services are affected, as these are dealt with by other routers. Affected services, which we offer on IPv6 are: - FTP: ftp.ripe.net - WWW: www.ripe.net - DNS: ns*.ripe.net - Whois: whois.ripe.net We suspect that an interfacecard of our dedicated IPv6 router is faulty, and at the moment an engineer is working on it. The long term solution is that we will replace this router. We apologise for any disruption or delay this may have caused. If you have any further questions about this matter, please send an e-mail to ops@ripe.net. Kind regards Andrei Robachevsky CTO, RIPE NCC
Dear Colleagues, With reference to the email from Andrei Robachevsky below the affected services are now up again. The uptime was 20:00. The outage was caused by a router hardware failure. We apologise for any inconvenience this may have caused. Regards, Brian Riddle. IT Manager, RIPE NCC Andrei Robachevsky wrote:
Dear Colleagues,
[We are sorry for any duplicate mails you might receive]
This afternoon we experienced a problem with our IPv6 router. Problems started at 13:50, and we are still facing problem.
None of our IPv4 services are affected, as these are dealt with by other routers.
Affected services, which we offer on IPv6 are: - FTP: ftp.ripe.net - WWW: www.ripe.net - DNS: ns*.ripe.net - Whois: whois.ripe.net
We suspect that an interfacecard of our dedicated IPv6 router is faulty, and at the moment an engineer is working on it.
The long term solution is that we will replace this router.
We apologise for any disruption or delay this may have caused. If you have any further questions about this matter, please send an e-mail to ops@ripe.net.
Kind regards
Andrei Robachevsky CTO, RIPE NCC
participants (2)
-
Andrei Robachevsky
-
briddle@ripe.net