DANAconnect Outage History

DANAconnect is up right now

DANAconnect had 10 outages in the last 2 years totaling 871h 21m of downtime — averaging 0.4 incidents per month.

There were 10 DANAconnect outages since August 28, 2024 totaling 871h 21m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.danaconnect.com

Major January 22, 2026

We are experiencing issues displaying real time reporting.

Detected by Pingoru
Jan 22, 2026, 03:01 PM UTC
Resolved
Jan 22, 2026, 05:00 PM UTC
Duration
1h 58m
Affected: Real-Time Reporting
Timeline · 4 updates
  1. investigating Jan 22, 2026, 03:01 PM UTC

    We are experiencing issues displaying real time reporting. The source of the problem is a reference to a service on w3.org. The DevOps team is working to enable the display. All events and processing are being logged.

  2. identified Jan 22, 2026, 03:03 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Jan 22, 2026, 04:19 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Jan 22, 2026, 05:00 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 2, 2025

Degradación en el envío de SMS

Detected by Pingoru
Dec 02, 2025, 03:47 PM UTC
Resolved
Dec 02, 2025, 05:45 PM UTC
Duration
1h 58m
Affected: SMS -Venezuela - Telefónica MovistarSMS - Venezuela - Digitel
Timeline · 4 updates
  1. investigating Dec 02, 2025, 03:47 PM UTC

    Estamos observando una degradación en el despacho de SMS y estamos investigando las posibles causas en coordinación con las operadoras correspondientes. Nuestro equipo continúa trabajando para normalizar el servicio. Compartiremos actualizaciones en cuanto tengamos más información

  2. identified Dec 02, 2025, 04:09 PM UTC

    Causa Identificada en el Servicio DNS Nos han indicado que la degradación en el envío de SMS está relacionada con una afectación en el servicio DNS del centro de datos utilizado por las operadoras. Nos mantenemos en monitoreo continuo del comportamiento del servicio mientras los equipos técnicos correspondientes realizan las acciones necesarias para la recuperación. Compartiremos nuevas actualizaciones cuando haya información adicional.

  3. monitoring Dec 02, 2025, 05:42 PM UTC

    La afectación relacionada con el envío de SMS ha sido solventada por las operadoras. Hemos pasado a modo de monitoreo para confirmar la estabilidad del servicio y asegurar que el desempeño se mantenga dentro de los parámetros habituales. Informaremos cualquier novedad relevante en caso de ser necesario.

  4. resolved Dec 02, 2025, 05:45 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 25, 2025

Delay in dispatching communications / Retraso en despacho de comunicaciones v

Detected by Pingoru
Nov 25, 2025, 10:55 PM UTC
Resolved
Nov 25, 2025, 11:58 PM UTC
Duration
1h 2m
Affected: Email platformDirector - Workflow OrchestrationWebhooks (API Request Node)
Timeline · 5 updates
  1. investigating Nov 25, 2025, 10:55 PM UTC

    We are experiencing delays in the delivery of outbound messages. We will provide updates as we work towards a resolution.

  2. identified Nov 25, 2025, 11:01 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Nov 25, 2025, 11:11 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. monitoring Nov 25, 2025, 11:24 PM UTC

    During a period of exceptionally high message-processing volume, the DANAconnect platform began receiving an elevated number of error logs generated by one of the internal background processes. These errors created congestion within the processing pipeline, which in turn caused delays in the dispatching of outbound messages. Our engineering team promptly investigated the issue and identified the specific massive process responsible for triggering the errors under heavy load. The process was corrected, and normal message-processing performance was restored. We continue to monitor the platform closely to ensure stable and timely message delivery. Thank you for your understanding.

  5. resolved Nov 25, 2025, 11:58 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical November 3, 2025

Crisp Services Partial service outage

