SmartBobby.6283:

Heyho,

I just wanna inform you, that the API is returning an 502 error.
Is there a possibility to get a downtime history, like i.e. BitBucket (http://status.bitbucket.org/history) is providing it? It should contain a list of all affected endpoints.

It seems not everything is down. The /v2/wvw/matches endpoint is affected, but the /v2/currencies endpoint works alright.

Thank you.

Lawton Campbell.8517:

The downtime history is an interesting idea; might be beneficial to set that up.

Everything looks up from here though, and there hasn’t been a deploy in ~20 hours. Usually when there’s a hotfix parts (most) of the API goes down as the backend servers patch and restart, but since there hasn’t been one recently I’m not sure why you’d be seeing this now.

SmartBobby.6283:

I’m experiencing this problem both on my server in Frankfurt a.M. (Germany) and at home in Berlin (Germany) as well. :/

My last cronjob with an 200 code was at Jan 28 19:20:01 CET. Since a minute afterwards (19:21:01 CET) the WvW API server endpoint respond with an 502 code.

SmartBobby.6283:

I’m not sure, what u did, but since Jan 28 21:14:01 CET it’s working again.

Lawton Campbell.8517:

I’m able to successfully request from the Frankfurt datacenter, but I’m seeing errors in the logs, so something’s afoot. Looking into it some more.

EDIT: Looks to have been caused by some internal service restarts; not sure why it took so long to come back up though.

SmartBobby.6283:

I’m able to successfully request from the Frankfurt datacenter, but I’m seeing errors in the logs, so something’s afoot. Looking into it some more.

Sounds good, that you’re seeing something and thank you.