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

Marketing Automation - Operational

360dialog Payments System - Operational

360dialog Sandbox - Operational

Operational

WhatsApp On-Premise API (Message Delivery) - Operational

WhatsApp Cloud API (Message Delivery) - Operational

WhatsApp Business Account Management (Meta Business Manager) - Operational

Embedded Signup - Operational

Notice history

Dec 2024

Meta incident - WhatsApp and Facebook not responding
  • Resolved
    Resolved

    According to Meta, they have successfully recovered from the earlier outage impacting Cloud API, and all services have now been fully restored. If you encounter any further issues, please feel free to reach out to our support team.

    You can find more details on META status page.

  • Update
    Update

    We’re still waiting for updates regarding the incident reported. You can find more details on META status page.

  • Update
    Update

    We identified that the embedded signup and Whatsapp flows have some disruptions too.

  • Identified
    Identified

    We confirm that Meta identified the problem, and they are already working on it.

  • Investigating
    Investigating

    We have noticed some disruptions to Facebook and WhatsApp. We are monitoring the situation closely and waiting on Meta.

    We´re still verifying if it has any impacts on WhatsApp API.

    Please refer to Meta Status Page and subscribe for updates.

Some disruptions to incoming messages
  • Resolved
    Resolved

    We are aware of an issue impacting incoming messages. Our engineering team has already fixed it, and we´re monitoring it.

Nov 2024

Meta incident - Template message delivery
  • Resolved
    Resolved

    We have received an update from the Meta's engineering team that the issue has been resolved.
    If you have any further questions or encounter any issues in the meantime, please don’t hesitate to reach out.

  • Update
    Update

    We are closely monitoring the situation and awaiting further updates from Meta. At this time, Meta has not provided an estimated timeframe for restoring all functionality.

  • Update
    Update

    We are continuing to monitor the situation closely and waiting on Meta. Meta do not currently have an ETA for restoration of all functionality.

  • Investigating
    Investigating

    Meta Engineers are working on a known issue affecting some template messages delivery. While sending these template messages, it returns the error Generic user error . We are monitoring the situation closely and waiting on Meta.

Meta incident - Interactive Messages on Cloud API
  • Resolved
    Resolved

    The issue with Interactive Messages on Cloud API is now resolved.

  • Update
    Update

    Meta's Engineering team are still working on a fix for the disruption impacting the delivery of Interactive Messages with empty text in header or footer, to iOS devices on WhatsApp Cloud API.

    Another update will be provided as more information becomes available.

  • Update
    Update

    Meta's Engineering team are still working on a fix for the disruption impacting the delivery of Interactive Messages with empty text in header or footer, to iOS devices on WhatsApp Cloud API.

    Another update will be provided as more information becomes available.

  • Update
    Update

    Meta is still experiencing a disruption impacting the delivery of Interactive Messages with empty text in the header or footer to iOS devices on the WhatsApp Cloud API. Meta's engineering teams have identified the cause of the issue and are working on a fix. Further updates will be provided as more information becomes available.

  • Identified
    Identified

    Meta is currently experiencing a disruption affecting the delivery of Interactive Messages with empty text in the header or footer to iOS devices on the WhatsApp Cloud API. Meta's engineering teams have identified the cause of the issue and are working on a fix. Further updates will be provided as more information becomes available.

    Thanks for your Patience!

  • Investigating
    Investigating

    Meta is currently experiencing some disruption impacting the delivery of Interactive Messages with empty text in header or footer, to iOS devices on WhatsApp Cloud API. This issue started at September 1st, 2024. Meta engineering teams are investigating the issue.

    We are monitoring the situation closely and waiting on Meta.

    Please refer to Meta's Status Page and subscribe for updates.

Oct 2024

Some disruptions to Embedded Signup
  • Resolved
    Resolved

    Meta has resolved the issue, and the Embedded Signup feature is now fully restored. We will continue to monitor the system to ensure stability and are available for any further assistance if needed.

  • Monitoring
    Monitoring

    Meta resolved the issue and expects the Embedded Signup to be fully restored within a couple of hours. We are monitoring this and we’ll provide updates as soon as we have more details.

  • Identified
    Identified

    Meta identified the issue and updated their status page as well: https://metastatus.com/whatsapp-business-api

    They are working on resolving this issue. We’ll provide updates as soon as we have more details.

  • Update
    Update

    Our team is still working with Meta Support Team to resolve the Embedded Signup issue, which currently prevents new number registrations. We’ll provide updates as soon as we have more details.

  • Update
    Update

    Our team is still working with Meta Support Team to resolve the Embedded Signup issue, which currently prevents new number registrations. Meta is actively investigating, and we’ll provide updates as soon as we have more details. Thank you for your patience.

  • Update
    Update

    Meta's Support team is aware of the issue and is investigating it. At this time, new numbers cannot be registered via the Embedded Signup flow. We will provide another update as soon as possible.

  • Investigating
    Investigating

    We are aware of an issue affecting number registration through Embedded Signup. Users may encounter a white screen after completing OTP verification. This issue has been escalated to Meta Direct Support. While we do not have an estimated time for resolution at this time, we will provide updates as soon as possible.

