Cronologia delle interruzioni di Zid

1. 25 ottobre 2026 alle ore 11:21 UTCidentified

   Ci troviamo di fronte e abbiamo identificato un parziale outage nel nostro servizio Merchant Imports & Exports e stiamo lavorando per risolverlo il prima possibile.

2. 25 ottobre 2026 alle ore 12:07 UTCresolved

   Questo incidente è stato risolto.

3. 25 ottobre 2026 alle ore 12:19 UTCpostmortem

   Traduzione: ** Esportazioni e importazioni di cartone in ritardo per tutti i negozi** | | | | --- | | **Date** | 25, 2026, 11:25 AM fino alle 2:26 PM\(UTC\+3, KSA time\). Durata: 3 ore 1 minuto | **Tipo di incidente** | Degrado di servizio: elaborazione di sfondo | | **Title** | Un'importazione di clienti molto grande bancarotta esporta e importa per tutti i negozi | | **Impact** | 132 richieste di esportazione da 66 Store sono state ritardate, in media, di 81 minuti e fino a 3 ore 43 minuti. 3 di loro hanno tempo e devono essere richiesti di nuovo. Le importazioni del cliente del negozio che ha iniziato la grande importazione sono state ritardate fino alle 15:12 PM. | ** Impatto totale sull'aggiornamento | Nessun outage. Negozi, checkout e il cruscotto ha funzionato tutto il tempo. Solo le esportazioni e le importazioni aspettavano. # # Le esportazioni di Dashboard \(ordini, clienti, portafogli, carrelli abbandonati e altri\) e le importazioni di cruscotto sono costruite sullo sfondo da un pool condiviso di lavoratori. Alle 11:23 un Merchant ha iniziato un'importazione di clienti con circa 1.05 milioni di righe. La piattaforma si divide ogni importazione in parti di 100 file, così questo è diventato 10.486 parti. Dopo ogni parte, la piattaforma controlla se l'intera importazione è finita, in modo da poter inviare al Merchant un riassunto. Quel controllo ha caricato ogni parte dell'importazione, le righe incluse, in memoria: circa 200 MB per assegno per questa importazione, con fino a cinque controlli in esecuzione subito. I lavoratori sono scappati di memoria e si riavviarono di nuovo e di nuovo. Le richieste di esportazione da ogni negozio hanno aspettato dietro le parti di importazione. Abbiamo spedito un cambiamento di livello di codice, quindi il controllo chiede solo se qualsiasi parte è ancora in sospeso e aggiunge i totali finali nel database. Non carica più le righe, quindi il suo uso di memoria non cresce più con la dimensione dell'importazione. ## Timeline \(KSA time\) | Time | Event | | --- | | 11:23 | A Merchant inizia un'importazione di circa 1.05 milioni di righe. Alle 11:27 è diviso in 10,486 parti. | | 11:25 | Viene creata la prima richiesta di esportazione che deve aspettare. Successivamente richiede la coda dietro le parti di importazione. | | ~11:34 I lavoratori cominciano a scappare dalla memoria e riavviarsi. Da qui terminano circa 5 parti di importazione per riavvio e quasi nessuna esportazione. # | 12:26 PM | A Merchant riferisce di sostenere che 3 esportazioni richieste dalle 11:30 sono ancora in fase di elaborazione. | ~1:15 PM | Product Engineering avvia l'indagine e traccia i riavviamenti al controllo di completamento dell'importazione. | 1:54 PM | Product Engineering prepara il cambiamento, con un test che riproduce la crescita della memoria. | 2:08 PM | I lavoratori iniziano a sgomberare il backlog, anche se si riavviano ancora di volta. # | 2:26 PM | L'ultima esportazione ritardata termina. Le esportazioni sono tornate alla normalità. | 2:34 PM | Il cambiamento è vivo. | | ~3:00 PM | Il lavoratore si riavvia. | | 3:09 PM | 3 richieste di esportazione che avevano aspettato più di 3 ore sono contrassegnate come timed out. | 3:10 PM | La grande importazione termina, ad eccezione di una parte di 100 righe che la piattaforma si ricarica automaticamente. # # Che cosa à ̈ stato interessato # | Area | Stato durante l'incidente | Come sappiamo | | --- | --- | Esportazioni di Dashboard, tutti i tipi e tutti i negozi | **Delayed:** 132 richieste da 66 Stores, 81 minuti in media, fino a 3 ore 43 minuti | Registrati di richiesta di esportazione. Ordini 72, ordini dettagliati 21, portafoglio 11, carrelli abbandonati 6, clienti 6, recensioni 5, preparazione ordine 4, tagliandi 3, altro 4. | Exports that timed out | **Failed:** 3 richieste da 2 Stores | Esporta record di richiesta. Questi Mercanti hanno bisogno di chiedere di nuovo l'esportazione. # | Exports still processing | **1 request** | Esporta record di richiesta. La piattaforma lo rimetta automaticamente. | | Importazioni del cliente del negozio che ha iniziato la grande importazione | **Delayed fino alle 15:12 PM:** 9 importazioni | Import records. Tutte le parti finite tranne una, che viene ritratta automaticamente. # | Importazioni da altri negozi | ** Non interessato | Nessun altro negozio ha iniziato un'importazione durante l'incidente | | Esportare il contenuto dei file | **Non interessato** | Ogni file è costruito da dati in tempo reale quando viene eseguito, quindi i file ritardati sono completi | | Negozi, checkout e cruscotto | **Non interessati | Solo i lavoratori di base per le esportazioni e le importazioni riavvicinati | ## Azione presa 1. Trovata la causa: i lavoratori che costruiscono le esportazioni e le importazioni stavano riavviando perché il controllo di completamento delle importazioni è finito di memoria. 2. Spedito un cambiamento di livello di codice: il controllo di completamento conta parti in sospeso e aggiunge i totali nel database invece di caricare ogni parte. Un test fallisce sul vecchio comportamento e passa al nuovo. 3. Confermato che le esportazioni ritardate sono finite, e ha identificato le 3 richieste timed-out in modo che il sostegno può chiedere a quei Mercanti di chiedere di nuovo loro. ## Conclusioni **L'importazione di One Merchant non dovrebbe contenere le esportazioni di ogni altro Store.** Le esportazioni e le importazioni condividono gli stessi lavoratori, quindi un'importazione pesante ritarda tutti. Il cambiamento rimuove questa causa. **Il lavoro che funziona una volta per parte non deve crescere con le dimensioni dell'intera importazione** Il controllo di completamento legge l'intera importazione dopo ogni parte. Questo è stato bene per le importazioni tipiche e non è riuscito solo per uno molto grande. Con il cambiamento, un'importazione di questa dimensione non esaurisce più la memoria dei lavoratori.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 9 ottobre 2026 alle ore 11:25 UTCinvestigating

   تجارنا الأعز الياً اضاب اباباً جيياب في بعب ددماتنا نتية مشكلة تقنية لدì اد مدودي الخدمة الخدمة الخارجينينين ان ان ان انانالي اياناماماناياماناناناياً ام اياياماً اياياً اً اياياً اً ام اً اً اً ام اً اً اً اياً اياياياياياً اً اً اً اً اً اً اياً اً اياياياراياياً اا الاميا التقني بشكل مثة وبالتنسيق المبار مع موود الخدمة المعالة الة الة المة المة المشقيامامياماماماماماميامامامامامامامامامياماماماماماماميامامياماماميامامامامامامياماماماماماماماماماماماماميامامامياماماماماماميامامامامامامياماماماماماماماماماماماماميامام عنتشر عن أي قزعاج قد يسبه هيالانقطاع، وسنوافييم بالمالمستجداتات فور توفرهام ام الامالاماماتاتاتار فور فور توراياياياياي اي اياي اي اي اي اي اي اي اي اي اي اي اي اي اي اي اي اي اي ام ام قد قد ام اي اي ام ام ام ام ام ام ام ام ام ام ام ارام ام ام ام ام ام اا شنكرم علYes ببركم وتفهمكم? Cari Mercanti, Attualmente stiamo vivendo una parziale interruzione di servizio a causa di un problema che riguarda uno dei nostri fornitori di servizi di terze parti. Il nostro team di ingegneria sta attivamente indagando e lavorando con il fornitore per ripristinare la piena disponibilità di servizio il più rapidamente possibile. Ci scusiamo per qualsiasi inconveniente e forniremo ulteriori aggiornamenti come ulteriori informazioni diventano disponibili. Grazie per la vostra pazienza e comprensione.

