Measurement Result Broken
Hi everyone, I am getting trouble getting results for ping measurements. Looking at the web portal and JSON results, they are both empty. Measurement ID: 29049476 I also checked from the account of a colleague, same story. There is something broken in the pipeline? Best, Raffaele Sommese
Hi Raffaele and others, Our backend is having trouble processing the amount of incoming data. No results are lost but there's currently no ETA when the problem will be fixed. Apologies for the inconvenience, we're working on ways to make the backend more stable and more performant. Johan ter Beest RIPE Atlas Team On 04/02/2021 15:56, r.sommese@utwente.nl wrote:
Hi everyone, I am getting trouble getting results for ping measurements. Looking at the web portal and JSON results, they are both empty. Measurement ID: 29049476 I also checked from the account of a colleague, same story. There is something broken in the pipeline? Best, Raffaele Sommese
Dear All, As a follow-up to this issue: the operations team yesterday found the reason for these issues and by today morning the situation stabilised. As of now we don't have unexpected processing delays. We plan to publish a more detailed report later on. Regards, Robert Kisteleki On 2021-02-04 16:47, Johan ter Beest wrote:
Hi Raffaele and others,
Our backend is having trouble processing the amount of incoming data. No results are lost but there's currently no ETA when the problem will be fixed.
Apologies for the inconvenience, we're working on ways to make the backend more stable and more performant.
Johan ter Beest
RIPE Atlas Team
Dear Robert, Johan, Thanks a lot for the effort and the time spent solving the problem. Now everything works perfectly. Best Regards, Raffaele Sommese ________________________________ From: ripe-atlas <ripe-atlas-bounces@ripe.net> on behalf of Robert Kisteleki <robert@ripe.net> Sent: 10 February 2021 10:27:30 To: ripe-atlas@ripe.net Subject: Re: [atlas] Measurement Result Broken Dear All, As a follow-up to this issue: the operations team yesterday found the reason for these issues and by today morning the situation stabilised. As of now we don't have unexpected processing delays. We plan to publish a more detailed report later on. Regards, Robert Kisteleki On 2021-02-04 16:47, Johan ter Beest wrote:
Hi Raffaele and others,
Our backend is having trouble processing the amount of incoming data. No results are lost but there's currently no ETA when the problem will be fixed.
Apologies for the inconvenience, we're working on ways to make the backend more stable and more performant.
Johan ter Beest
RIPE Atlas Team
Thanks Robert and team! My results are looking much better today as well. -Steve
On Feb 10, 2021, at 1:27 AM, Robert Kisteleki <robert@ripe.net> wrote:
Dear All,
As a follow-up to this issue: the operations team yesterday found the reason for these issues and by today morning the situation stabilised. As of now we don't have unexpected processing delays.
We plan to publish a more detailed report later on.
Regards, Robert Kisteleki
On 2021-02-04 16:47, Johan ter Beest wrote:
Hi Raffaele and others, Our backend is having trouble processing the amount of incoming data. No results are lost but there's currently no ETA when the problem will be fixed. Apologies for the inconvenience, we're working on ways to make the backend more stable and more performant. Johan ter Beest RIPE Atlas Team
Thank you Robert and the rest of the Atlas team. All the results from past measurements seem to have come in and our new measures are coming in fast. - Hampton Moore
On Wed, 2021-02-10 at 10:27 +0100, Robert Kisteleki wrote: Dear All,
As a follow-up to this issue: the operations team yesterday found the reason for these issues and by today morning the situation stabilised. As of now we don't have unexpected processing delays.
We plan to publish a more detailed report later on.
Regards, Robert Kisteleki
On 2021-02-04 16:47, Johan ter Beest wrote:
Hi Raffaele and others,
Our backend is having trouble processing the amount of incoming data. No results are lost but there's currently no ETA when the problem will be fixed.
Apologies for the inconvenience, we're working on ways to make the backend more stable and more performant.
Johan ter Beest
RIPE Atlas Team
participants (5)
-
hamptonm＠usc.edu -
Johan ter Beest -
r.sommese＠utwente.nl -
Robert Kisteleki -
Steve Gibbard