Detected by Pingoru
Nov 03, 2025, 02:14 PM UTC
Resolved
Nov 03, 2025, 02:32 PM UTC
Duration
18m
Affected: Crisp Chat Support
Timeline · 3 updates
  1. investigating Nov 03, 2025, 02:14 PM UTC

    Interrupción Parcial del Servicio de Chat Crisp Estamos experimentando una interrupción parcial en el servicio de chat en vivo de Crisp. Algunos usuarios pueden tener problemas para enviar o recibir mensajes.

  2. identified Nov 03, 2025, 02:17 PM UTC

    Hemos recibido una notificación de nuestro proveedor del servicio de chat, Crisp, confirmando que están experimentando fallas serias y generalizadas en varios de sus componentes principales. Su equipo de ingeniería está trabajando activamente en la resolución. Impacto: Esta situación está afectando de manera intermitente o total el servicio de chat en vivo y la recepción de mensajes. Nuestras Acciones: Estamos monitoreando de cerca las actualizaciones de Crisp y confirmando el restablecimiento de nuestro servicio tan pronto como el incidente sea resuelto por su parte. Lamentamos profundamente las molestias causadas por esta situación fuera de nuestro control. Agradecemos su comprensión.

  3. resolved Nov 03, 2025, 02:32 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice October 20, 2025

We are experiencing intermittence in multiple services

Detected by Pingoru
Oct 20, 2025, 01:31 PM UTC
Resolved
Oct 21, 2025, 12:15 AM UTC
Duration
10h 43m
Affected: Portal US-EST1Email platformAWS cloud9-us-east-2Audit Reports & Delivery LogsSMS -Venezuela - Telefónica MovistarDocument Upload APIAWS cloudfrontDirector - Workflow OrchestrationReal-Time ReportingPortal Apps US-EST1SMS - Infobip APIDo Not Contact List APIAWS cloud9-us-east-1Webhooks (API Request Node)Landing PagesCustom ETL ProcessingSMS - Venezuela - DigitelOne Time Password APIAWS route53Web FormsAutomated Contact LoadingConversation APIAWS s3-us-east-2SMTP ServiceAWS ec2-us-east-1AWS ec2-us-east-2Bulk Contacts Load APISite DANAConnect
Timeline · 14 updates

Read the full incident report →

Critical May 9, 2025

Incidente integrador de SMS en Venezuela

Detected by Pingoru
May 09, 2025, 12:57 PM UTC
Resolved
May 09, 2025, 01:32 PM UTC
Duration
35m
Affected: SMS -Venezuela - Telefónica MovistarSMS - Venezuela - Digitel
Timeline · 3 updates
  1. investigating May 09, 2025, 12:57 PM UTC

    integrador de sms en venezuela esta presentando problemas en servidor Le saludamos respetuosamente e informamos que, nuestro Integrador de SMS en Venezuela esta presentando un incidente sobre su Data Center, debido a una falla en uno de sus enlaces principales, generando problema de conexión, situación que impacta en el despacho de los mensajes de notificación (MT) y bidireccional o interactivo (MO) que son emitidos hacia las operadoras locales en Venezuela. Nuestro integrador se encuentra en comunicación con el personal operativo de Data Center. Una vez solventada la falla estaremos informando.

  2. monitoring May 09, 2025, 01:20 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved May 09, 2025, 01:32 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 28, 2024

Retraso en despacho de comunicaciones

Detected by Pingoru
Aug 28, 2024, 02:32 PM UTC
Resolved
Aug 28, 2024, 06:30 PM UTC
Duration
3h 58m
Affected: Email platform
Timeline · 4 updates
  1. investigating Aug 28, 2024, 02:32 PM UTC

    En estos momentos se esta presentado un elevado numero de transacciones, lo cual esta generando un leve retraso en los despacho y entregas de algunos correos. Nuestro personal se encuentra trabajando sobre el caso para solventar el mismo lo mas pronto posible.

  2. identified Aug 28, 2024, 02:32 PM UTC

    Nuestro personal se encuentra trabajando sobre el caso para solventar el mismo lo mas pronto posible

  3. monitoring Aug 28, 2024, 03:35 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Aug 28, 2024, 06:30 PM UTC

    This incident has been resolved.

Read the full incident report →