Deliverect 장애 기록

1. 2026년 9월 26일 오후 2:07 UTCresolved

   사이 13:13 그리고 13:42 UTC 에 26 9 월, 일부 고객 경험 오류 또는 순서 처리와 지연. 우리의 팀은 13:42 UTC에 문제점과 회복된 정상적인 서비스를 확인했습니다. 우리는 사건을 검토하고 다시 일어나지 않도록 조치를 취합니다.

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

1. 2026년 9월 18일 오전 10:39 UTCresolved

   16:55 및 17:14 UTC에서 15 9 월, 일부 고객 경험 오류 또는 순서 처리와 지연. 우리의 팀은 17 : 14 UTC의 문제 및 복원 정상적인 서비스를 확인했습니다. 우리는 사건을 검토하고 다시 일어나지 않도록 조치를 취합니다.

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

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

   We are currently experiencing an issue where menu pushes are failing. Our team is aware and actively investigating the root cause. We will provide updates as more information becomes available.

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

   We are continuing to investigate this issue.

3. 2026년 4월 23일 오후 5:55 UTCidentified

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

4. 2026년 4월 23일 오후 6:03 UTCmonitoring

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

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

   This incident has been resolved.

1. 2025년 12월 5일 오전 9:09 UTCinvestigating

   We are currently investigating a major, global outage reported by our cloud provider, Cloudflare. This outage is affecting their network infrastructure, which is severely impact the availability, performance, and accessibility of some of our products and services.

2. 2025년 12월 5일 오전 9:15 UTCmonitoring

   A fix has been implemented by Cloudflare and our systems are recovering, we are monitoring closely.

3. 2025년 12월 5일 오전 9:20 UTCresolved

   The incident has been resolved and our services and products are fully operational again.

1. 2025년 11월 18일 오후 4:20 UTCresolved

   We noticed a service interruption impacting our Retail Order Processing and related front-end UIs in several regions. The root cause was identified as a major global outage affecting our critical third-party provider, Cloudflare. The incident started at roughly 1:00 PM UTC. Importantly, our restaurant order processing channels were unaffected and continued to function normally throughout this period. Our engineering teams were immediately focused on developing and implementing a service workaround. As of 2:21 PM UTC, all Retail Order Processing services and front-end UIs were fully functional and stable. We apologize for the disruption caused by this external event.

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

   We are currently experiencing a service outage due to an incident with our cloud provider. This disruption is impacting multiple systems, and our team is actively working to assess the situation and restore services as quickly as possible

2. 2025년 6월 12일 오후 6:52 UTCmonitoring

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

3. 2025년 6월 12일 오후 9:40 UTCresolved

   This incident has been resolved.

1. 2025년 3월 16일 오후 7:46 UTCinvestigating

   We are currently investigating an issue within our API that is causing delays in order processing. Our engineering team is actively working to identify the root cause and resolve the issue as quickly as possible.

2. 2025년 3월 16일 오후 8:02 UTCmonitoring

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

3. 2025년 3월 16일 오후 9:33 UTCresolved

   This incident has been resolved

4. 2025년 3월 17일 오후 2:41 UTCpostmortem

   Some of our customers experienced temporary delays in order processing due to an issue with a new feature. This feature, designed to improve how we handle old data, unintentionally created extra work for our system during a busy period. While our team resolved the issue, we understand how important it is for your operations to run smoothly. To prevent this from happening again, we’ve made several improvements, including better monitoring, stricter testing for new features, and adjustments to how our system handles errors. We sincerely apologize for any inconvenience this may have caused and thank you for your patience as we continue to make Deliverect more reliable for your business.

1. 2024년 11월 1일 오후 9:57 UTCresolved

   Deliverect experienced degraded performance between 20:08 UTC and 20:53 UTC. Most customers should not have been impacted, but a small number may have experienced dropped orders, delayed orders, or other issues with Deliverect functionalities. The issue has been resolved and we are working to prevent future occurrences.

1. 2024년 7월 18일 오후 5:20 UTCinvestigating

   We are currently investigating the issue.

2. 2024년 7월 18일 오후 5:30 UTCmonitoring

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

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

   The overall degradation in API response times has been solved. The fix we implemented has fixed the issue.

1. 2024년 4월 30일 오전 10:11 UTCresolved

   Start Time: April 30, 2024, 06:41 AM CEST (04:41 AM UTC) End Time: April 30, 2024, 06:48 AM CEST (04:48 AM UTC) We are backfilling an incident that occurred earlier this morning where the Deliverect API experienced degraded performance for a short period of time (approximatively 7 minutes). This resulted in slower response times and potential delayed order processing. Deliverect API is now functioning normally and we apologize for any inconvenience this may have caused.

