Incidents reported on status page for Delogue https://www.deloguestatus.com/ https://d1lppblt9t2x15.cloudfront.net/logos/da78c5dfe5176db816ae1567e0265f47.png https://www.deloguestatus.com/ en https://www.deloguestatus.com/incident/819193 Thu, 05 Feb 2026 12:32:12 -0000 https://www.deloguestatus.com/incident/819193#11fb48d5dfb23769ced99271b571d68a7168341cd2039d2434ab5a74e9f9bbbb my.delogue.com recovered. https://www.deloguestatus.com/incident/819193 Thu, 05 Feb 2026 12:21:39 -0000 https://www.deloguestatus.com/incident/819193#f27edd5f29e5673829bacb6f3dca7ab8a14c65b79babfeba3716c947da815813 my.delogue.com went down. https://www.deloguestatus.com/incident/818673 Wed, 04 Feb 2026 20:15:10 -0000 https://www.deloguestatus.com/incident/818673#fa42f6263a62d66bcf5373cb382ff7d7d2d19bc458d10080e9618f334807d41e my.delogue.com recovered. https://www.deloguestatus.com/incident/818673 Wed, 04 Feb 2026 20:14:22 -0000 https://www.deloguestatus.com/incident/818673#06332bb5c99073a01e96bb100db0f3d0661ce72a228e041631d2f15dbc1e7b69 my.delogue.com went down. https://www.deloguestatus.com/incident/814902 Fri, 30 Jan 2026 06:27:49 -0000 https://www.deloguestatus.com/incident/814902#1c761c0b7e4de4cfca7dfdee88d74112b69fbde66cf87683b1e0b75d4655ac05 my.delogue.com recovered. https://www.deloguestatus.com/incident/814902 Fri, 30 Jan 2026 06:21:25 -0000 https://www.deloguestatus.com/incident/814902#903f9423f35d3b32ee08821efd7f06469e43b6a7f48149a860cfab04ef39cb51 my.delogue.com went down. https://www.deloguestatus.com/incident/813467 Wed, 28 Jan 2026 10:27:11 -0000 https://www.deloguestatus.com/incident/813467#e547c55013d3f130905e544c02df86f604787917238fcff168f9b9a0384825d1 my.delogue.com recovered. https://www.deloguestatus.com/incident/813467 Wed, 28 Jan 2026 10:25:14 -0000 https://www.deloguestatus.com/incident/813467#0e6038a8915e06ff3a44ccbd17410224cd06668304d09a84e8af6e6c2140c6d7 my.delogue.com went down. https://www.deloguestatus.com/incident/806368 Sat, 17 Jan 2026 17:26:08 -0000 https://www.deloguestatus.com/incident/806368#a50d38bda51d91820a5ac76068b4e9470e7afd6cd7106bc08ce733fe83edc862 my.delogue.com recovered. https://www.deloguestatus.com/incident/806368 Sat, 17 Jan 2026 17:11:38 -0000 https://www.deloguestatus.com/incident/806368#bb6de9cb3601afcdacdcead30b3ed236a28a199deb8a4547b2df84662702f77f my.delogue.com went down. https://www.deloguestatus.com/incident/804221 Wed, 14 Jan 2026 15:17:00 -0000 https://www.deloguestatus.com/incident/804221#19857c7b626869e8de5f0bfd1d592ee7d0e223ab1bc5ac4b07e055ee0e730df8 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://www.deloguestatus.com/incident/804221 Wed, 14 Jan 2026 10:18:00 -0000 https://www.deloguestatus.com/incident/804221#05aa7fdc19483eba03b2f0e0e5870215a2908bf865036582a0344a1277915167 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://www.deloguestatus.com/incident/803857 Tue, 13 Jan 2026 19:54:00 -0000 https://www.deloguestatus.com/incident/803857#8b8ce3463666b4954aa7858d36b05ffc0593f8a696c613cabdf5bf59508618d7 my.delogue.com recovered. https://www.deloguestatus.com/incident/803857 Tue, 13 Jan 2026 19:48:12 -0000 https://www.deloguestatus.com/incident/803857#16dcf74f9a0d35697c4a5f76ac7167024d135d38dfb7ab4319899e04b2309198 my.delogue.com went down. https://www.deloguestatus.com/incident/800195 Wed, 07 Jan 2026 19:39:00 -0000 https://www.deloguestatus.com/incident/800195#007b8faf507ff555ef9ec7625df03a78a23992345157f29052b89bfcaa7b4eef 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://www.deloguestatus.com/incident/800195 Wed, 07 Jan 2026 18:09:00 -0000 https://www.deloguestatus.com/incident/800195#d8219695cff55c2a106c10f6c6eedd0bde0a480d03b7e19617cc78426e790084 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://www.deloguestatus.com/incident/800195 Wed, 07 Jan 2026 15:30:00 -0000 https://www.deloguestatus.com/incident/800195#b5d2d3390f82f44ab74c8a69449857f88ed34fc6d69fb6b95b3c548047b92bd5 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://www.deloguestatus.com/incident/790679 Mon, 22 Dec 2025 06:41:00 -0000 https://www.deloguestatus.com/incident/790679#3319b6dcd01efe5734efc6b29558eedc03b5bfc96fc4dad59a3a8abc715735c8 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://www.deloguestatus.com/incident/790679 Mon, 22 Dec 2025 06:41:00 -0000 https://www.deloguestatus.com/incident/790679#3319b6dcd01efe5734efc6b29558eedc03b5bfc96fc4dad59a3a8abc715735c8 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://www.deloguestatus.com/incident/790679 Fri, 19 Dec 2025 14:26:00 -0000 https://www.deloguestatus.com/incident/790679#7be7eb7bb51feeb4e497a23985fe5581d85c1559777100305a42c566b9f35175 Fix is ready and scheduled for release Monday morning, Dec 22nd. https://www.deloguestatus.com/incident/790679 Fri, 19 Dec 2025 08:09:00 -0000 https://www.deloguestatus.com/incident/790679#428a25bace37f02bbe08dd9cda369994a70413c6464bb76bb3a712c12a4af46f 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.