Hi Chris, Thanks for the quick response. I don’t see any data coming in on any of our streams yet, even after restarting the collectors. So maybe there still is something broken there. You can check https://bit.org/network, which uses this data. Best regards, -- Teun Vink BIT | teun@bit.nl | +31 318 648 688 KvK: 09090351 | GPG: 0xFC8B25D6 | RIPE: TEUN-RIPE On 19 Jan 2021, at 16:14, Chris Amin wrote:

Hi Teun,

There were indeed issues with the stream for the past couple of hours. An upgrade of one of the backend servers caused an unexpected outage. Everything should be back to normal now, please let me know if there are any more issues.

Sorry for the inconvenience.

Regards, Chris Amin RIPE NCC

On 19/01/2021 15:28, Teun Vink wrote:

...

Hi,

RIPE Atlas API streams seem to have broken down today at ~12.05h CET. Is this a known problem?

Best regards,

Hi Chris, It seems to be working now, thanks! Best regards, Teun On 19 Jan 2021, at 16:38, Chris Amin wrote:

Hi Teun,

I will take a look into this and get back to you.

Chris

On 19/01/2021 16:32, Teun Vink wrote:

...

Hi Chris,

Thanks for the quick response. I don’t see any data coming in on any of our streams yet, even after restarting the collectors. So maybe there still is something broken there. You can check https://bit.org/network, which uses this data.

Best regards,

Hello, This was an unrelated problem: the data storage backend had a hickup. It developed a backlog and as a consequence it could not store and retrieve new results. According to our logs this event started approximately at 17:30 (CET) yesterday and resolved around 05:00 (CET) today. Admittedly, we have such delays occasionally and unfortunately more frequently in the last couple of weeks. Last night's event was particularly visible because it lasted longer. The backend team is investigating various options to improve the situation. We apologise for the inconvenience! Regards, Robert On 2021-01-20 06:33, Steve Gibbard wrote:

Hi Chris,

Maybe related, maybe not, we’re seeing our one-off traceroute measurements, which normally take under 90 seconds, taking upwards of ten minutes to complete over the last 10 days or so. Is there something going on that’s slowing measurement responses?

Thanks, Steve

Mistake, please ignore! On 20/01/2021 14:25, Chris Amin wrote:

On 19/01/2021 15:28, Teun Vink wrote:

...

Hi,

RIPE Atlas API streams seem to have broken down today at ~12.05h CET. Is this a known problem?

Best regards,