Latitude 장애 기록

1. 2026년 10월 9일 오후 12:50 UTCinvestigating

   우리의 네트워크 팀은 SAO 지역에 영향을 미치는 연결 문제의 인식과 적극적인 투자입니다. 추가 업데이트는 더 많은 정보가 사용되기 때문에 곧 제공됩니다.

2. 2026년 10월 9일 오후 1:39 UTCmonitoring

   수정이 적용되고 네트워크 연결이 완전히 복원되었습니다. 우리의 팀은 현재 진행된 안정성을 지키기 위하여 소통량을 감시하고 있습니다.

3. 2026년 10월 9일 오후 4:45 UTCresolved

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

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

1. 2026년 9월 10일 오후 10:03 UTCinvestigating

   우리의 상 파울로 위치에 영향을 미치는 네트워크 문제, 오늘 확인 21 : 00 UTC. 우리의 네트워크 가동 팀은 적극적으로 문제점을 투자하고 완전히 정상적인 상태를 복구하기 위하여 일하고 있습니다.

2. 2026년 9월 10일 오후 10:13 UTCinvestigating

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

3. 2026년 9월 10일 오후 11:37 UTCmonitoring

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

4. 2026년 9월 11일 오전 12:03 UTCresolved

   링크 degradation는 우리의 공급자의 한으로 확인되었습니다. 분쟁 측정으로, 데이터 센터의 트래픽은 대체 링크를 통해 다시 시작되었습니다. 지속적인 감시 후에, 연결은 안정되고 성과는 정상에 돌려보내집니다.

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

1. 2026년 8월 8일 오전 12:17 UTCinvestigating

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

2. 2026년 8월 8일 오전 12:29 UTCinvestigating

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

3. 2026년 8월 8일 오전 3:05 UTCidentified

   일부 장치는 복구됩니다. 우리 팀은 여전히 DCO를 사용하여 사이트를 완전히 복구합니다.

4. 2026년 8월 8일 오전 11:06 UTCidentified

   여러 서버가 복구되었지만 사이트의 전체 확장은 여전히 순간에 일하고 있습니다. 우리의 팀은 아직도 가득 차있는 해결책을 위한 DCO로 일하고 있습니다.

5. 2026년 8월 8일 오후 11:54 UTCresolved

   이 사건은 해결되었습니다. 우리의 팀은 지속적인 표를 통해 영향을받는 고객을 위한 커뮤니케이션을 지킬 것입니다.

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

1. 2026년 6월 26일 오후 10:09 UTCinvestigating

   We are currently investigating this issue.

2. 2026년 6월 26일 오후 11:09 UTCmonitoring

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

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

   We experienced an issue on one of our border routers in New York. The router did not fail completely, however some services were impacted, which required a reboot to fully restore normal operation. During this time, our redundant infrastructure ensured that only part of the traffic was affected. Traffic is now fully stable, we are monitoring the health status closely and will share a full update once our investigation is complete.

1. 2026년 6월 25일 오전 9:16 UTCinvestigating

   We are currently investigating this issue and will provide more details as soon as they are available.

2. 2026년 6월 25일 오전 11:40 UTCmonitoring

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

3. 2026년 6월 25일 오후 9:25 UTCresolved

   This incident has been resolved.

1. 2026년 6월 23일 오후 10:23 UTCinvestigating

   We are currently investigating an outage in Miami HQ. Is it impacting all of our services, Dashboard and API.

2. 2026년 6월 23일 오후 10:41 UTCinvestigating

   We have a preliminary diagnosis that the incident was caused by a power outage affecting all the customers on the same floor. We are pushing the DC operator for an update. Is it impacting all of our services, Dashboard and API.

3. 2026년 6월 24일 오전 12:35 UTCmonitoring

   Services have been restored following a power outage. We are currently monitoring the environment closely and awaiting final confirmation from the data center team. Further updates to follow.

4. 2026년 6월 24일 오전 9:29 UTCresolved

   This incident has been resolved. We will follow up with a post-mortem as soon as a complete RCA is finished between Latitude.sh and our DCO.

