This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] Problem in status checks?
- Previous message (by thread): [atlas] Problem in status checks?
- Next message (by thread): [atlas] New on RIPE Labs: Insights from RIPE Atlas Probe Disconnections
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Chris Amin
camin at ripe.net
Sat Oct 14 10:03:43 CEST 2017
Hi Stephane, We are currently experiencing some problems with one of our backends which is affecting various API endpoints, including status checks. We are looking into the root cause now. Regards, Chris On 14/10/2017 09:11, Stephane Bortzmeyer wrote: > Error 500 when trying to retrieve status checks: > > % curl -v 'https://atlas.ripe.net/api/v2/measurements/2060427/status-check?permitted_total_alerts=3' > ... >> GET /api/v2/measurements/2060427/status-check?permitted_total_alerts=3 HTTP/1.1 >> Host: atlas.ripe.net >> User-Agent: curl/7.52.1 >> Accept: */* >> > > < HTTP/1.1 500 Internal Server Error > < Server: nginx/1.10.2 > < Date: Sat, 14 Oct 2017 07:09:10 GMT > < Content-Type: text/html; charset=utf-8 > < Content-Length: 38403 > < Connection: keep-alive > < Vary: Accept-Encoding, Cookie > < X-Frame-Options: SAMEORIGIN > < Strict-Transport-Security: max-age=15768000 > >
- Previous message (by thread): [atlas] Problem in status checks?
- Next message (by thread): [atlas] New on RIPE Labs: Insights from RIPE Atlas Probe Disconnections
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]