The issue identified it as a problem in AWS US-West servers. Our team is actively monitoring the situation.