Domotz 장애 기록

1. 2026년 8월 20일 오후 7:03 UTCinvestigating

   이 문제를 조사하고 있습니다.

2. 2026년 8월 20일 오후 8:44 UTCinvestigating

   우리는 현재이 문제를 조사하고 있습니다.

3. 2026년 8월 20일 오후 9:23 UTCmonitoring

   수정이 구현되어 결과를 모니터링하고 있습니다.

4. 2026년 8월 20일 오후 10:08 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 30일 오후 4:13 UTCinvestigating

   우리는 현재이 문제를 조사하고 있습니다.

2. 2026년 7월 30일 오후 5:25 UTCidentified

   문제는 식별되고 수정이 구현됩니다.

3. 2026년 7월 30일 오후 7:50 UTCidentified

   구현, 모니터링.

4. 2026년 7월 30일 오후 7:51 UTCmonitoring

   수정이 구현되어 결과를 모니터링하고 있습니다.

5. 2026년 7월 30일 오후 8:42 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 15일 오후 10:38 UTCinvestigating

   Domotz Web App 로그인 페이지에 영향을 미치는 문제의 인식입니다. 일부 사용자는 로그인 양식을로드 할 수 없습니다. 우리의 팀은 현재 뿌리 원인을 조사하고 있습니다. 더 많은 정보를 사용할 수 있도록 업데이트를 제공합니다.

2. 2026년 7월 15일 오후 11:41 UTCidentified

   이 문제는 일부 브라우저 세션에서 스크립트 오류를 일으키는 제 3 자 서비스 (Amplitude)에 추적되었습니다. Domotz 백엔드 및 인프라는 완전히 운영됩니다. 수정이 준비되고 곧 구출됩니다. 우리는 불편을 끼쳐 드려요.

3. 2026년 7월 16일 오전 5:00 UTCmonitoring

   수정이 구현되어 결과를 모니터링하고 있습니다.

4. 2026년 7월 16일 오전 11:26 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 5월 12일 오후 10:26 UTCinvestigating

   We are currently investigating this issue.

2. 2026년 5월 13일 오전 8:28 UTCidentified

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

3. 2026년 5월 13일 오전 8:57 UTCmonitoring

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

4. 2026년 5월 13일 오후 12:04 UTCresolved

   This incident has been resolved.

1. 2026년 4월 23일 오후 1:28 UTCinvestigating

   We are currently investigating this issue.

2. 2026년 4월 23일 오후 2:00 UTCinvestigating

   We are continuing to investigate this issue.

3. 2026년 4월 23일 오후 2:01 UTCidentified

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

4. 2026년 4월 23일 오후 3:15 UTCmonitoring

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

5. 2026년 4월 23일 오후 4:32 UTCresolved

   This incident has been resolved.

1. 2026년 4월 13일 오후 1:57 UTCinvestigating

   We are currently investigating this issue.

2. 2026년 4월 13일 오후 2:07 UTCidentified

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

3. 2026년 4월 13일 오후 3:10 UTCmonitoring

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

4. 2026년 4월 13일 오후 5:08 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 2026년 4월 13일 오후 5:08 UTCresolved

   This incident has been resolved.

1. 2026년 2월 11일 오후 5:09 UTCinvestigating

   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.

2. 2026년 2월 11일 오후 5:48 UTCmonitoring

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

3. 2026년 2월 11일 오후 6:51 UTCresolved

   This incident has been resolved.

1. 2026년 1월 8일 오후 6:44 UTCinvestigating

   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.

2. 2026년 1월 8일 오후 7:52 UTCmonitoring

   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.

3. 2026년 1월 8일 오후 8:24 UTCresolved

   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.

1. 2025년 12월 3일 오후 5:15 UTCinvestigating

   We are currently investigating this issue.

2. 2025년 12월 3일 오후 5:38 UTCmonitoring

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

3. 2025년 12월 3일 오후 5:42 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 2025년 12월 3일 오후 6:29 UTCresolved

   This incident has been resolved.

1. 2025년 11월 10일 오후 9:46 UTCresolved

   Login service in North America was briefly degraded and has now been restored and is currently being monitored.

1. 2025년 8월 21일 오전 8:28 UTCinvestigating

   We are currently investigating this issue.

2. 2025년 8월 21일 오전 8:32 UTCidentified

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

3. 2025년 8월 21일 오전 8:39 UTCmonitoring

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

4. 2025년 8월 21일 오전 9:17 UTCresolved

   This incident has been resolved.

1. 2025년 7월 22일 오후 4:00 UTCidentified

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

2. 2025년 7월 22일 오후 4:36 UTCmonitoring

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

3. 2025년 7월 22일 오후 5:53 UTCresolved

   This incident has been resolved.

1. 2025년 7월 1일 오후 10:55 UTCinvestigating

   We are currently investigating this issue.

2. 2025년 7월 1일 오후 11:54 UTCmonitoring

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

3. 2025년 7월 2일 오전 12:26 UTCresolved

   This incident has been resolved.

1. 2025년 6월 30일 오후 5:03 UTCinvestigating

   We are currently investigating this issue.

2. 2025년 6월 30일 오후 5:09 UTCidentified

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

3. 2025년 6월 30일 오후 5:10 UTCmonitoring

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

4. 2025년 6월 30일 오후 6:14 UTCresolved

   This incident has been resolved.

1. 2025년 6월 23일 오후 8:51 UTCinvestigating

   We are currently investigating this issue.

2. 2025년 6월 23일 오후 8:52 UTCinvestigating

   We are continuing to investigate this issue.

3. 2025년 6월 23일 오후 9:15 UTCmonitoring

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

4. 2025년 6월 23일 오후 9:28 UTCresolved

   This incident has been resolved.

1. 2025년 5월 28일 오전 8:39 UTCinvestigating

   We are currently investigating this issue.

2. 2025년 5월 28일 오전 9:20 UTCinvestigating

   We are continuing to investigate this issue.

3. 2025년 5월 28일 오전 9:21 UTCidentified

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

4. 2025년 5월 28일 오전 9:24 UTCmonitoring

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

5. 2025년 5월 28일 오전 10:03 UTCresolved

   This incident has been resolved.

1. 2025년 5월 21일 오전 8:19 UTCinvestigating

   We are currently investigating this issue.

2. 2025년 5월 21일 오전 8:23 UTCidentified

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

3. 2025년 5월 21일 오전 8:24 UTCmonitoring

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

4. 2025년 5월 21일 오전 8:42 UTCresolved

   This incident has been resolved.

1. 2025년 5월 19일 오후 1:19 UTCinvestigating

   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.

2. 2025년 5월 19일 오후 1:45 UTCidentified

   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.

3. 2025년 5월 19일 오후 1:56 UTCmonitoring

   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.

4. 2025년 5월 19일 오후 4:04 UTCresolved

   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.

1. 2025년 4월 22일 오후 8:19 UTCidentified

   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.

2. 2025년 4월 22일 오후 9:02 UTCmonitoring

   The issue has been identified and a fix is in place. We are now monitoring the situation.

3. 2025년 4월 22일 오후 9:51 UTCresolved

   This incident has been resolved.

1. 2025년 4월 10일 오후 8:59 UTCidentified

   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.

2. 2025년 4월 10일 오후 9:16 UTCmonitoring

   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.

3. 2025년 4월 10일 오후 11:02 UTCresolved

   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.