2. 9 ottobre 2026 alle ore 11:50 UTCresolved

   تم حل المشكلة: عادت تصاميم المتاجر إلى العمل تجارنا الأعزاء، عادت الخدمة إلى العمل، وتظهر واجهات المتاجر الآن بتصاميمها المعتادة. إن ظهر متجرك لأحد العملاء دون تنسيق، فيكفي تحديث الصفحة أو فتحها من جديد. لا يلزمك أي إجراء آخر. سنواصل متابعة الخدمة للتأكد من استقرارها. نعتذر عن الإزعاج، ونشكر لكم صبركم وتفهمكم. --- Resolved: Store designs are loading again Dear Merchants, The service is back, and storefronts are loading with their usual designs. If a shopper still sees a store without styling, refreshing the page will fix it. You don't need to do anything else. We will keep monitoring to make sure the service stays stable. We apologize for the disruption and thank you for your patience.

3. 9 ottobre 2026 alle ore 11:54 UTCpostmortem

   ملخص الحادثة: خلل في ظهور الثيمات وتخصيصها للمتاجر — ٩ أكتوبر ٢٠٢٦ ماذا حدث ظهرت بعض واجهات المتاجر يوم ٩ أكتوبر ٢٠٢٦ دون تنسيقاتها، فبدت صفحاتها نصوصاً وروابط متتابعة بلا تصميم. بدأ الخلل قرابة الساعة 1:06 ظهراً بتوقيت السعودية، وانتهى قرابة الساعة 2:48 عصراً. السبب أوقف أحد مزودي البنية التحتية خدمة التخزين التي تُحمَّل منها ملفات تصاميم المتاجر، والسبب خطأ في الفوترة والمحاسبة لدى المزوّد. لم يكن الخلل تقنياً، ولم يكن من جهة زد. الأثر • تأثر شكل واجهات المتاجر لدى العملاء طوال مدة الخلل. • لم تتأثر بيانات المتاجر ولا المنتجات ولا الطلبات، ولم يُفقد منها شيء. • ظلت صور المنتجات تعمل طوال مدة الخلل. الحل تواصلنا مع المزوّد مباشرة حتى صحّح الخطأ لديه وأعاد تفعيل الخدمة، فعادت المتاجر إلى شكلها الطبيعي دون أن يلزم التجار أي إجراء. ما سنفعله لمنع تكراره سنبني مصدراً بديلاً لملفات تصاميم المتاجر، تنتقل إليه المتاجر تلقائياً إذا تعطّل المصدر الأساسي، فلا يتوقف ظهور المتاجر بسبب مزوّد واحد. نعتذر عن الإزعاج الذي سببه هذا الخلل لكم ولعملائكم، ونشكر لكم صبركم وثقتكم. --- Incident summary: Store themes and customizations not loading — October 9, 2026 What happened On October 9, 2026, some storefronts loaded without their styling, so pages showed as plain text and links. The issue began at about 1:06 PM Saudi time and ended at about 2:48 PM. Cause One of our infrastructure providers suspended the storage service that serves store theme files because of a billing and accounting error on their side. This was not a technical failure, and it was not caused by Zid. Impact • Storefronts looked unstyled to shoppers for the duration of the incident. • Store data, products and orders were not affected, and nothing was lost. • Product images kept working throughout. Resolution We worked with the provider directly until they corrected their error and re-enabled the service. Stores returned to normal without merchants having to do anything. Preventing a repeat We will add a backup source for store theme files. If the primary source fails, stores will switch to the backup automatically, so a single provider can no longer take down how stores look. We apologize for the disruption to you and your customers, and we thank you for your patience and trust.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 13 maggio 2026 alle ore 16:14 UTCresolved

   أعزاؤنا التجار، واجهت متاجرنا مشكلة في صفحة تسجيل الدخول ابتداءً من الساعة 3:17 مساءً وحتى 3:37 مساءً بتوقيت السعودية. خلال هذه الفترة، لم يتمكن المستخدمون مؤقتًا من الوصول إلى صفحة تسجيل الدخول. لقد تم تحديد المشكلة والسيطرة عليها، وعاد النظام إلى العمل بشكل طبيعي. تبيّن أن السبب كان عملية نشر غير سليمة لتطبيق الواجهة الأمامية React، وتم التراجع عن التغيير ومعالجة المشكلة بشكل فوري. كما نعمل حاليًا على مراجعة عمليات النشر والتحقق الخاصة بالواجهة الأمامية للمساعدة في منع تكرار مثل هذه المشكلات مستقبلًا. نأسف للإزعاج، ونقدّر تفهمكم. مع خالص التحيات، Dear Merchants, Our stores experienced an issue affecting the login page from 3:17 PM to 3:37 PM KSA, during which users were temporarily unable to access the login page. The issue has been identified and resolved, and the system is now operating normally. The issue was caused by a faulty frontend React deployment. The change was promptly reverted and remediated. We are currently reviewing our frontend deployment and validation processes to help prevent similar issues from recurring. We apologize for the inconvenience and appreciate your understanding.

