I made during my free time a little tool to check the status of HITMAN servers and steam services, you can see current outages, problems of both platforms and maintenance periods for all HITMAN services. It might be useful to know if the connectivity problems come from your side or not.
Going to PM what I have to say because it could be abused.
Edit: Sent. Hopefully that’ll help make it more reliable.
Edit #2:@Travis_IOI any chance of a trivial JSON api output when you guys take the site down? I already know how to check it, I’m just curious if we could get a clean API to read off on each of the endpoints (something consistent like /status.json with caching maybe?).
Really all we need is the availability message field, or some blank/boring page throwing 200 (all good) or an appropriate error when the client can’t access it. I know it wouldn’t be an API as such, but could you please replicate that one field into a public status document (literally just returning it, and nothing else, in /status.json would do). I’m happy to get creative with analysing how it works.
As someone who has had to write public facing APIs I know there’s probably huge issues with a few things, but I’d rather not have to emulate part of the game client* to pull the status message if it could be replicated out (and in fact if it could replace the checks); I had a look at things after what happened in June/July last year (passive analysis – I actually assumed it was a sync issue with Steam cloud which had corrupted something, this is when I realised how much of the game was online), and was planning an ET tracker before the phone app landed (so I have a fair idea of a few things).
* Obviously my primary concern with doing any of that is people getting hold of it and abusing it, which is why I sent the PM to Hardware rather than discussing any of it on the public boards.
Not a problem. I like the game running (and development continuing); it’s not in my nature to break things that aren’t local (something something clients and live dev something something darkside something something complete).
Short term I’ll expose the status for @Hardware (using read-only data). It isn’t ideal, but it’ll do for now.
Azure platform is really reliable and have high-availability features, so this tool isn’t really useful most of the time if you have a good connection to internet. But many users on reddit / steam and hitmanforum.com regularly report connectivity issues with Hitman servers, most of the time this issues come from their LAN network or their ISP provider, and not because of IOI azure backend unavailability.
Do not forget, hitman backend have a strong adherence to the steam auth system, which also impacts ps4 and xbox one players when downtimes occur.
hitmanstat.us is useful to see current outages on both platform from 2 geographic locations (USA/EU), high loaded endpoints, maintenance periods and a global status reporting soon (thanks @swixel).
And maybe more if the Lead Online Programmer decides to provide us an API
So, @Hardware had the exclusivity for a while, but I deployed this week https://auth.hitman.io/status
It is a small JSON resource which returns the current status of the services (maintenance, health check, high latency)
If you are writing a service like hitmanstat.us, please use this rather than direct ping on the servers, as I ensure we minimize the calls and always serve a cached version.
Behind the scene, what the health check does is an authenticated call on all 3 servers, which allocates a proper session on the cluster, and check for the response time.
We tend to publish maintenance notices late, but when we do the expected maintenance window will be returned in the nextWindow property.
I read on another post that @Hardware might update the status page with the new call soon