Incidents reported on status page for Delogue https://es.deloguestatus.com/ https://d1lppblt9t2x15.cloudfront.net/logos/4f80fa6f283b90b55eebb904bac83bfa.png https://es.deloguestatus.com/ en https://es.deloguestatus.com/incident/824670 Fri, 13 Feb 2026 13:11:00 -0000 https://es.deloguestatus.com/incident/824670#7d103f89df623e5e9d280d2f8f44ebd00fb6289ca7487bc8529d87a918fecb7e 14:11 - Authentication & Platform Availability Disruption On February 12–13, Delogue experienced a significant service disruption that prevented users from logging into the platform and temporarily impacted availability. What Happened During scheduled infrastructure maintenance intended to improve performance and stability, an issue occurred while rolling back a change. An incorrect configuration was introduced into one isolated platform instance during the rollback process. Although the instance was brought back online shortly thereafter, the configuration error impacted the authentication layer, preventing successful user logins. As login attempts accumulated overnight, the application entered an unstable state that ultimately exhausted system resources and caused a broader outage. Once the underlying configuration issue was identified and corrected, we cleared affected login sessions and fully restored platform stability. Current Status The platform has been fully restored and is operating normally. Users are able to log in and work as expected. Our Responsibility While the incident originated during a maintenance rollback, ensuring safe deployment and recovery processes is our responsibility. We take this event very seriously. Reliability and uninterrupted access to Delogue are critical to your daily operations, and any disruption is unacceptable to us. Corrective Actions To prevent recurrence, we are implementing the following measures: • Strict Automation Enforcement All rollback and recovery procedures will now require automated deployment safeguards, eliminating the risk of configuration inconsistencies. • Improved Session Resilience We are strengthening the authentication layer so that corrupted or invalid session data cannot impact system availability. • Additional Monitoring & Guardrails Enhanced alerting and protection mechanisms will ensure similar issues are detected and contained immediately 12:20 - The site is now up and running. We advise you to clear your browser caches and login in to the platform again. 12:02 - We are writing to provide a further update on this morning's service issues. Our investigation has revealed that the resolution will require a more significant effort than initially anticipated.  Our engineering team is fully committed to this, and we are doing everything in our power to solve the issue. 10:43 – We are unfortunately still experiencing issues this morning, and the platform remains unavailable. Our team is actively investigating and working to resolve the problem as quickly as possible. We understand the impact this has on your work and sincerely apologise for the continued disruption. We will provide another update as soon as we have more information. 09:44 – Unfortunately, all servers are down this morning. The underlying issues have been fixed, and the servers are now being restarted. We expect to be live in 15 minutes. https://es.deloguestatus.com/incident/824353 Thu, 12 Feb 2026 21:24:04 -0000 https://es.deloguestatus.com/incident/824353#1c9c6e22a746905530ceaa4e3cdda4e7c9e38c9fbf802833ecc73406f68e194f es.delogue.com recovered. https://es.deloguestatus.com/incident/824353 Thu, 12 Feb 2026 20:36:07 -0000 https://es.deloguestatus.com/incident/824353#bcb20c8609ca028c8d2932a7998a8a2edf7fb395d91e5e9a60caf6d472a0aeae es.delogue.com went down. https://es.deloguestatus.com/incident/824353 Thu, 12 Feb 2026 20:08:32 -0000 https://es.deloguestatus.com/incident/824353#a92acef0b85e6b1606d4588a06e5bc11b0f4dc2fc8cb424bb0470ab952c4003b es.delogue.com recovered. https://es.deloguestatus.com/incident/824353 Thu, 12 Feb 2026 20:04:38 -0000 https://es.deloguestatus.com/incident/824353#f637c301a2136a0dbfa90e31721e6fb15624fdc4a059283a0854a27fe9fcb838 es.delogue.com went down. https://es.deloguestatus.com/incident/819192 Thu, 05 Feb 2026 12:34:33 -0000 https://es.deloguestatus.com/incident/819192#146f9892412938b1ccf6f6f1129967bf1dc8e23ce31148b4371b6f881739d9df es.delogue.com recovered. https://es.deloguestatus.com/incident/819192 Thu, 05 Feb 2026 12:20:59 -0000 https://es.deloguestatus.com/incident/819192#72e7282f7a96a91f9da42113e43bec0a20b7dc75318e61a7f242787022e75178 es.delogue.com went down. https://es.deloguestatus.com/incident/804223 Wed, 14 Jan 2026 15:20:00 -0000 https://es.deloguestatus.com/incident/804223#165543bf3fdecf813a130686724c3011a93d1d338acba3e736f668ef5a0fd451 The issue has been mitigated for now, and we’re sorry for any disruption this may have caused. We’re taking this opportunity to strengthen the system and improve its resilience going forward. https://es.deloguestatus.com/incident/804223 Wed, 14 Jan 2026 10:22:00 -0000 https://es.deloguestatus.com/incident/804223#a94ec498305ee499a4abc0ef96df5db786ef91f10e30629b0b10ec8eb7079a0e We’re currently seeing periods of higher-than-normal system activity, which may cause slower performance for some users. Our team is actively monitoring the situation and responding to any incidents as they occur to keep the service running smoothly. At the same time, we’re investigating the underlying cause of these resource spikes so we can prevent them from happening again. We’ll share further updates as we learn more. https://es.deloguestatus.com/incident/800197 Wed, 07 Jan 2026 20:02:00 -0000 https://es.deloguestatus.com/incident/800197#b685f9cff386a4b4e2469e3ff942e2f8f2a8e33d541aa8209bffa275a733e9d4 Data has been recovered. Our support team will reach out directly to you if there was any data that needs manual review. This issue has been resolved. https://es.deloguestatus.com/incident/800197 Wed, 07 Jan 2026 18:11:00 -0000 https://es.deloguestatus.com/incident/800197#5ace830747480b0a1d4d095bed3b0aaaae8424b50de8481fa0953cb3e662edc9 A fix for this issue has been released and future updates on the style header will not clear custom field values of the "allowed values" data type. We are proceeding to recover the affected data, updates will be posted here when completed. https://es.deloguestatus.com/incident/800197 Wed, 07 Jan 2026 15:30:00 -0000 https://es.deloguestatus.com/incident/800197#bb408a266a5fd18c083f4692c3ae4c5f0b1b836a0cd60d402f029ef9bed17cf8 We are providing an update on a priority incident affecting certain organizations. ### Affected Users Organizations who have configured custom fields to be visible in the Style Header. For these users, custom fields of the "allowed values" data type were cleared for some styles after updates performed on the style header. ### What Happened A recent change to the custom field logic caused incompatibility with configurations using allowed values, which resulted in the data being cleared for affected styles. ### Current Status The underlying issue has been fixed. The fix will be released today. ### Planned Actions (UTC) - The fix will be released at 17:00 UTC. - Immediately after the release, we will begin restoring the affected data. - Any styles that cannot be fully restored automatically will be identified and our support team will reach out on these cases. We will provide a follow-up update once the release and data restoration have been completed. Thank you for your patience while we resolve this. https://es.deloguestatus.com/incident/790680 Mon, 22 Dec 2025 06:29:00 -0000 https://es.deloguestatus.com/incident/790680#9c642d9aa2fdec699147b59bee8a4073c0e1307dbe3e16faf95ac0d6ca26907d Email links to styles - Issue resolved The fix has been successfully deployed and tested. Style links now work correctly for all supplier and Designer users. Previously, accessing a direct style link would cause the page to reset to the first style in the list. This has been resolved and email links now display the intended style as expected. If you experience any issues, please contact our support team. Thank you for your patience. https://es.deloguestatus.com/incident/790680 Mon, 22 Dec 2025 06:29:00 -0000 https://es.deloguestatus.com/incident/790680#9c642d9aa2fdec699147b59bee8a4073c0e1307dbe3e16faf95ac0d6ca26907d Email links to styles - Issue resolved The fix has been successfully deployed and tested. Style links now work correctly for all supplier and Designer users. Previously, accessing a direct style link would cause the page to reset to the first style in the list. This has been resolved and email links now display the intended style as expected. If you experience any issues, please contact our support team. Thank you for your patience. https://es.deloguestatus.com/incident/790680 Fri, 19 Dec 2025 14:27:00 -0000 https://es.deloguestatus.com/incident/790680#d8811d5394e5b46369200d8d412ea41b23d398bc34e6f54cad33f32fb459ca88 Fix is ready and scheduled for release Monday morning, Dec 22nd. https://es.deloguestatus.com/incident/790680 Fri, 19 Dec 2025 08:13:00 -0000 https://es.deloguestatus.com/incident/790680#4af192c35974cc5a04dada99c77d2a63e3ef42f5912243747c286446ba897ff3 We're investigating an issue with email links to styles. All supplier users are affected, as well Designer users who have disabled the "Recent" style filter. We're actively working to resolve this and will share another update shortly. Update: We've identified the root cause. When accessing a direct style link or refreshing while on a style page, the page loads correctly but then automatically resets to display the first style in the list instead of the intended one. This affects: - All supplier users - Designer users with the "Recent" filter disabled Our team is working on a fix. We'll share an update here when resolved.