Scheduled work on RIPE Atlas
Dear RIPE Atlas users, We have planned maintenance on the main RIPE Atlas backend database tomorrow (Tuesday, 16 July) starting at 08:00 UTC, 10:00 Amsterdam local time. We expect complete unavailability of the service for a short while and further intermittent delays during the day. During this time the website (UI and APIs) will not be responding (properly). This also means that requests for new measurements will be denied or delayed. Data from existing measurements will still be collected normally, though access to them will be impacted. Our apologies for the inconvenience. Regards, Robert Kisteleki
Dear All, The publicly visible part of this work finished around noon (local time) and all functions should be back to normal. Regards, Robert On 2019-07-15 12:00, Robert Kisteleki wrote:
Dear RIPE Atlas users,
We have planned maintenance on the main RIPE Atlas backend database tomorrow (Tuesday, 16 July) starting at 08:00 UTC, 10:00 Amsterdam local time. We expect complete unavailability of the service for a short while and further intermittent delays during the day.
During this time the website (UI and APIs) will not be responding (properly). This also means that requests for new measurements will be denied or delayed. Data from existing measurements will still be collected normally, though access to them will be impacted.
Our apologies for the inconvenience.
Regards, Robert Kisteleki
Hi! Does this maintenance was related with DNS measurements? I generated today 60 DNS, got their IDs, I see in web UI that they are running but when I want to open them or search for them I get nulls or messages like " This measurement most probably does not exist (yet).". Can you for example check measurement 22378601? Regards, Grzegorz From: Robert Kisteleki <robert@ripe.net> Organization: RIPE NCC Date: Tuesday 2019-07-16 at 13:47 To: "ripe-atlas@ripe.net" <ripe-atlas@ripe.net> Subject: Re: [atlas] Scheduled work on RIPE Atlas Dear All, The publicly visible part of this work finished around noon (local time) and all functions should be back to normal. Regards, Robert On 2019-07-15 12:00, Robert Kisteleki wrote: Dear RIPE Atlas users, We have planned maintenance on the main RIPE Atlas backend database tomorrow (Tuesday, 16 July) starting at 08:00 UTC, 10:00 Amsterdam local time. We expect complete unavailability of the service for a short while and further intermittent delays during the day. During this time the website (UI and APIs) will not be responding (properly). This also means that requests for new measurements will be denied or delayed. Data from existing measurements will still be collected normally, though access to them will be impacted. Our apologies for the inconvenience. Regards, Robert Kisteleki
Hi Grzegorz, Apologies for this, it was actually an unrelated issue to do with synchronizing certain DNS measurements. Those measurements should now work as normal. Regards, Chris Amin RIPE NCC On 18/07/2019 12:05, Ponikierski, Grzegorz wrote:
Hi!
Does this maintenance was related with DNS measurements? I generated today 60 DNS, got their IDs, I see in web UI that they are running but when I want to open them or search for them I get nulls or messages like "This measurement most probably does not exist (yet).". Can you for example check measurement *22378601*?
Regards,
Grzegorz
*From: *Robert Kisteleki <robert@ripe.net> *Organization: *RIPE NCC *Date: *Tuesday 2019-07-16 at 13:47 *To: *"ripe-atlas@ripe.net" <ripe-atlas@ripe.net> *Subject: *Re: [atlas] Scheduled work on RIPE Atlas
Dear All,
The publicly visible part of this work finished around noon (local time)
and all functions should be back to normal.
Regards,
Robert
On 2019-07-15 12:00, Robert Kisteleki wrote:
Dear RIPE Atlas users,
We have planned maintenance on the main RIPE Atlas backend database
tomorrow (Tuesday, 16 July) starting at 08:00 UTC, 10:00 Amsterdam local
time. We expect complete unavailability of the service for a short while
and further intermittent delays during the day.
During this time the website (UI and APIs) will not be responding
(properly). This also means that requests for new measurements will be
denied or delayed. Data from existing measurements will still be
collected normally, though access to them will be impacted.
Our apologies for the inconvenience.
Regards,
Robert Kisteleki
Works like magic. Thank you! Regards, Grzegorz From: Chris Amin <camin@ripe.net> Date: Thursday 2019-07-18 at 13:34 To: "ripe-atlas@ripe.net" <ripe-atlas@ripe.net> Subject: Re: [atlas] Scheduled work on RIPE Atlas Hi Grzegorz, Apologies for this, it was actually an unrelated issue to do with synchronizing certain DNS measurements. Those measurements should now work as normal. Regards, Chris Amin RIPE NCC On 18/07/2019 12:05, Ponikierski, Grzegorz wrote: Hi! Does this maintenance was related with DNS measurements? I generated today 60 DNS, got their IDs, I see in web UI that they are running but when I want to open them or search for them I get nulls or messages like "This measurement most probably does not exist (yet).". Can you for example check measurement *22378601*? Regards, Grzegorz *From: *Robert Kisteleki <robert@ripe.net<mailto:robert@ripe.net>> *Organization: *RIPE NCC *Date: *Tuesday 2019-07-16 at 13:47 *To: *"ripe-atlas@ripe.net<mailto:ripe-atlas@ripe.net>" <ripe-atlas@ripe.net<mailto:ripe-atlas@ripe.net>> *Subject: *Re: [atlas] Scheduled work on RIPE Atlas Dear All, The publicly visible part of this work finished around noon (local time) and all functions should be back to normal. Regards, Robert On 2019-07-15 12:00, Robert Kisteleki wrote: Dear RIPE Atlas users, We have planned maintenance on the main RIPE Atlas backend database tomorrow (Tuesday, 16 July) starting at 08:00 UTC, 10:00 Amsterdam local time. We expect complete unavailability of the service for a short while and further intermittent delays during the day. During this time the website (UI and APIs) will not be responding (properly). This also means that requests for new measurements will be denied or delayed. Data from existing measurements will still be collected normally, though access to them will be impacted. Our apologies for the inconvenience. Regards, Robert Kisteleki
participants (3)
-
Chris Amin -
Ponikierski, Grzegorz -
Robert Kisteleki