1. 18 febbraio 2026 alle ore 17:59 UTCidentified

   Some stores were experiencing slower than usual response times.

2. 18 febbraio 2026 alle ore 18:02 UTCmonitoring

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

3. 18 febbraio 2026 alle ore 18:03 UTCresolved

   This incident has been resolved.

4. 18 febbraio 2026 alle ore 18:25 UTCpostmortem

   The team released an incident fix for an issue where the count of products under categories was not calculated correctly, and was instead showing 0 for parent categories whose products are all placed inside child categories. As a result of this fix, there was an increase in DB queries, leading to a spike in CPU utilization of our database. This happened mainly due to cache warming jobs used in the old catalog system. While the fix was intended for the Dashboard, an inadvertent consequence happened on “Old Catalog” – not Vitrin \(stores on Vitrin were browsable safely\). During that period, some users who did not have the store cached on their end may have experienced downtime with some stores. Others experienced degraded performance only on cart actions. ‌ Action Taken: 1. We immediately reverted the troublesome deployment. 2. The congested queues for store cashing were purged to avoid having blocked jobs 3. Assembled a rapid response team to decouple this dependency and prevent such incidents in the future.

1. 18 novembre 2025 alle ore 12:27 UTCmonitoring

   Start Time: 2025-11-18 2:48 PM Impact: Some users may experience intermittent errors or inability to access parts of the Zid platform. Cloudflare has reported a global network issue and is currently investigating. As Zid’s traffic flows through Cloudflare’s network, this incident may impact accessibility for some users, depending on their region and routing. Our systems and infrastructure remain healthy, and the issue is external. We are actively monitoring Cloudflare’s updates and will provide further details as soon as they are available. أعلنت كلاودفلاير عن وجود مشكلة في شبكتها العالمية وهي حالياً في مرحلة التحقيق. ونظرًا لاعتماد منصة زد على شبكة كلاودفلاير لتوجيه حركة المرور، قد يتأثر جزء من المستخدمين حسب المنطقة ومسار الاتصال. جميع خوادمنا تعمل بشكل طبيعي، والمشكلة خارج نطاق منصة زد. نقوم بمتابعة الموقف بشكل مستمر، وسيتم نشر أي تحديثات جديدة فور توفرها من كلاودفلاير.

