360Dialog - Historial de avisos

Todos los sistemas funcionan con normalidad

Operativo

API de WhatsApp Business de 360dialog - Operativo

Configuración del número de la API empresarial de WhatsApp - Operativo

Centro de clientes de 360dialog - Operativo

Centro de socios de 360dialog - Operativo

API de socios - Operativo

Partner Webhooks - Operativo

Automatización de marketing - Operativo

Sistema de Pagos 360 - Operativo

Zona de pruebas de 360dialog - Operativo

Diálogo 360 - Operativo

Operativo

API de nube de WhatsApp (entrega de mensajes) - Operativo

WhatsApp Business Account Management (Meta Business Manager) - Operativo

Registro integrado - Operativo

Historial de avisos

Ver estado actual

ago 2025

Meta Issue - Templates not always duplicated during migration
ResueltoRendimiento degradado401 horas 22 minutos
  • ResueltoUTC

    Template duplication is now working as expected in most cases, so we are closing this incident notice.

    Template Migration Limitations

    • Templates can only be migrated between WABAs owned by the same Meta business.

    • Only templates with a status of APPROVED and a quality_score of either GREEN or UNKNOWN are eligible for migration.

    Meta is still experiencing intermittent API issues, which can sometimes cause template duplication to fail. In such cases, please contact our support team and we will escalate the case to Meta, who will run a script to complete the duplication process

  • IdentificadoUTC

    We are aware of a Meta issue affecting template duplication during phone number migration. In some cases, templates with a status of APPROVED and a quality_score of GREEN are not copied from the source to the destination WhatsApp Business Account. This issue can affect any ecosystem participant (BSP, Tech Provider, ISV, Business, etc.) that performs phone number migrations.

    Meta has confirmed this is a known issue on their side, though it is not yet reflected on their public status page.

    If your templates are not duplicated during migration, please contact our support team. We will raise a request with Meta Direct Support, and their Engineering team will duplicate the templates with priority.

    As a precaution, Meta recommends duplicating templates to the destination WABA before starting the migration. Once templates are copied, proceed with the phone number migration.

jul 2025

Algunas interrupciones en ((insertar servicio o componente))
ResueltoRendimiento degradado1 hora 2 minutos
  • ResueltoUTC

    El problema ya está resuelto.

  • IdentificadoUTC

    Seguimos trabajando en este problema y tenemos una posible mitigación para restaurar la mayor parte de la funcionalidad que se está probando.

  • InvestigandoUTC

    Somos conscientes de un problema que está afectando a nuestro {{insertar servicio o componente}}. Nuestro equipo de ingeniería lo está investigando actualmente. Actualmente no tenemos una ETA de resolución, pero la actualizaremos nuevamente lo antes posible.

JUL22
Scheduled Maintenance – July 22, 2025, 05:00 UTC
CompletadoMantenimiento1 hora
  • Completadojulio 22, 2025 a 06:00UTC
    El mantenimiento se ha completado con éxito
  • En cursojulio 22, 2025 a 05:00UTC
    El mantenimiento está ahora en progreso
  • Planificadojulio 22, 2025 a 05:00UTC

    A scheduled maintenance window has been planned for July 22, 2025, starting at 05:00 UTC, with an estimated duration of 1 hour.

    During this time, the following services may be temporarily impacted:

    • Number Webhook Management

    • New Number Onboarding

    • External events webhook

    • Measurement UI

    This maintenance is part of our continued commitment to ensuring the reliability, stability, and performance of our systems.

    Please note:

    • Webhook configuration and updates may be delayed or temporarily unavailable.

    • Onboarding of new numbers may experience temporary delays.

    • Measurement of external events in Insights API may be temporarily unavailable.

    We will provide real-time updates throughout the maintenance period.
    Normal operations will resume promptly upon completion of the work.

    We appreciate your understanding and cooperation.

jun 2025

