@Tmadel It looks like this is not yet fixed because it just happened to one of our users :(

www.000webhost.com