This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/dns-wg@ripe.net/
[ripe.net #121131] [dns-wg] RIPE NCC Service Interruption
- Previous message (by thread): [dns-wg] RIPE NCC Service Interruption
- Next message (by thread): [ripe.net #121131] [dns-wg] RIPE NCC Service Interruption
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Roy Arends
roy at dnss.ec
Thu Sep 29 10:34:59 CEST 2005
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 at ripe.net>. Just curious, but has the cause of the disruption been determined, and if so, what was it ? Thanks, Roy
- Previous message (by thread): [dns-wg] RIPE NCC Service Interruption
- Next message (by thread): [ripe.net #121131] [dns-wg] RIPE NCC Service Interruption
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]