Same situation with me.
I'm not sure who manages it, but @brollb probably does know.
Same.
Yesterday, (or maybe earlier today) it was working, but now it's giving the 502 again.
