503 Service Unavailable while SMS auth but email works fine

Do someone experience the same issue with 503 error while SMS enter via passwordless?

We utilize hosted page and Auth0 Lock SDK on both ios/android and each time enter SMS code - this error cause notification.

No commits were made to the backend to cause any changes.
Email authentication works fine at the same time! No errors.

{
  "date": "2018-01-22T09:48:35.605Z",
  "type": "f",
  "description": "The login returned an unknown error. Status: 503Body: <html><body><h1>503 Service Unavailable</h1>\nNo server is available to handle this request.\n</body></html>\n",
  "connection": "sms",
  "connection_id": "con_rwfCCq44FpDUYkLH",
  "client_id": "vUy05HVi.....OWEitpqV",
  "client_name": "....property.com",
  "ip": "52.50.221.223",
  "user_agent": "Ruby/2.1.5",
  "details": {
    "body": {
      "client_id": "vUy05HVi.......3OWEitpqV",
      "username": "+....719665",
      "password": "*****",
      "scope": "openid",
      "connection": "sms",
      "grant_type": "password"
    },
    "qs": {},
    "connection": "sms",
    "error": {
      "message": "The login returned an unknown error. Status: 503Body: <html><body><h1>503 Service Unavailable</h1>\nNo server is available to handle this request.\n</body></html>\n",
      "oauthError": "The login returned an unknown error. Status: 503Body: <html><body><h1>503 Service Unavailable</h1>\nNo server is available to handle this request.\n</body></html>\n",
      "type": "access_denied"
    },
    "stats": {
      "loginsCount": 9
    }
  },
  "hostname": "mobile.eu.auth0.com",
  "user_id": "sms|59faf12........d943d",
  "user_name": "+35797719665",
  "strategy": "sms",
  "strategy_type": "passwordless",
  "auth0_client": {
    "name": "ruby-auth0",
    "version": "4.1.0"
  },
  "log_id": "90020180122094835606753257103149892541238823857516707890"
}

Dear @jmangelo - as I see through tickets history same took place in 2016 and 2017

The error is caused by one of your rules. In both your rules, after calling an external API, you have:

  return callback(new Error('The login returned an unknown error. Status: ' + response.statusCode + 'Body: ' + body));

This will cause the error that you’re seeing in the logs. Please check if these external APIs are returning a proper response.