Metaincidente informado:
ResueltoRendimiento degradado57 minutos
  • ResueltoUTC

    Meta rolled back the unintended early enablement of Per Message Pricing (PMP).

    Due to Meta's charging mechanism, some messages sent during the incident may still be charged under PMP and businesses may receive related webhooks over the next few days.

  • InvestigandoUTC

    Meta….

    Consulte la página de estado de Meta para obtener más información y actualizaciones.

Algunas interrupciones en ((insertar servicio o componente))
Resuelto11 minutos
  • ResueltoUTC

    El problema ya está resuelto.

  • InvestigandoUTC

    Somos conscientes de un problema que está afectando a nuestro {{insertar servicio o componente}}. Nuestro equipo de ingeniería lo está investigando actualmente. Actualmente no tenemos una ETA de resolución, pero la actualizaremos nuevamente lo antes posible.

Metaincidente informado:
ResueltoRendimiento degradado40 horas 57 minutos
  • ResueltoUTC

    El problema ya está resuelto.

  • ActualizarUTC

    Meta has deployed a fix and the issue is now resolved. We are currently monitoring and validating with affected users. The issue will be marked as resolved once confirmations are received.

  • SupervisandoUTC

    Meta’s engineering team has confirmed that the fix has been deployed. We are currently validating its effectiveness with affected clients. We will share further updates as soon as we confirm that the issue has been fully resolved.

  • ActualizarUTC

    We are still awaiting the Meta engineering team to deploy the fix they have prepared. We will keep you informed with any updates as soon as they become available.

  • ActualizarUTC

    We are currently waiting for Meta to release the fix they have prepared. We will announce it as soon as it becomes available.

  • IdentificadoUTC

    Estamos monitoreando de cerca la situación y esperando actualizaciones de Meta.
    Consulte la página de estado Meta y suscríbase para recibir actualizaciones.

  • ActualizarUTC

    We're still waiting for feedback from Meta engineers, who are actively investigating the issue together with our team.

    At this time, there’s no new information available.

    We’ll keep you informed as soon as any relevant information becomes available.

  • InvestigandoUTC

    Meta engineers are continuing to investigate the issue.

    We’ll keep you informed as soon as more information becomes available.

  • ActualizarUTC

    We're still awaiting feedback from Meta engineers, who are actively investigating the issue together with our team.

    At this time, there’s no new information available, but the investigation is ongoing. We’ll keep you informed as soon as any relevant information becomes available.

  • IdentificadoUTC

    We're still awaiting feedback from Meta engineers, who are actively investigating the issue together with our team.

    At this time, there’s no new information available, but the investigation is ongoing. We’ll keep you informed as soon as any relevant information becomes available.

  • ActualizarUTC

    We are currently awaiting an update from Meta engineers as they continue investigating the issue.

    We’ll keep you informed as soon as more information becomes available.

  • ActualizarUTC

    Estamos monitoreando de cerca la situación y esperando actualizaciones de Meta.
    Consulte la página de estado Meta y suscríbase para recibir actualizaciones.

  • InvestigandoUTC

    Meta….

    Consulte la página de estado de Meta para obtener más información y actualizaciones.

Metaincidente informado:
Resuelto2 horas 24 minutos
  • ResueltoUTC

    Cloudflare has confirmed that the issue has been fully resolved. The 360dialog website is now functioning normally, and no further impact is expected. We appreciate your patience during this incident.

    Further details about the incident can be found on Cloudflare’s status page

  • SupervisandoUTC

    The 360dialog website is now accessible, and services appear to be functioning normally. However, Cloudflare has not yet confirmed that the underlying issue is fully resolved. We will continue to monitor the situation closely and provide updates as soon as we receive official confirmation from Cloudflare.

  • ActualizarUTC

    The Cloudflare engineering team has identified the issue and has started working on a fix to reestablish the services.

    We will provide more updates as information becomes available.

  • IdentificadoUTC

    The Cloudflare engineering team has identified the issue and has started working on a fix to reestablish the services.

    We will provide more updates as information becomes available.

  • InvestigandoUTC

    Meta….

    Consulte la página de estado de Meta para obtener más información y actualizaciones.

Anterior

jun 2025 a ago 2025

Siguiente