Closed AlexThurston closed 10 months ago
Thanks @AlexThurston. We should be able to resolve this shortly.
We're churning through a backlog of tasks from last week at the moment, but this issue is resolved.
It looks like DEMO is giving 503 again for the health route. It seems like this becomes an issue each time there is maintenance. Could it be that it's related to that in some what since I think there was some maintenance over the weekend.
Hi @AlexThurston - there was an unexpected issue with the TQP that occurred over the weekend. We discovered and resolved it upon logging in this morning. It is currently working through the backlog and should be caught up shortly. That being said, appreciate you highlighting the /health endpoint 503 error.
No worries. Thanks for the prompt response.
environment Demo
Endpoint in which the error is experienced
https://demo.acvts.nist.gov/health
GETExpected behaviour The route would return a 200 with the information
Additional context Right now it seems to be returned a 503 with some of the information in the JSON:
The
serverVersion
key is there, but not thestatus