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/ripe-atlas@ripe.net/
[atlas] Infrastructure upgrades
- Previous message (by thread): [atlas] Infrastructure upgrades
- Next message (by thread): [atlas] Infrastructure upgrades
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Chris Amin
camin at ripe.net
Wed Sep 6 17:57:59 CEST 2017
Dear John, You are correct, we worked on one of the anchor controllers today and we have identified an issue that caused more of an impact than expected. We are in the process of fixing this: you should already see some of the broken anchors stabilizing, and you can expect to see the remaining ones fixed shortly. We'll provide an update when everything is back to normal. Regards, Chris On 06/09/2017 17:28, ripe-atlas at johnbond.org wrote: > Hello Robert, > > I just wanted to confirm that this work is why we see missing data in DNSMON for a number of the anchors > > Thanks John > >> On Aug 24, 2017, at 3:47 PM, Robert Kisteleki <robert at ripe.net> wrote: >> >> Dear all, >> >> Yesterday we began infrastructure (OS) upgrades on our controllers. As a >> consequence each probe will be disconnected for an hour or two. This can >> trigger notifications, if you have that configured to a sensitive enough >> setting. >> >> Regards, >> Robert Kisteleki >> RIPE NCC >> >> > > >
- Previous message (by thread): [atlas] Infrastructure upgrades
- Next message (by thread): [atlas] Infrastructure upgrades
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]