Hi Stephane and all, As Robert mentioned here before, we have been seeing some issues on the Atlas backend systems these past days. It's an intermittent problem so finding the root cause has proven to be a bit of a challenge and we are still investigating it. We have a notice up where we will post updates:
https://www.ripe.net/support/service-announcements/delays-in-ripe-atlas-measurement-result-processing To reassure you, there is no data lost because of these issues, but the delays are of course quite annoying, so we are investigating this problem actively at the moment. Apologies for the inconvenience. Romeo On 18/06/12 17:35 , Stephane Bortzmeyer wrote: > On Tue, Jun 12, 2018 at 03:54:44PM +0200, > Stephane Bortzmeyer <[email protected]> wrote > a message of 9 lines which said: > >>> The data storage backend had a few hickups today, meaning results >>> were queued and served with a delay around 10:00, 11:30 and >>> 13:30-15:00. No results were lost. >> >> I confirm it now works. Thanks. > > It seems it happens again "Total responsive: 0 Total allocated: 2 > Total requested: 2" > > Good thing is that it forced me to make my code less brittle :-) > <https://framagit.org/bortzmeyer/blaeu/commit/21759e20ef104383792d8c43fe84ef90f22a78c7> > >
