https://status.koyeb.com/cmd5ovmge005jyf0kgkt7i91z seems to have not been fixed completely. One of my services returns
204
for a particular usecase. It is an API.
The users began to report issues with me not being able to figure out what went wrong. Local test, no errors. Check server logs, no errors. But Koyeb still shows the service returned errors and thats why they are giving
502
. What? And so I made a dramatic guess and decided to test on another hosting provided. And this time I finally got
204
as I should.
So, in the end I think for some reason Koyeb is giving
502
when an API gives
204
. Maybe someone hardcoded
status != 200
not knowing that any
2xx
status code is known as success by standards, who knows. But the problem is still there and needs to be fixed.