2. 18 novembre 2025 alle ore 18:55 UTCresolved

   This incident has been resolved.

1. 26 marzo 2025 alle ore 23:53 UTCresolved

   Dears, We experienced a brief service disruption due to a DDoS attack, which caused temporary unavailability of our stores for approximately 3 minutes. The issue was promptly identified and successfully mitigated by our security team. All systems are now operating normally. Thank you for your patience and understanding. اعزائنا التجار لقد واجهنا انقطاعًا مؤقتًا في الخدمة نتيجة لهجوم (DDoS) مما أدى إلى تعذر الوصول إلى متاجرنا لمدة تقارب 3 دقائق. وقد تم التعرف على المشكلة بسرعة والتعامل معها بنجاح من قبل فريق الأمن لدينا. جميع الأنظمة تعمل الآن بشكل طبيعي. نشكر لكم تفهمكم.

1. 18 febbraio 2025 alle ore 10:40 UTCidentified

   Our stores are currently experiencing downtime. We’re actively working on resolving the issue and will keep you updated on the progress. Thank you for your patience! 🙏

2. 18 febbraio 2025 alle ore 11:12 UTCresolved

   Our stores are back online! Our team has successfully handled the issue, and we are now in the monitoring phase to ensure everything runs smoothly.

1. 2 febbraio 2025 alle ore 20:05 UTCresolved

   أعزاؤنا التجار، واجهت متاجرنا بطئًا في عربة التسوق استمر لحوالي 20 دقيقة، مما تسبب في تأخير تأكيد بعض الطلبات . لقد تم تحديد المشكلة والسيطرة عليها، وعاد النظام إلى العمل بشكل طبيعي. نحن نواصل مراقبة الوضع لضمان استقرار المنصة. نأسف للإزعاج، ونقدّر تفهمكم. مع خالص التحيات، Dear Merchants, Our stores experienced slowness in the cart for about 20 minutes, which caused some orders to take longer to confirm. The issue has been identified and resolved, and the system is now operating normally. We continue to monitor the situation to ensure platform stability. We apologize for the inconvenience and appreciate your understanding.

