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

View current status

Apr 2026

Disruption to the Client and Partner Hub
ResolvedMajor outage8 minutes
  • ResolvedUTC
    This incident has been resolved.
  • InvestigatingUTC

    We are aware of an issue that is impacting our Client and Partner Hub. Our engineering team is currently investigating it.

    We'll update again as soon as we have more information.

APR16
System Maintenance - 16 April 2026, 05:00 UTC
CompletedMaintenance20 minutes
  • CompletedApril 16, 2026 at 5:20 AMUTC
    Maintenance has completed successfully
  • In progressApril 16, 2026 at 5:00 AMUTC
    Maintenance is now in progress
  • PlannedApril 16, 2026 at 5:00 AMUTC

    We are performing upgrades to internal platform components. No service disruption is expected. Any messages that are not delivered during the maintenance window will be automatically retried by WhatsApp’s backoff mechanism and delivered once maintenance is complete.

Meta incident - High disruptions impacting Embedded Signup
ResolvedDegraded performance5 hours 37 minutes
  • ResolvedUTC

    The issue is now resolved as we have received the following update from Meta:

    Meta has recovered from an earlier outage impacting Embedded Signup, and services have now been restored. We apologize for any inconvenience that this may have caused.

  • IdentifiedUTC

    We are closely monitoring the situation and awaiting updates from Meta regarding the deployment of the fix.
    Please refer to Meta Status Page and subscribe for updates.

  • InvestigatingUTC

    Meta have reported an issue that is causing high disruptions impacting Embedded Signup

    Meta engineering teams have identified the root cause of the high disruptions impacting Embedded Signup. Meta Engineers are currently deploying the fix, and we will provide another update soon.

    Please refer to Meta Status Page and subscribe for updates.

Meta incident - Webhook registration failing for newly created numbers
ResolvedDegraded performance26 hours 54 minutes
  • ResolvedUTC
    This incident has been resolved.
  • IdentifiedUTC

    We have found the potential root cause on Meta side and are waiting on Meta engineers to confirm.

    We will update again soon.

  • UpdateUTC

    We are closely monitoring the situation and awaiting updates from Meta.

  • UpdateUTC

    We are closely monitoring the situation and awaiting updates from Meta.

  • UpdateUTC

    We are closely monitoring the situation and awaiting updates from Meta.


  • UpdateUTC

    We are awaiting updates from Meta investigation.

  • UpdateUTC

    We are closely monitoring the situation and awaiting updates from Meta.

  • InvestigatingUTC

    We are recieving an unknown error from Meta while registering the webhook URL for newly created numbers.

    We are monitoring the situation closely and waiting on Meta.

Mar 2026

Templates API Partial Service Disruption
Resolved
  • UpdateUTC

  • ResolvedUTC

    Root Cause Analysis – Templates API Partial Service Disruption
    Date: 09 March 2026
    Duration: ~1 hour
    Affected Service: Templates API (Partners API)

    Summary


    On 09 March 2026, a configuration inconsistency introduced during a routine production release caused a partial disruption of the Templates API. As a result, some template-related API requests were not processed correctly for approximately one hour.
    The issue was identified through internal monitoring alerts and resolved shortly after detection.

    Timeline (UTC)


    07:20 – Production release deployed.
    08:20 – Internal monitoring alert triggered indicating abnormal behavior.
    08:20 – Investigation started.
    08:34 – Root cause identified and configuration corrected. Fix deployed.
    08:38 – Service confirmed fully operational.

    Root Cause


    During a scheduled production release, one configuration component was not updated consistently with the rest of the deployment. This resulted in a mismatch that temporarily affected the Templates API routing.

    Resolution


    The configuration was updated to align with the production deployment settings. Once the correction was applied, the Templates API immediately resumed normal operation.

    Preventive Measures


    To reduce the risk of similar issues in the future, we are implementing the following improvements:

    • Reviewing configuration management to reduce duplicated configuration elements.

    • Adding additional validation checks during deployments.

    • Improving deployment procedures to ensure configuration consistency across all components.

    We apologize for any inconvenience this incident may have caused and appreciate your understanding.

Feb 2026

Meta incident - Meta reported disruptions impacting Onboarding and Offboarding WhatsApp "Coexistence" users
ResolvedDegraded performance1 hour 15 minutes
  • ResolvedUTC

    Meta confirmed the issue is now resolved.

    The fix for the disruptions impacting onboarding and offboarding WhatsApp "Coexistence" users has been deployed and this issue is now resolved. Thank you for your patience.

  • InvestigatingUTC

    Meta has reported an issue that is causing medium disruptions impacting Onboarding and Offboarding WhatsApp "Coexistence" users.

    Meta Engineering teams are investigating the issue.

    We will provide another update if additional information is available.

    We are monitoring the situation closely and waiting on Meta.

    Please refer to Meta Status Page and subscribe for updates.

Meta Incident - PDF Messages Not Delivering Webhooks (Feb 2025)
ResolvedDegraded performance
  • UpdateUTC
    This incident has been resolved.
  • ResolvedUTC

    Summary
    Between February 4 and February 11, 2025, Meta identified an issue affecting incoming webhook delivery for a small subset of PDF messages sent via WhatsApp Web. Certain PDFs failed to generate incoming message webhooks for Cloud API partners due to an internal change in PDF thumbnail generation, which produced thumbnails exceeding Cloud API size limits. Outgoing messages and messages sent from Android or iOS clients were not impacted.

    Impact
    A very low volume of incoming PDF messages sent via WhatsApp Web were not delivered through Cloud API webhooks. Business messaging functionality and 360dialog platform operations remained fully operational.

    Resolution
    Meta acknowledged the issue, reverted the thumbnail generation change, and deployed a fix on February 11, 2025 at 00:03 UTC, after which normal webhook delivery resumed.

    Prevention
    Meta implemented additional testing, monitoring, and platform consistency checks to prevent recurrence.

    This was a Meta incident and was not related to 360dialog systems or infrastructure.

Previous

Feb 2026 to Apr 2026

Next