53 incidentes de Domotz registrados desde diciembre de 2023, con actualizaciones oficiales, componentes afectados, duración y detalles de resolución.
Seguimos investigando esta cuestión.
Actualmente estamos investigando esta cuestión.
Se ha aplicado una solución y estamos monitoreando los resultados.
Este incidente ha sido resuelto.
Traducido automáticamente desde la actualización oficial del incidente.
Actualmente estamos investigando esta cuestión.
Se ha determinado la cuestión y se está aplicando una solución.
Corregir implementado, monitorización.
Se ha aplicado una solución y estamos monitoreando los resultados.
Este incidente ha sido resuelto.
Traducido automáticamente desde la actualización oficial del incidente.
Somos conscientes de un problema que afecta a la página de inicio de sesión de Domotz Web App, donde algunos usuarios pueden no poder cargar el formulario de inicio de sesión. Nuestro equipo está investigando la causa raíz. Proporcionaremos una actualización tan pronto como esté disponible más información.
El problema se ha rastreado a un servicio de terceros (Amplitud) causando un error de script en algunas sesiones del navegador. El backend de Domotz y la infraestructura son totalmente operacionales. Se está preparando una solución y se extenderá en breve. Nos disculpamos por la molestia.
Se ha aplicado una solución y estamos monitoreando los resultados.
Este incidente ha sido resuelto.
Traducido automáticamente desde la actualización oficial del incidente.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently experiencing intermittent slowdowns affecting services hosted on the US cell. Some users may notice degraded performance or increased response times. Our team is actively investigating the root cause and working to restore full performance. We will provide updates as more information becomes available.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating reports of connectivity issues affecting Domotz collectors located in the United States. Our initial findings indicate that a regional DNS resolution issue is preventing some devices from connecting to the Domotz Cloud. Our engineering team is actively working to mitigate the impact. We will provide further updates as soon as more information becomes available.
We are currently tracking an issue where some Domotz Agents are appearing as “Offline” or failing to send heartbeats. Our internal logs indicate DNS resolution failures (ENOTFOUND) when Agents attempt to reach our North American API endpoints. This behavior appears to be related to an ongoing service disruption affecting Cloudflare DNS, as reported on their status page: https://www.cloudflarestatus.com/ We are actively monitoring the situation and will provide further updates as soon as service stability is restored.
The issue impacting some Domotz Collectors appearing as “Offline” or failing to send heartbeats has now been resolved. Cloudflare has completed their remediation of the DNS service disruption, and our monitoring confirms that DNS resolution and connectivity to our Cloud API endpoints have fully recovered.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
Login service in North America was briefly degraded and has now been restored and is currently being monitored.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We’re currently experiencing login issues in our US data center, which may prevent users from accessing the application or signing into their accounts. Users in the EU and APAC regions might also see delays or be unable to log in. Our team is actively investigating the root cause and will share updates as soon as we have more information. We apologize for the inconvenience and appreciate your patience. Thank you for your understanding.
We have successfully identified the root cause of the issue and our development team is currently in the process of deploying a comprehensive solution. We anticipate that the fix will be implemented shortly and appreciate your continued patience as we work to fully resolve the matter.
We have deployed a corrective update and are closely monitoring its performance to ensure that the issue is fully resolved. Thank you for your patience as we validate the results and maintain system stability.
Following a comprehensive investigation, we have fully resolved the incident. The root cause was traced to a lag in our RDBMS, which in turn caused unpredictable performance issues across several system components. Our engineering team has rectified the replication delay, restored normal functionality, and conducted thorough validation checks. We will continue to monitor system performance closely to ensure sustained stability and prevent any recurrence.
We are currently experiencing delays in processing events from Collectors and Devices. Our team is actively working on a fix to resolve the issue as quickly as possible. We appreciate your patience and will provide further updates as soon as they are available.
The issue has been identified and a fix is in place. We are now monitoring the situation.
This incident has been resolved.
We're currently experiencing performance issues on the platform. Users may encounter slow loading times when accessing the Collector device list in the UI, as well as delays in processing historical data related to device status and metrics collection. Some integration scripts may also appear as "disabled." Our team has identified the root cause and is actively working on a fix. We're closely monitoring the situation and will share updates as progress is made.
A remediation has been applied, leading to a notable improvement in both App and WebApp performance. Our engineering team is actively monitoring system behavior and continues to address residual issues related to metrics retrieval—specifically historical data access via Custom Scripts and SNMP polling. We appreciate your patience as we work toward full resolution and will provide further technical updates as developments occur.
This incident has been resolved. The reported slowness has been identified and eliminated, and Custom Scripts have been re-enabled on the affected devices. We thank you for your patience during this time.
