[atlas] Delays in backend…

I forgot to mention that the result stream 
(https://atlas-stream.ripe.net/) does not share fate with the data 
backend, it is delivering results as expected.

Cheers,
Robert


On 2023-07-01 13:06, Robert Kisteleki wrote:
> Hello,
> 
> I can confirm that the data storage backend has been struggling in the 
> last couple of days. Our operations people are trying to come up with a 
> permanent solution, but the problem keeps reappearing.
> 
> The status page has entries about these issues - though admittedly not 
> about all the hickups. Apologies for that, we'll add one for the current 
> instance.
> 
> We have a publicly available delay indicator on the front page of Atlas, 
> that helps if you're unsure.
> 
> Regards,
> Robert
> 
> 
> On 2023-07-01 12:32, Ernst J. Oud wrote:
>> L.S.
>>
>> Saturday July 1st. Just did a test, first result reported in the web 
>> interface after 25 minutes! Results of the other probes in this test 
>> still unreported.
>>
>> Come on guys. There is something terribly wrong in the back-end for 
>> three days now. I know it is a free service but is there no monitoring 
>> on this?
>>
>> Status page still mentions no issues. There clearly is.
>>
>> Met vriendelijke groet / Regards,
>>
>> Ernst J. Oud
>>
>>> On 30 Jun 2023, at 13:24, Ernst J. Oud <ernstoud at gmail.com> wrote:
>>>
>>> Hi,
>>>
>>> Measurements stream fine in Magellan, but results only show up in the 
>>> web interface after - in extreme cases - hours.
>>>
>>> The RIPE status info says:
>>> Resolved
>>> This incident has been resolved.
>>> Posted 1 day ago. Jun 29, 2023 - 10:11 UTC
>>> Investigating
>>> We are experiencing issues with the RIPE Atlas backend and currently 
>>> are investigating this issue.
>>> Posted 1 day ago. Jun 29, 2023 - 08:55 UTC
>>>
>>>
>>>
>>>
>>>
>>>
>>> But clearly this has not been resolved!
>>>
>>> Regards,
>>>
>>> Ernst J. Oud
>>> -- 
>>> ripe-atlas mailing list
>>> ripe-atlas at ripe.net
>>> https://mailman.ripe.net/
>>
>