All systems operational

Problems with messaging

Resolved
Major outage
Started almost 2 years ago Lasted 2 days

Affected

Meta Infrastructure
WhatsApp On-Premise API (Message Delivery)
Updates
  • Resolved
    Resolved

    Meta have advised that the issue impacting message delivery is resolved.

    If you are still experiencing a problem relating to this incident: please create a Support Ticket with us (Category: Messaging Has Completely Stopped Working) and we will assist you.

    We are awaiting RCA from Meta.

  • Monitoring
    Monitoring

    Meta have advised that the issue impacting message delivery has now been resolved and the service has been restored.

    Some WhatsApp API setups require a restart to fully restore the service. We are currently working on restarting all setups that require this action.

    If you urgently require a restart, please create a Support Ticket with us (Category: Messaging Has Completely Stopped Working) and we will prioritize the restart for you.

  • Identified
    Identified

    Meta has confirmed that the problem is rooted in the WhatsApp Business Platform. We are working closely together with them to understand how to solve it as soon as possible. We will update this incident as soon as we have more information from Meta

    You can recognize this issue if you try to perform certain operations like check contacts or send messages and you receive a response such as: errors":[{"code":1014,"title":"Internal error","details":"Connection timed out. Please check if wacore is running: x"}]} or "error": "HTTPSConnectionPool(host='x', port=443): Read timed out. (read timeout=20)"

  • Investigating
    Investigating

    We are receiving some reports that there is an issue with the messaging service (such as {"error":"HTTPSConnectionPool(host='x', port=443): Read timed out. (read timeout=20)"} We are currently investigating.