360Dialog - История уведомлений

Все системы работают

Работает

API WhatsApp Business 360dialog - Работает

Настройка номера WhatsApp Business API - Работает

Клиентский центр 360dialog - Работает

Партнерский центр 360dialog - Работает

Партнерский API - Работает

Partner Webhooks - Работает

Автоматизация маркетинга - Работает

Платежная система 360 - Работает

Песочница 360dialog - Работает

360Диалог - Работает

Работает

Облачный API WhatsApp (доставка сообщений) - Работает

WhatsApp Business Account Management (Meta Business Manager) - Работает

Встроенная регистрация - Работает

История уведомлений

Посмотреть текущий статус

мая 2026

Some disruptions to waba-v2.360dialog.io
РешеноПроизводительность снижена18 минут
  • постмортемUTC

    Root Cause Analysis – Messaging API Service Disruption

    Date: 14 May 2026

    Duration: 43 minutes

    Service Affected: Messaging API (waba-v2.360dialog.io)

    Summary
    On 14 May 2026 between 13:26 and 14:09 UTC, the Messaging API experienced a service disruption lasting approximately 43 minutes. During this window, customers may have experienced timeouts or errors when sending messages or making API calls to waba-v2.360dialog.io. Service was fully restored at 14:09 UTC.

    Outbound webhooks were not lost during the disruption. They were queued and delivered with a delay once service was restored.

    Timeline (UTC)
    13:26 – Service disruption begins.
    14:09 – Service fully restored.

    Root Cause
    An infrastructure update did not behave as expected under production load. The new configuration was unable to sustain the volume of customer traffic, which led to the temporary disruption.

    Resolution
    Once the issue was confirmed, our engineering team applied a mitigation that restored the previous configuration. The Messaging API recovered immediately after the mitigation was in place, and we have continued to monitor the platform closely since the incident.

    Preventive Measures
    To reduce the likelihood and impact of similar incidents in the future, we are strengthening our infrastructure change process. This includes expanded validation prior to production rollout, more granular runtime monitoring on critical components, and a more gradual approach to applying production traffic changes.

    We apologize for the disruption and any impact this may have had on your operations. We take the reliability of our platform seriously and are committed to learning from this incident.

  • РешеноUTC

    The issue is now resolved.

  • ИзучаетсяUTC

    We are aware of an issue that is impacting our waba-v2.360dialog.io endpoint. Our engineering team is currently investigating it. We'll update again as soon as we have more information.

МАЙ13
System Maintenance - 13 May 2026, 05:00 UTC
ЗавершеноТехническое обслуживание8 часов 13 минут
  • Завершеномая 13, 2026 в 13:13UTC
    Maintenance has completed successfully.
  • В ходе выполнениямая 13, 2026 в 5:00UTC
    Сейчас идет техническое обслуживание
  • Запланированомая 13, 2026 в 5:00UTC

    On Wednesday, May 13, 2026, starting at 05:00 UTC (07:00 CEST), we will be performing scheduled network infrastructure upgrades to improve our platform's reliability. The maintenance window will last approximately 30 minutes. During this time, traffic will be rerouted to our upgraded gateway, and you may experience brief, intermittent connection errors (HTTP 404) lasting up to 80 seconds when accessing the following endpoint:

    • waba-v2.360dialog.io

    All service hostnames and URLs will remain the same, and no action is required on your part. Inbound message webhooks may also be delayed for a short time as Meta retries delivery. If errors continue after the end time, please contact support.

    We appreciate your patience as we complete these upgrades.

Some disruptions to number onboarding — 360dialog Direct clients (partner ID: srMmqpPA)
Решено4 часа 21 минута
  • РешеноUTC
    This incident has been resolved.
  • ИзучаетсяUTC

    We are aware of an issue that is impacting our number onboarding for 360Dialog Direct clients. Number onboarding has been temporarily disabled while our engineering team works on a fix. We'll update again as soon as we have more information.

апр. 2026

Disruption to the Client and Partner Hub
РешеноПолная недоступность8 минут
  • РешеноUTC
    This incident has been resolved.
  • ИзучаетсяUTC

    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.

АПР16
System Maintenance - 16 April 2026, 05:00 UTC
ЗавершеноТехническое обслуживание20 минут
  • Завершеноапреля 16, 2026 в 5:20UTC
    Техническое обслуживание успешно завершено
  • В ходе выполненияапреля 16, 2026 в 5:00UTC
    Сейчас идет техническое обслуживание
  • Запланированоапреля 16, 2026 в 5:00UTC

    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
РешеноПроизводительность снижена5 часов 37 минут
  • РешеноUTC

    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.

  • ОпределеноUTC

    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.

  • ИзучаетсяUTC

    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
РешеноПроизводительность снижена26 часов 54 минуты
  • РешеноUTC
    This incident has been resolved.
  • ОпределеноUTC

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

    We will update again soon.

  • ОбновлениеUTC

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

  • ОбновлениеUTC

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

  • ОбновлениеUTC

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


  • ОбновлениеUTC

    We are awaiting updates from Meta investigation.

  • ОбновлениеUTC

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

  • ИзучаетсяUTC

    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.

мар. 2026

Templates API Partial Service Disruption
Решено
  • ОбновлениеUTC

  • РешеноUTC

    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.

Назад

мар. 2026 до мая 2026

Следующая