1. 14 novembre 2024 alle ore 09:38 UTCidentified

   Dear Merchants, We are currently facing an issue impacting the POS and MyZid applications on both iOS and Android platforms, which may result in unexpected logouts. Our team is actively working on a resolution and will provide updates shortly. Thank you for your patience and understanding as we work to resolve this issue promptly. أعزاءنا التجار نواجه حاليًا مشكلة تؤثر على تطبيقات نقاط البيع و ماي زد، وقد تؤدي إلى تسجيل خروج غير متوقع يعمل فريقنا بنشاط على إيجاد حل وسوف يقدم تحديثات قريبًا نشكرك على صبركم وتفهمكم بينما نعمل على حل هذه المشكلة على الفور.

2. 14 novembre 2024 alle ore 09:48 UTCidentified

   Here’s the latest update: • The issue with ZIDPOS has been resolved. - Users should force close the app, and it will automatically load the new configuration. • MyZID is still under investigation. - On iOS, the update is still in progress. - For Android, the update is still in progress. آخر التحديثات: • تم حل مشكلة ZIDPOS ينبغي على المستخدمين إغلاق واعادة تشغيل التطبيق ، وسيتم تحميل الإعدادات الجديدة تلقائيًا. • مشكلة MyZID لا تزال قيد التحقق

3. 14 novembre 2024 alle ore 12:17 UTCresolved

   Dear Merchants, We are pleased to inform you that the issue impacting the POS and MyZid applications on both iOS and Android platforms, which resulted in unexpected logouts, has been resolved. السادة التجار الكرام، نود إعلامكم بأنه قد تم حل المشكلة التي أثرت على تطبيقات POS و MyZid والتي تسببت في عمليات تسجيل خروج غير متوقعة.

1. 17 ottobre 2024 alle ore 21:37 UTCresolved

   Dears, We experienced a brief disruption in our stores frontend service that lasted approximately 3 minutes due to an unexpected technical issue. The disruption affected random stores, not all. Our team immediately identified the problem, took full control, and resolved the issue swiftly. The service is now fully operational. أعزاؤنا التجار لقد واجهنا انقطاعًا قصيرًا في خدمة الواجهة الأمامية للمتاجر استمر لمدة حوالي 3 دقائق نتيجة لمشكلة تقنية غير متوقعة. تأثرت بعض المتاجر بشكل عشوائي وليس جميعها. قام فريقنا بتحديد المشكلة على الفور، وتم حل المشكلة بسرعة. الخدمة الآن تعمل بشكل كامل، ونحن نراقب لضمان استقرارها. نعتذر عن أي إزعاج قد تسبب به هذا الأمر و نقدر تفهمكم.

