>>82831195
apparently the issue is fixed now, it was a DNS thing after all :P