All US profile ladder endpoints return 503 error. Is this a temporary issue, as the code suggests, or something is wrong?
Example:
https://us.api.blizzard.com/sc2/profile/1/1/20782779/ladder/summary
This call returns 503 error, but their web profile Profile Summary - PartinG - StarCraft II Official Game Site correctly shows the ladder.
/sc2/profile/1/1/20782779/ladder/304452
(player’s last ladder) also returns 503 error code.
https://us.api.blizzard.com/data/sc2/season/49
returns 404
I’ve been experiencing this too!
1 Like
Now some EU endpoints return 502 error code sometimes
Affected endpoints:
/data/sc2/league/:season/:queue/:type/:league
/sc2/legacy/profile/:regionId/:realmId/:profileId/matches
/sc2/legacy/ladder/:regionId/:ladderId
Matches and ladder errors are more frequent. It’s only relevant for eu.api.blizzard.com
host, if any other host is used, like us.api.blizzard.com
, then there are no errors.
1 Like
This is incredibly frustrating, the SC2 API is still broken and there hasn’t been any acknowledgment of this 
The issues have been resolved.
Well, it didn’t last long - unfortunately, it appears it’s broken once again. Getting 503 again, since 16h ago. Didn’t fully investigate, but I assume it’s the same problem, as it’s only affecting data from US region.