1. 2026년 6월 19일 오후 5:58 UTCinvestigating

   We are currently investigating this issue.

2. 2026년 6월 19일 오후 6:24 UTCmonitoring

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

3. 2026년 6월 19일 오후 6:36 UTCresolved

   This incident has been resolved.

1. 2026년 6월 18일 오후 9:43 UTCinvestigating

   We are currently investigating this issue.

2. 2026년 6월 19일 오전 12:30 UTCresolved

   This incident has been resolved.

1. 2026년 5월 22일 오후 8:12 UTCresolved

   Between 14:00 BRT and 14:10 BRT (17:00 UTC — 17:10 UTC) on May 22, 2026, a subset of customers experienced intermittent 5xx errors on the Dashboard and API. The issue was identified, mitigated, and services are fully operational. We apologize for the inconvenience. If you continue to experience issues, please reach out to our support team.

1. 2026년 5월 7일 오후 6:11 UTCinvestigating

   We are aware and currently investigating an ongoing outage at Silicon Valley DC. We apologize for any inconvenience and will provide updates as more information becomes available.

2. 2026년 5월 7일 오후 6:25 UTCmonitoring

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

3. 2026년 5월 7일 오후 7:18 UTCresolved

   The issue has already been resolved, and services have been fully restored. We're currently investigating the case together with the Colocation Provider, and we will provide a post-mortem report as soon as possible.

1. 2026년 3월 25일 오후 4:40 UTCinvestigating

   We are currently investigating this issue.

2. 2026년 3월 25일 오후 7:14 UTCmonitoring

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

3. 2026년 3월 25일 오후 7:27 UTCresolved

   This incident has been resolved.

1. 2026년 3월 18일 오후 7:03 UTCidentified

   We are resolving an increased error rate affecting provisioning actions and virtual machines. It was related to a connection issue with internal services and should be solved within the next 30 minutes. This issue only affects new provisioning action requests. We are truly sorry about the inconvenience.

2. 2026년 3월 18일 오후 7:45 UTCmonitoring

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

3. 2026년 3월 18일 오후 8:35 UTCresolved

   This incident has been resolved.

1. 2026년 3월 17일 오후 2:23 UTCinvestigating

   We are investigating an increased error rate affecting provisinings. This issue only affects new provisinings requests. We are working to address this issue as soon as possible and will provide updates as we learn more and implement the necessary fixes

2. 2026년 3월 17일 오후 2:51 UTCinvestigating

   We are currently investigating this issue.

3. 2026년 3월 17일 오후 4:47 UTCmonitoring

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

4. 2026년 3월 17일 오후 6:07 UTCresolved

   This incident has been resolved.

1. 2026년 3월 11일 오후 4:21 UTCinvestigating

   We are currently investigating this issue.

2. 2026년 3월 11일 오후 4:44 UTCidentified

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

3. 2026년 3월 11일 오후 7:32 UTCresolved

   This incident has been resolved.

1. 2026년 3월 4일 오후 6:05 UTCinvestigating

   We are investigating an increased error rate affecting deployments and a problem with Dallas connectivity We are working to address this issue as soon as possible and will provide updates as we learn more and implement the necessary fixes.

2. 2026년 3월 4일 오후 6:06 UTCinvestigating

   We are continuing to investigate this issue.

3. 2026년 3월 4일 오후 6:25 UTCmonitoring

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

4. 2026년 3월 4일 오후 7:47 UTCresolved

   This incident has been resolved.

1. 2026년 2월 16일 오후 3:07 UTCidentified

   We are currently experiencing a connectivity issue affecting the dark fiber provider links between our SAO and SAO2 sites. This circuit is responsible for carrying several extended VLANs between the locations, resulting in some devices appearing unavailable. The provider is working on resolving the issue. At the moment, no ETA has been provided. We will continue to monitor and provide updates as soon as new information becomes available.

