<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">I stand corrected. Magellan is also dead.<br><br><div dir="ltr">Regards,<br><div><br></div><div>Ernst J. Oud</div></div><div dir="ltr"><br><blockquote type="cite">On 19 Sep 2023, at 20:14, Ernst J. Oud <ernstoud@gmail.com> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><meta http-equiv="content-type" content="text/html; charset=utf-8">Hi,<div><br></div><div>If you look here, it shows that the back-end is dead:</div><div><br></div><div><a href="https://atlas.ripe.net/">https://atlas.ripe.net/</a></div><div><br></div><div>> 20 hours backlog, 0 results processed.</div><div><br></div><div>Magellan works fine, so streaming is ok, only storage of results seems to be severely impacted.<br><br><div dir="ltr">Regards,<br><div><br></div><div>Ernst J. Oud</div><div><br></div></div><div dir="ltr"><blockquote type="cite">On 19 Sep 2023, at 20:04, Gerdriaan Mulder <ripe@moeilijklastig.nl> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><span>Hi list,</span><br><span></span><br><span>A few hours ago (around 15:00Z), I launched some one-off measurements[1][2][3] on the platform for a select number of probes (based on ASN and region). The target in all three cases was 2a02:1807:1020:700::1 (no hostname, purely the address). Although the number of requested and participating probes varied a bit, it seems none of the measurements yielded any results.</span><br><span></span><br><span>At the time I didn't look at recent posts on this mailing list, nor was I aware of this ongoing incident[4] on the Atlas backend. It seems like that incident might be the cause of the (current) unavailability of these results.</span><br><span></span><br><span>It would be great if anyone can confirm that (viewing results of) user-defined measurements are affected as well.</span><br><span></span><br><span>Aside, I suppose the following messages on "My RIPE Atlas Dashboard" are also caused by the mentioned incident[4]?</span><br><span></span><br><span>--->8---</span><br><span>2023-09-18 16:40 UTC Your probe #11nnn was automatically untagged as "system: Resolves AAAA Correctly"</span><br><span>2023-09-18 16:40 UTC Your probe #11nnn was automatically untagged as "system: Resolves A Correctly"</span><br><span>2023-09-18 16:20 UTC Your probe #11nnn was automatically untagged as "system: IPv6 Works"</span><br><span>2023-09-18 16:20 UTC Your probe #11nnn was automatically untagged as "system: IPv4 Works"</span><br><span>---8<---</span><br><span></span><br><span>Perhaps the incident page[4] can include a few lines of the current (estimated) impact, as well.</span><br><span></span><br><span>Best regards,</span><br><span>Gerdriaan Mulder</span><br><span></span><br><span>[1] https://atlas.ripe.net/frames/measurements/60161706/ (default IPv6 traceroute)</span><br><span>[2] https://atlas.ripe.net/frames/measurements/60162230/ (IPv6 traceroute, paris=0)</span><br><span>[3] https://atlas.ripe.net/frames/measurements/60162753/ (default IPv6 ping)</span><br><span>[4] https://status.ripe.net/incidents/wfd7qywz3v68</span><br><span></span><br><span>-- </span><br><span>ripe-atlas mailing list</span><br><span>ripe-atlas@ripe.net</span><br><span>https://mailman.ripe.net/</span><br></div></blockquote></div></div></blockquote></body></html>