1. 2 ottobre 2024 alle ore 09:02 UTCresolved

   The system experienced a brief outage lasting approximately 4 minutes due to an unexpected technical issue. Our team promptly identified and resolved the problem, ensuring minimal disruption to services. We are taking steps to prevent similar occurrences in the future.

1. 23 settembre 2024 alle ore 23:36 UTCresolved

   On September 22, 2024, at around 1:42 AM KSA time (GMT+3), our stores encountered a brief outage lasting approximately one minute, caused by an unexpected technical issue that was not managed by our service provider.

1. 5 giugno 2024 alle ore 06:45 UTCresolved

   Dear Merchants, Some of our stores have encountered a brief 2 min 404 error message as a result of a current deployment we have done. All systems are now operating successfully. Thank you أعزاؤنا التجار واجهت بعض متاجرنا رسالة خطأ (404) لفترة قصيرة مدتها دقيقتين نتيجة لعملية التحديث الأخيرة التي قمنا بها جميع الأنظمة تعمل الآن بنجاح. شكرًا لك

1. 7 aprile 2024 alle ore 10:41 UTCresolved

   Partial outage for some stores from 5:24:03 on 6th April 2024 till 5:31:06 the same day. Total partial downtime 7 minutes and 3 seconds.

2. 7 aprile 2024 alle ore 10:42 UTCpostmortem

   **What happened?** We suffered from a similar issue as the day before. This issue has been a hardware issue that affected our auto-scaling \(done when traffic increases\). ‌ **How long it lasted for?** 7 minutes and 3 seconds ‌ **What have we done to ensure it does not happen again?** We have rebuild the hardware and re-build the cluster in which our gateway runs. This will ensure that there is a brand new platform supporting it.

1. 6 aprile 2024 alle ore 08:39 UTCresolved

   Some stores were not opening and showing error messages shown to their customers from 9:43:57 pm to 9:57:59 PM. The issue caused the platform to be unstable and it was related to a our gateway cluster used to secure the traffic and cache the stores to ensure faster response to end consumers.

2. 7 aprile 2024 alle ore 09:52 UTCpostmortem

   **What happened?**  A set of improvements have been undertaken on the platform in the last weeks to absorb the high volume of traffic generated by the stores associated with the campaigns period of Ramadan. A subset of these changes has been done on one of the critical components use to accelerate the speed of showing the website to end consumers. This component is called Caddy. This is used for 2 main reasons, to control unwanted traffic to the platform and filter it and also cache the stores so that people that are browsing the same store can be shown with the different pages faster \(an acceleration of around 200% compared to not using this component\).  At 9:43:57 pm on 4th April 2024 Caddy scaled up failed. This issue caused intermittently some stores to show errors to end consumers not allowing them to continue browsing and forcing them to refresh.  **How long it latest for?**  6 minutes and 2 seconds At 9:57:59 pm on 4th April 2024 all pods went back to work effectively and the issue was resolved.  **Did it affect orders?**  * Ratio of created orders in the next 15 min after the issue happened is higher by 10 or 15 orders more than average per minute \(before the issue occurring\). This suggest that all orders were not lost considering the traffic after the issue and the orders after the issue. **How are we preventing from this happening again?**  * Review proactively the Caddy configuration to ensure we don’t have bigger issues like the one reported in the future and ensure that all issues are resolved in the Caddy gateway  * We have added additional monitoring however this was a hardware failure that we continuing to investigate with hosting supplier in cloud.

1. 17 marzo 2024 alle ore 20:35 UTCresolved

   أعزاؤنا التجار واجهت متاجرنا بطء ملحوظ. تم حل المشكلة ونحن نراقب الوضع لضمان استقرار المنصة. مع خالص التحيات Dear Merchants, Our stores have experienced noticeable slowdowns. The issue has been resolved, and we are monitoring the situation to ensure the stability of the platform. Sincerely,