2. 2026년 2월 16일 오후 4:00 UTCidentified

   An ETR has been provided by the dark fiber provider. They are currently working on the issue, and the ETR is 7:00 PM (UTC). The fiber cut was caused by an incident during public road renovation works, which resulted in a major outage affecting several other fiber providers in the region. We will continue to monitor the situation and provide updates as soon as new information becomes available.

3. 2026년 2월 16일 오후 9:49 UTCresolved

   The fiber cut was restored by the provider at 7:15 PM (UTC). We have been monitoring the link since then and have not observed any new incidents.

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

   We are currently experiencing intermittent issues with server deployments in US regions. The issue affects Ubuntu 24.04, Ubuntu 22.04, and Debian 12 base images, where user data may not be applied correctly during provisioning. Our team is actively investigating and working on a fix. We will provide updates as the situation progresses.

2. 2026년 2월 11일 오후 2:53 UTCidentified

   We are continuing to work on a fix for this issue.

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

   The fix has been applied, and we are monitoring the situation.

4. 2026년 2월 11일 오후 7:53 UTCresolved

   This incident has been resolved. All services are operating normally, and the system is stable. Monitoring remains in place to ensure continued reliability.

1. 2026년 2월 5일 오전 11:35 UTCinvestigating

   We are investigating an increased error rate affecting deployments with Ubuntu 24.04. This issue only affects new deployments and reinstallations of existing servers. During the incident, if possible, prefer deploying any other OS over Ubuntu 24.04. We are working to address this issue as soon as possible and will provide updates as we learn more and implement the necessary fixes.

2. 2026년 2월 5일 오후 12:23 UTCidentified

   We have identified the root cause of the issue as an instability on Canonical’s side affecting Ubuntu 24.04 images. This problem impacts new deployments and reinstallations only. Existing servers already running Ubuntu 24.04 are not affected. Our team is monitoring the situation and working on restoring normal deployment operations for Ubuntu 24.04 across the affected regions. As a temporary workaround, we recommend deploying an alternative OS until the issue is fully resolved. Further updates will be shared as more information becomes available.

3. 2026년 2월 5일 오후 5:03 UTCidentified

   The issue affecting Ubuntu 24.04 deployments has been resolved in the majority of regions. At this time, deployment issues persist only in the ASH (Ashburn) and CHI (Chicago) regions. All other regions are operating normally. Our team continues to work on a fix to fully restore Ubuntu 24.04 deployments in the remaining affected regions. Further updates will be provided as progress is made.

4. 2026년 2월 5일 오후 6:19 UTCidentified

   We are continuing to work on a fix for this issue.

5. 2026년 2월 5일 오후 6:22 UTCmonitoring

   This incident has been resolved. The issue affecting Ubuntu 24.04 deployments has been fully mitigated, and all regions are now operating normally. Deployments and reinstallations are functioning as expected across all locations. Thank you for your patience.

6. 2026년 2월 5일 오후 11:55 UTCresolved

   This incident has been resolved.

1. 2025년 12월 21일 오후 2:35 UTCinvestigating

   We are currently investigating an issue affecting IPMI access in our London (LON) location. Some users may experience failures when establishing VPN sessions required for IPMI connectivity. Our Network Enginnering team is actively working to identify the root cause and apply the necessary configuration changes. Impact: - IPMI access in London may be unavailable or fail to establish - No impact to customer data or running workloads has been identified We will provide further updates as soon as more information is available.

2. 2025년 12월 21일 오후 8:41 UTCresolved

   This incident has been resolved.

1. 2025년 12월 15일 오후 2:57 UTCinvestigating

   We are investigating an increased error rate affecting the bandwidth usage page. We are working to address this issue as soon as possible and will provide updates as we learn more and implement the necessary fixes.

2. 2025년 12월 15일 오후 3:14 UTCmonitoring

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

3. 2025년 12월 15일 오후 5:57 UTCresolved

   The issue affecting the bandwidth usage page has been resolved. The fix has been successfully applied, and monitoring confirms that services are operating normally. We appreciate your patience and apologize for any inconvenience caused.