504 Gateway Time-out error on post request for ping measurements

RIPE Atlas
,
1

Hello everyone,

I am running ping measurements using a fixed number of 50 probes.
The problem is quite simple: after starting 5 to 6 measurements I get a 504 Gateway time-out error.
I was wondering if anyone experienced this behaviour or if anything has changed in the past days (months?) as I have been running these measurements for quite some time without any problem.
Just in case, all my measurements are tagged as “dioptra” (here are a few ids of some successful runs: [78879509, 78879504, 78879503]).
I also checked the reference API as I thought some rate limiting was occurring but I found out that the status code for it is 429.

Thanks in advance for your help, let me know if some more information are necessary!

Edit: I put a timeout of 60 seconds in the POST request.

  • Hugo
2

Hi,

We are currently experiencing some issues both on the backend as well as the frontend causing either 502’s or 504’s.

We’re working to get it fixed but it’s likely that it will be a bit spotty for a bit longer.

Cheers,
Johan

2 Likes
3

Hey,

Thanks for the quick update. Good luck with that I guess!

Cheers,

Hugo.