1. 12 marzo 2024 alle ore 18:55 UTCinvestigating

   أعزاؤنا التجار نحن نواجه حاليًا بطء في عملية الدفع عبر متاجرنا بسبب حجم كبير غير متوقع من الزيارات. يرجى الثقة بأن فريقنا يعمل بنشاط على حل هذه المشكلة في أقرب وقت ممكن. إلى جانب ذلك، يرجى ملاحظة أن منصتنا بشكل عام لا تزال تعمل بكامل طاقتها. نحن ملتزمون بضمان تجربة سلسة في أماكن أخرى على موقعنا ونركز على حل تأخير عملية الدفع. سنوفر تحديثات بشكل دوري. مع خالص التحيات Dears, We are currently experiencing a slowdown in the checkout process across our stores due to an unexpectedly high volume of traffic. Please be assured that our team is actively working to resolve this issue as quickly as possible. Apart from this, please note that our overall platform remains fully operational. We are dedicated to ensuring a seamless experience elsewhere on our site and are focused on resolving the checkout delay. We will provide regular updates. Best regards

2. 12 marzo 2024 alle ore 19:48 UTCidentified

   أعزاؤنا التجار لقد تمكنا من تحديد سبب البطء في عملية الدفع عبر متاجرنا. فريقنا يعمل الآن بجد لحل هذه المشكلة في أسرع وقت ممكن. نقدر صبركم بينما نقوم بالتعديلات اللازمة Dears, We have identified the cause of the slowdown in the checkout process across our stores. Our team is now working diligently to resolve this issue as swiftly as possible. We appreciate your patience as we make the necessary adjustments.

3. 12 marzo 2024 alle ore 20:38 UTCresolved

   أعزاؤنا التجار منصتنا تعمل تحت ظروف مرورية طبيعية وبسرعة طبيعية الان . قد نواجه بعض التأخيرالطفيف في إضافة المنتجات إلى السلة في حال زيادة الزيارات، ونحن نراقب الوضع لضمان استقرار المنصة. نعتبر المشكلة قد تم حلها، الفريق سيواصل العمل ومراقبة المنصة. Dears, Our platform is operating under normal traffic and normal speed. At times we might have some delays on add to cart if the volume of traffic increase and we are monitoring to ensure the stability of the platform. We consider the issue resolve but rest assure that the team will continue to work and monitor the platform. Best regards

1. 6 marzo 2024 alle ore 14:14 UTCresolved

   Dear all, Our stores and associated services experienced multiple instances of complete downtime, starting at 2:57:21 PM and lasting until 3:12:05 PM, totaling 9 minutes and 54 seconds. Our team promptly addressed the issue and successfully resolved it. We are now operating smoothly تجارنا الأعزاء تعرضت متاجرنا والخدمات المرتبطة بها لعدة حالات من تعطل كامل، بدءًا من الساعة 2:57:21 مساءً وحتى الساعة 3:12:05 مساءً، بمجموع 9 دقائق و 54 ثانية. فريقنا استجاب للمشكلة على الفور ونجح في حلها بشكل صحيح. نعمل الآن بسلاسة. نقدر تفهمكم الكريم

1. 2 gennaio 2024 alle ore 09:39 UTCinvestigating

   We are currently investigating this issue.

2. 2 gennaio 2024 alle ore 09:40 UTCinvestigating

   We are continuing to investigate this issue.

3. 2 gennaio 2024 alle ore 09:40 UTCidentified

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

4. 2 gennaio 2024 alle ore 09:42 UTCresolved

   This incident has been resolved.

1. 2 dicembre 2023 alle ore 16:54 UTCresolved

   تجارنا الأعزاء تعرضت متاجرنا لبطء شديد غير متوقع لمدة دقيقة واحدة، وانقطعت الخدمة عن بعض المتاجر من الساعة 7:20 مساءً حتى الساعة 7:21 مساءً، قام فريق الدعم لدينا بحل المشكلة بسرعة. نقدر تفهمكم الكريم Our stores experienced an unexpected sever slowness/ partial outage and got a timeout from 7:20 pm to 7:21 pm. Our support team promptly resolved the issue. Appreciating your kind understanding