RIPE NCC Service Interruption
[apologies for duplicate mails] Dear Colleagues,
From 07:00 until 08:00 GMT, the RIPE NCC experienced an unexpected disruption to services. Although this may have caused delays to updates to the RIPE Whois Database, these updates have been processed normally.
The disruption may have also affected some of these RIPE NCC services: - whois.ripe.net - www.ripe.net - lirportal.ripe.net - ns*.ripe.net - ftp.ripe.net - www.aso.icann.org - www.nro.net - k.root-servers.org (Global node at the AMS-IX) - AS112.ripe.net We apologise for any interruption or delay to services. If you have any questions or concerns regarding this issue, please contact <ops@ripe.net>. Regards, RIPE NCC Operations
On Thu, 29 Sep 2005, RIPE NCC Operations wrote:
[apologies for duplicate mails]
Dear Colleagues,
From 07:00 until 08:00 GMT, the RIPE NCC experienced an unexpected disruption to services. Although this may have caused delays to updates to the RIPE Whois Database, these updates have been processed normally.
The disruption may have also affected some of these RIPE NCC services:
- whois.ripe.net - www.ripe.net - lirportal.ripe.net - ns*.ripe.net - ftp.ripe.net - www.aso.icann.org - www.nro.net - k.root-servers.org (Global node at the AMS-IX) - AS112.ripe.net
We apologise for any interruption or delay to services. If you have any questions or concerns regarding this issue, please contact <ops@ripe.net>.
Just curious, but has the cause of the disruption been determined, and if so, what was it ? Thanks, Roy
From: dns-wg-admin@ripe.net [mailto:dns-wg-admin@ripe.net] On Behalf Of Roy Arends Sent: 29 September 2005 10:35 To: RIPE NCC Operations Cc: dns-wg@ripe.net Subject: Re: [ripe.net #121131] [dns-wg] RIPE NCC Service Interruption
On Thu, 29 Sep 2005, RIPE NCC Operations wrote:
[apologies for duplicate mails]
Dear Colleagues,
From 07:00 until 08:00 GMT, the RIPE NCC experienced an unexpected disruption to services. Although this may have caused delays to updates to the RIPE Whois Database, these updates have been processed normally.
The disruption may have also affected some of these RIPE NCC services:
- whois.ripe.net - www.ripe.net - lirportal.ripe.net - ns*.ripe.net - ftp.ripe.net - www.aso.icann.org - www.nro.net - k.root-servers.org (Global node at the AMS-IX) - AS112.ripe.net
We apologise for any interruption or delay to services. If you have any questions or concerns regarding this issue, please contact <ops@ripe.net>.
Just curious, but has the cause of the disruption been determined, and if so, what was it ?
The disruption was caused by a network issue which we are currently investigating. Regards -- Brett Carr RIPE Network Coordination Centre Systems Engineer -- Operations Group Amsterdam, Netherlands GPG Key fingerprint = F20D B2A7 C91D E370 44CF F244 B6A1 EF48 E743 F7D8
On 29.09 10:30, RIPE NCC Operations wrote:
[apologies for duplicate mails]
Dear Colleagues,
From 07:00 until 08:00 GMT, the RIPE NCC experienced an unexpected disruption to services. ...
The disruption may have also affected some of these RIPE NCC services: ... - k.root-servers.org (Global node at the AMS-IX)
For the record: According to our monitoring this interruption has not at all affected the K root server. In particular our monitoring has detected no interruption in service and no shifting of traffic to other anycast instances of K. Daniel References: http://k.root-servers.org/stats/ams-ix/index.html http://dnsmon.ripe.net/dns-servmon/server/plot?server=k.root-servers.net&type=drops&tstart=1127887200&tstop=1127901599
On Fri, 30 Sep 2005, Daniel Karrenberg wrote:
On 29.09 10:30, RIPE NCC Operations wrote:
[apologies for duplicate mails]
Dear Colleagues,
From 07:00 until 08:00 GMT, the RIPE NCC experienced an unexpected disruption to services. ...
The disruption may have also affected some of these RIPE NCC services: ... - k.root-servers.org (Global node at the AMS-IX)
For the record:
According to our monitoring this interruption has not at all affected the K root server. In particular our monitoring has detected no interruption in service and no shifting of traffic to other anycast instances of K.
Yes indeed the problem briefly affected the website k.root-servers.org but not the global K-root at amsix as they sit behind different routers. Brett -- Brett Carr Ripe Network Coordination Centre System Engineer -- Operations Group Singel 258 Amsterdam NL http://www.ripe.net +31 627 546046 GPG Key fingerprint = F20D B2A7 C91D E370 44CF F244 B6A1 EF48 E743 F7D8
participants (4)
-
Brett Carr -
Daniel Karrenberg -
RIPE NCC Operations -
Roy Arends