Some disruptions to hosting type change
  • Resolved
    Resolved

    The issue is now resolved.

  • Update
    Update

    We are currently in the testing phase of our latest deployment, focusing on ensuring that the OTP verification status is correctly handled for the affected channels during on-premise to cloud API migrations. Once testing is complete and we successfully deploy the changes in the hub, we will provide you with an update.
    Thank you for your continued patience as we work to resolve this incident. If you have any questions, please reach out to our support team if you have any immediate concerns.

  • Update
    Update

    We are still working on releasing the product update in response to recent changes from Meta.

    For any concerns, please reach out to our customer support team. We appreciate your patience and we will keep you updated as more information becomes available.

  • Update
    Update

    Please note that, as previously mentioned, we are preparing a product update in response to recent changes from Meta, scheduled for release on Monday, October 21, 2024. Our engineering team is focused on implementing a solution.

    For any concerns, please reach out to our customer support team. We appreciate your patience and we will keep you updated as more information becomes available.

  • Update
    Update

    We have prepared a product change in response to the changes on the Meta side. We plan to release these changes on Monday 21.10.2024. In the meantime, in case of any issues, please contact our customer support.

  • Update
    Update

    We are still actively working with our engineering team to find a solution for the recent changes related to OTP verification during on-premise to cloud API migrations. We will provide new updates as soon as we have more details.

  • Update
    Update

    We are continuing to work closely with our engineering team to address the recent changes affecting OTP verification during on-premise to cloud API migrations.

    We appreciate your patience and understanding during this time. We will provide new updates as soon as we have more details to share. Please continue to check our status page for the latest information regarding this issue.

  • Update
    Update

    We are still actively working with our engineering team to find a solution for the recent changes related to OTP verification during on-premise to cloud API migrations. We will provide new updates as soon as we have more details.

  • Update
    Update

    We´re still working on a way to better handle this new change on our side.

  • Update
    Update

    Meta has identified and resolved a security issue on their side. This update, which was implemented without public announcement, has affected on-premise to cloud API migrations, requiring OTP (One-Time Password) verification.

    We are currently working on implementing a solution within our product allowing OTP verification to be handled seamlessly during migrations. This will ensure that the transition process continues without disruption.

    We will regularly post updates on our status page regarding this issue.

  • Identified
    Identified

    We are currently experiencing issues related to recent changes implemented by Meta, specifically affecting hosting type changes from On-premise to Cloud API. This issue has been escalated to Meta Direct Support. Standard migrations from other BSPs to 360dialog are not affected.

    We will regularly post updates on our status page regarding this issue.

Some templates could not be submitted
  • Resolved
    Resolved

    The issue is now resolved.

  • Update
    Update

    The engineering team is still working on the issue.

    We'll provide further updates as soon as possible.

  • Update
    Update

    We’re still working on the fix. Our engineering team is continuing to make progress on resolving the issue. We will provide further updates as soon as we have more information.

    Thank you for your patience.

  • Update
    Update

    We´re still working on the fix.

  • Update
    Update

    We are continuing to work on this problem.

    We expect to release the fix on 10.10.2024 during the day.

  • Update
    Update

    We are continuing to work on this problem.

    We expect to release the fix on 10.10.2024 during the day.

  • Update
    Update

    The engineering team is still working on the issue and making progress toward a fix. We'll provide further updates as soon as possible.

  • Identified
    Identified

    The development team has identified the issue and they´re working on a fix.

  • Investigating
    Investigating

    We are aware of an issue that is impacting our template creation process.

    360dialog API returns the following response in this case:

    "developer_message":"Template could not be submitted. Error. ","http_code":400,"success":false

    We observed that these errors usually appear for templates that use non Latin characters – like templates with Cyrillic or Arabic letters. One of the potential ways to solve this is to shorten the text in the template or remove one or two cards from carousel template.

    Our engineering team is currently investigating it.

    We do not currently have a resolution ETA but we'll update again as soon as possible.

Some disruptions to media template creation
  • Resolved
    Resolved

    The issue has been mitigated.

  • Investigating
    Investigating

    We are aware of an issue that is impacting media template creation. Our engineering team is currently investigating it. We'll provide an update as soon as possible.

Oct 2024 to Dec 2024

Next