Yep, same errors here - 502 and 504. What happened back in March to fix it? Did you just have to wait for it to fix itself?
