Re: [atlas] No Atlas today: bad gateway

2020-03-31 Thread Jasper den Hertog
hi all, I can confirm that we’re still having problems, we’ve identified the problem and working on it right now, Greetings, Jasper den Hertog > On 31 Mar 2020, at 10:45, wrote: > > Looks like there's still a problem. Just got a refused to connect, followed > by Bad Gateway. > > Rich >

Re: [atlas] No Atlas today: bad gateway

2020-03-31 Thread Stephane Bortzmeyer
On Tue, Mar 31, 2020 at 10:40:28AM +0200, Jasper den Hertog wrote a message of 92 lines which said: > There definitely was a glitch, we saw it as well. And it just happened again.

Re: [atlas] No Atlas today: bad gateway

2020-03-31 Thread rsmithy
Looks like there's still a problem. Just got a refused to connect, followed by Bad Gateway. Rich -Original Message- From: ripe-atlas On Behalf Of Jasper den Hertog Sent: 31 March 2020 09:40 To: RIPE Atlas People Subject: Re: [atlas] No Atlas today: bad gateway hi all, There

Re: [atlas] No Atlas today: bad gateway

2020-03-31 Thread Jasper den Hertog
hi all, There definitely was a glitch, we saw it as well. Seems to have gone now, we’re investigating if we can see what happened, Greetings, Jasper den Hertog RIPE Atlas team > On 31 Mar 2020, at 10:38, Colin Johnston wrote: > > Seems fine me > > >> On 31 Mar 2020, at 09:33, Stephane

Re: [atlas] No Atlas today: bad gateway

2020-03-31 Thread Colin Johnston
Seems fine me > On 31 Mar 2020, at 09:33, Stephane Bortzmeyer wrote: > > https://atlas.ripe.net/ > > 502 Bad Gateway > nginx/1.16.1 > > COVID-19 on the server? >

[atlas] No Atlas today: bad gateway

2020-03-31 Thread Stephane Bortzmeyer
https://atlas.ripe.net/ 502 Bad Gateway nginx/1.16.1 COVID-19 on the server?