Maintenance or incident?
% curl https://atlas.ripe.net/ curl: (7) Failed to connect to atlas.ripe.net port 443: Connection refused It started around 1015 UTC.
Hi Stephane, This is an incident... the relevant folks are aware, and looking into it. Regards, Anand Buddhdev On 07/01/2020 13:40, Stephane Bortzmeyer wrote:
% curl https://atlas.ripe.net/ curl: (7) Failed to connect to atlas.ripe.net port 443: Connection refused
It started around 1015 UTC.
Thank you for your quick response :) On 07.01.20 12:50, Anand Buddhdev wrote:
Hi Stephane,
This is an incident... the relevant folks are aware, and looking into it.
Regards, Anand Buddhdev
On 07/01/2020 13:40, Stephane Bortzmeyer wrote:
% curl https://atlas.ripe.net/ curl: (7) Failed to connect to atlas.ripe.net port 443: Connection refused
It started around 1015 UTC.
On Tue, Jan 07, 2020 at 01:50:28PM +0300, Anand Buddhdev <anandb@ripe.net> wrote a message of 14 lines which said:
This is an incident... the relevant folks are aware, and looking into it.
It works again, thanks.
On 2020-01-07 11:54, Stephane Bortzmeyer wrote:
On Tue, Jan 07, 2020 at 01:50:28PM +0300, Anand Buddhdev <anandb@ripe.net> wrote a message of 14 lines which said:
This is an incident... the relevant folks are aware, and looking into it.
It works again, thanks.
Yes, indeed. We also just tweeted about it. The service (UI and API) was unavailable for about 30 minutes due to a bug in newly deployed code. Measurements were unaffected and results were collected normally. Apologies again, Robert
participants (4)
-
Anand Buddhdev -
Georg Kahest -
Robert Kisteleki -
Stephane Bortzmeyer