360dialog - Notice history

All systems operational

Operational

360dialog WhatsApp Business API - Operational

WhatsApp Business API Number Setup - Operational

360dialog Client Hub - Operational

360dialog Partner Hub - Operational

Partner API - Operational

Partner Webhooks - Operational

Performance Messaging - Operational

360dialog Payments System - Operational

360dialog Sandbox - Operational

360dialog Support & Documentation - Operational

Operational

WhatsApp Cloud API (Message Delivery) - Operational

WhatsApp Business Account Management (Meta Business Manager) - Operational

Embedded Signup - Operational

Notice history

Apr 2025

No notices reported this month

Mar 2025

Some disruptions to Message template creation
  • Update
    UTC
    Update

    The issue is now resolved.

  • Resolved
    UTC
    Resolved

    The issue is now resolved.

  • Investigating
    UTC
    Investigating

    We are aware of an issue that is impacting the creation of message templates. Our engineering team is currently investigating it. We'll update again as soon as we have more information.

Meta incident - Marketing and authentication templates
  • Update
    UTC
    Update

    The issue has been resolved.

    To avoid the issue, please don't use the category field in the payload.

  • Resolved
    UTC
    Resolved

    The issue has been resolved.

    To avoid the issue, please don´t use the category field in the payload.

  • Update
    UTC
    Update

    We are actively monitoring the situation and awaiting further details from Meta regarding their ongoing investigation. We will provide updates as soon as more information becomes available.

  • Investigating
    UTC
    Investigating

    We are aware of an issue that impacts sending of some marketing and authentication templates.

    The error message is: 

    "(#100) Param category must be one of {SERVICE, UTILITY} - got \"AUTHENTICATION\"."


    We are monitoring the situation closely and waiting for Meta.

Meta incident - Incoming messages issue
  • Resolved
    UTC
    Resolved

    Meta has resolved the issue on their side, and the services have now been restored.

  • Update
    UTC
    Update

    We´re monitoring and waiting for further updates from Meta.

  • Monitoring
    UTC
    Monitoring

    We are monitoring and waiting for further updates from Meta.

  • Update
    UTC
    Update

    We are closely monitoring the situation and awaiting further updates from Meta on their ongoing investigation. We will share any new information as soon as it becomes available.

  • Update
    UTC
    Update

    We are closely monitoring the situation and awaiting further updates from Meta on their ongoing investigation. We will share any new information as soon as it becomes available.

  • Update
    UTC
    Update

    We are actively monitoring the situation and awaiting further details from Meta regarding their ongoing investigation. We will provide updates as soon as more information becomes available.

  • Investigating
    UTC
    Investigating

    Meta has acknowledged an issue on their side, experiencing some disruption that impacts the receipt of incoming messages on WhatsApp Cloud API. This issue started on March 5th at 8 AM GMT.

Feb 2025

Meta incident - Disruption to WhatsApp Flows
  • Resolved
    UTC
    Resolved

    Meta has recovered from an earlier outage impacting WhatsApp Flows, and services have now been restored.

  • Update
    UTC
    Update

    We are still waiting for the Meta engineering team to deploy the fix for this issue. We will provide a new update once we have any news.

  • Identified
    UTC
    Identified

    Meta have reported an issue that is causing disruptions to WhatsApp Flows.
    Meta engineering teams have identified the root cause of the disruptions and are currently deploying the fix. The expected deployment time is in 5-8 hours.
    Please refer to Meta Status Page and subscribe for updates.