1. 2024년 3월 13일 오후 7:38 UTCresolved

   Customers might have experienced delay on order processing from 18:12 to 18:36 UTC+0 The incident is now resolved and we are back to normal order processing activities.

1. 2024년 1월 19일 오전 12:23 UTCresolved

   Between 00:18 and 00:27 UTC+1, our system degraded and performance slowly declined. The incident was caused by a third-party provider experiencing issues. We sincerely apologize for the inconvenience.

1. 2023년 10월 4일 오후 5:15 UTCinvestigating

   We are currently investigating this issue.

2. 2023년 10월 4일 오후 5:42 UTCidentified

   We experienced order processing delays, but we can confirm that now all processing activities are back to normal. As a way to improve order processing performance, the menu-push feature has been paused until we have further information about its impact on the order flow.

3. 2023년 10월 4일 오후 7:11 UTCmonitoring

   We've identified the cause of the incident and applied a fix for it. We'll keep monitoring.

4. 2023년 10월 5일 오전 8:53 UTCresolved

   This incident has been resolved.

1. 2023년 8월 24일 오전 7:46 UTCinvestigating

   We are currently investigating this issue.

2. 2023년 8월 24일 오전 7:48 UTCidentified

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

3. 2023년 8월 24일 오전 8:32 UTCmonitoring

   A fix has been implemented and we are monitoring the results

4. 2023년 8월 24일 오전 8:33 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 2023년 8월 24일 오전 9:30 UTCresolved

   This incident has been resolved.

1. 2023년 8월 16일 오후 2:26 UTCinvestigating

   Our monitoring system detected a sudden traffic decrease on one of our systems, which was impacting order processing. Requests are not correctly arriving to our systems we are actively investigating and setting all efforts to quickly resolve it.

2. 2023년 8월 16일 오후 2:35 UTCinvestigating

   We are continuing to investigate this issue. The impact was that our queueing systems was struggling to process orders to the POS systems, and restarting them only partially helped recovery.

3. 2023년 8월 16일 오후 2:44 UTCidentified

   After a thorough investigation the issue has been identified and a fix is being implemented.

4. 2023년 8월 16일 오후 2:45 UTCmonitoring

   A fix has been deployed and we are monitoring the results

5. 2023년 8월 16일 오후 3:33 UTCresolved

   Operations were restored completely for affected customers. We are currently actively monitoring our systems.

1. 2023년 7월 28일 오후 12:44 UTCmonitoring

   Starting at 10:28 (UTC+0), we faced potential delays over a period of 45min. All orders were eventually processed and the incident has been addressed and fixed.

2. 2023년 7월 28일 오후 12:44 UTCmonitoring

   We are monitoring the fix that was applied, and are implementing changes to avoid this from occurring in the future.

3. 2023년 7월 28일 오후 12:45 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 2023년 7월 31일 오전 9:17 UTCresolved

   This incident has been resolved.

1. 2023년 5월 22일 오전 10:23 UTCinvestigating

   Starting May 21, 19:00 CET time we have been experiencing degraded performance with our API, which is impacting the speed and responsiveness of our frontend.

2. 2023년 5월 22일 오전 10:32 UTCidentified

   You may notice that our Frontend is slower than usual at certain times, when it's the case our API takes more time than usual to respond to requests. This can lead to some orders being rejected or duplicated. Our team is actively working on resolving the problem and restoring normal operations as quickly as possible.

3. 2023년 5월 22일 오전 10:37 UTCmonitoring

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

4. 2023년 5월 22일 오후 1:33 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 2023년 5월 23일 오전 7:54 UTCresolved

   This incident has been resolved

1. 2023년 5월 19일 오후 8:10 UTCresolved

   Customers and partners might have experienced slowness on the Deliverect Frontend and non-critical API calls between 8:00 PM CET and 9:45 PM CET. A fix has been implemented and the incident is now resolved.

1. 2023년 2월 6일 오전 9:29 UTCresolved

   An issue with a TLS certificate impacted customers using the Tunnel but did not affect customers using DMA. We experienced system instability for around 50 minutes. The issue is related to the expiry of a TLS certificate, which is normally automatically renewed by our processes. Our Infrastructure and Support teams were notified of the incident and immediately began investigating the cause. The automation responsible for renewing this specific certificate was identified as the root cause of the incident. The team worked to replace manually the expired certificate with a new one so customers can use the tunnel again without disruption. The code responsible for the certificate renewal is now being reviewed to avoid this bug from happening again.

1. 2022년 11월 7일 오후 8:00 UTCresolved

   We’ve noticed some order updates did not reach the DMA. This issue was noticed between 15:19:45 (UTC+0) and 18:40:00 (UTC+0). We’ve identified the issue and applied a fix to it. We will keep monitoring.