Hi Ernst, Because of the length of the outage, the system was not able to instantly process all of the incoming results that probes had been buffering on their local storage. This meant that although probes were reconnected to the infrastructure they could not deliver results -- they were trying to, but the system asked them to try later. This backlog has now been fully processed, so probes are submitting results freely and the delay (https://atlas.ripe.net/coverage/) is in healthy territory. Regards, Chris On Tue, 17 Sept 2024 at 13:11, Ernst J. Oud <ernstoud@gmail.com> wrote:
Johan,
Even fully connected probes (according their status via the API) did not deliver results.
Regards,
Ernst J. Oud
Met vriendelijke groet,
Ernst J. Oud
On 17 Sep 2024, at 12:49, Johan ter Beest <jterbeest@ripe.net> wrote:
When probes disconnect, they are not able to deliver the results they are collecting. The results will come in once the probe reconnects of course but by that time the value of the one-off is indeed gone...
Cheers, Johan
On Tue, 17 Sept 2024 at 12:00, Ernst J. Oud <ernstoud@gmail.com> wrote:
Current Atlas status shows a delay of over 16 hours. I created a measurement and no data is returned.
It appears this is not a problem with only probes disconnecting…
Ernst J. Oud ----- To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/ripe-atlas.ripe.net/ As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings. More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
----- To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/ripe-atlas.ripe.net/ As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings. More details at: https://www.ripe.net/membership/mail/mailman-3-migration/