Some disruptions to Messaging post migration from On-premise to Cloud API for some numbers
  • Resolved
    UTC
    Resolved

    The issue is impacting a small number of migration attempts from the On-Premise API to the Cloud API, with Meta returning an error during the migration process.

    As this affects only a limited number of requests, we are removing the incident from our status page. However, if your migration fails, please submit a support request, and our team will assist you on a case-by-case basis.

  • Update
    UTC
    Update

    We´re still working with the Meta engineering team on this issue. We´ll provide a new update once we have any news.

  • Update
    UTC
    Update

    We´re still working with the Meta engineering team on this issue. We´ll provide a new update once we have any news.

  • Update
    UTC
    Update

    We´re still working with the Meta engineering team on this issue. We´ll provide a new update once we have any news.

  • Update
    UTC
    Update

    We´re still working with the Meta engineering team on this issue. We´ll provide a new update once we have any news.

  • Investigating
    UTC
    Investigating

    We´re still working with the Meta engineering team on this issue. We´ll provide a new update once we have any news.

  • Identified
    UTC
    Identified

    We´re still working with the Meta engineering team on this issue. We´ll provide a new update once we have any news.

  • Update
    UTC
    Update

    We are continuing to work with Meta Engineering team on this problem. We'll update again as soon as possible.

  • Update
    UTC
    Update

    We are continuing to work with Meta Engineering team on this problem. We'll update again as soon as possible.

  • Update
    UTC
    Update

    We are continuing to work with Meta Engineering team on this problem. We'll update again as soon as possible.

  • Update
    UTC
    Update

    We are aware of an issue that is impacting Messaging for some numbers after migration from On-premise to Cloud API. Our engineering team is currently investigating it with Meta Engineering team. We'll update again as soon as possible.

  • Update
    UTC
    Update

    We are aware of an issue that is impacting Messaging for some numbers after migration from On-premise to Cloud API. Our engineering team is currently investigating it with Meta Engineering team. We'll update again as soon as possible.

  • Investigating
    UTC
    Investigating

    We are aware of an issue that is impacting Messaging for some numbers after migration from On-premise to Cloud API. Our engineering team is currently investigating it with Meta Engineering team. We'll update again as soon as possible.

Meta incident - business.facebook.com is partly available
  • Resolved
    UTC
    Resolved

    The issue has been resolved by Meta.

  • Update
    UTC
    Update

    We´re still monitoring the issue and waiting for an update from Meta.

  • Monitoring
    UTC
    Monitoring

    We are monitoring the situation and waiting on Meta to confirm that the issue is fixed.

  • Identified
    UTC
    Identified

    Meta have confirmed an issue with Business Manager interface at business.facebook.com.

    Meta Business Suite is impacted, especially the Business Support section.

    We are monitoring the situation and waiting on Meta engineers to fix the issue.

Some disruptions to Cloud API messaging
  • Resolved
    UTC
    Resolved

    Meta has resolved the issue: "We have recovered from an earlier outage impacting Cloud API, and services have now been restored. We apologize for any inconvenience that this may have caused."

    META also informed that messages sent during the incident will not be recovered and cannot be resent to the webhooks.

    We will also provide a Root Cause Analysis (RCA) with all the incident details as soon as possible.

  • Monitoring
    UTC
    Monitoring

    We´re still monitoring and waiting for an update from Meta.

  • Identified
    UTC
    Identified

    We have identified the cause of message delays affecting Cloud API numbers as a Meta issue and we’re awaiting their response.

    Meta have acknowledged this issue on their status page "Our engineering teams have identified the root cause of the medium disruptions impacting webhooks on WhatsApp Cloud API. We are currently deploying the fix and the expected deployment time is in 8hours. We will provide another update within 4 hours or sooner if additional information is available."

    Our engineering team is preparing a workaround to mitigate the issue for WhatsApp Business Accounts with a single number until Meta resolves the issue on their side.

  • Update
    UTC
    Update

    We are monitoring the situation closely and waiting on Meta.

  • Investigating
    UTC
    Investigating

    We are aware of an issue affecting Cloud API numbers, specifically impacting the messaging service for incoming messages.

    Our engineering team is actively investigating the root cause. We will share an update as soon as more information becomes available.

Some disruptions to Account reactivation
  • Resolved
    UTC
    Resolved

    The issue is now resolved.

  • Investigating
    UTC
    Investigating

    We're aware of an issue that may be causing reactivation of accounts after a past due payment has been submitted. Our engineering team is already working on releasing a patch to resolve this issue and prevent it from happening again.

    Incident Timeline

    • Detected: 9:00am GMT+1

    • Estimated ETA: Today

    Next Update
    We'll provide another update when the patch is released and the issue is resolved. Thank you for your patience and understanding.

    Additional Information
    If you have any questions or concerns, please don't hesitate to reach out to our support team. We appreciate your feedback and look forward to resolving this issue soon.

Feb 2025 to Apr 2025

Next