<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Clubs PSMT Status - Incident history</title>
    <link>https://it-ops-clubs.status.pricesmart.io</link>
    <description>Clubs PSMT</description>
    <pubDate>Tue, 11 Mar 2025 20:02:18 +0000</pubDate>
    
<item>
  <title>Problems with point redemption and gift card activation -  Club BOLIVAR 6806 - 2025-03-11</title>
  <description>
    Type: Incident
    Duration: 41 minutes

    Affected Components: 6806 - Bolivar
    Mar 11, 20:02:18 GMT+0 - Investigating - We are currently addressing an incident affecting our systems, which is impacting Club Bolívar 6806 in the Dominican Republic and causing issues with points redemption and gift card activation. Our team is actively investigating the cause and working diligently to restore full functionality as soon as possible.

We will provide further updates as we make progress. Thank you for your understanding and patience as we work to resolve this issue. Mar 11, 20:43:45 GMT+0 - Resolved - The recent incident has been successfully resolved, and all affected systems are now back to normal operation.

### **Incident Summary**

**Brief Description of the Problem:**  
A connectivity issue between the servers of Club BOLIVAR 6806 was affecting the point redemption and gift card activation process.

### **Current Status**

All systems have been fully restored, and normal functionality has been confirmed. We are monitoring the systems closely to ensure continued stability.

### **Root Cause**

Due to a misconfiguration in Change Request CHG0030818, the connectivity between the servers of Club BOLIVAR 6806 was impacted.

Thank you for your patience and understanding as we worked to resolve this issue. We appreciate your continued support and trust in our commitment to ensuring system reliability. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 41 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 11&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:02:18&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently addressing an incident affecting our systems, which is impacting Club Bolívar 6806 in the Dominican Republic and causing issues with points redemption and gift card activation. Our team is actively investigating the cause and working diligently to restore full functionality as soon as possible.

We will provide further updates as we make progress. Thank you for your understanding and patience as we work to resolve this issue..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 11&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:43:45&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The recent incident has been successfully resolved, and all affected systems are now back to normal operation.

### **Incident Summary**

**Brief Description of the Problem:**  
A connectivity issue between the servers of Club BOLIVAR 6806 was affecting the point redemption and gift card activation process.

### **Current Status**

All systems have been fully restored, and normal functionality has been confirmed. We are monitoring the systems closely to ensure continued stability.

### **Root Cause**

Due to a misconfiguration in Change Request CHG0030818, the connectivity between the servers of Club BOLIVAR 6806 was impacted.

Thank you for your patience and understanding as we worked to resolve this issue. We appreciate your continued support and trust in our commitment to ensuring system reliability..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 11 Mar 2025 20:02:18 +0000</pubDate>
  <link>https://it-ops-clubs.status.pricesmart.io/incident/cm84x3tr4000111ltf9encnyg</link>
  <guid>https://it-ops-clubs.status.pricesmart.io/incident/cm84x3tr4000111ltf9encnyg</guid>
</item>

<item>
  <title>POS 8702 down on 2025-03-04</title>
  <description>
    Type: Incident
    Duration: 3 hours and 45 minutes

    Affected Components: 8702 - Portmore
    Mar 4, 15:58:12 GMT+0 - Monitoring - The system is currently stable, and we are actively monitoring the situation to ensure continued stability. Our team is closely observing for any signs of potential impact and will take immediate action if necessary. We will provide additional updates as we have more information.

Thank you for your patience and understanding as we work to maintain a stable environment. Mar 4, 16:30:34 GMT+0 - Resolved - The recent incident has been successfully resolved, and all affected systems are now back to normal operation.

### 

Thank you for your patience and understanding as we worked to resolve this issue. We appreciate your continued support and trust in our commitment to ensuring system reliability. Mar 4, 12:45:49 GMT+0 - Investigating - We are currently addressing an incident affecting our systems, which is impacting 8702\. Our team is actively investigating the cause and working diligently to restore full functionality as soon as possible.

We will provide further updates as we make progress. Thank you for your understanding and patience as we work to resolve this issue. Mar 4, 14:02:19 GMT+0 - Identified - We have identified the cause of the current issue and our team is actively working to resolve it. Rest assured, we are making every effort to restore full functionality as quickly as possible.

We appreciate your patience and understanding during this time. Further updates will be provided as we make progress toward a resolution. Mar 4, 15:38:55 GMT+0 - Identified - We have identified the cause of the current issue and our team is actively working to resolve it. Rest assured, we are making every effort to restore full functionality as quickly as possible.

We appreciate your patience and understanding during this time. Further updates will be provided as we make progress toward a resolution. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 45 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:58:12&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  The system is currently stable, and we are actively monitoring the situation to ensure continued stability. Our team is closely observing for any signs of potential impact and will take immediate action if necessary. We will provide additional updates as we have more information.

Thank you for your patience and understanding as we work to maintain a stable environment..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:30:34&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The recent incident has been successfully resolved, and all affected systems are now back to normal operation.

### 

Thank you for your patience and understanding as we worked to resolve this issue. We appreciate your continued support and trust in our commitment to ensuring system reliability..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:45:49&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently addressing an incident affecting our systems, which is impacting 8702\. Our team is actively investigating the cause and working diligently to restore full functionality as soon as possible.

We will provide further updates as we make progress. Thank you for your understanding and patience as we work to resolve this issue..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:02:19&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We have identified the cause of the current issue and our team is actively working to resolve it. Rest assured, we are making every effort to restore full functionality as quickly as possible.

We appreciate your patience and understanding during this time. Further updates will be provided as we make progress toward a resolution..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:38:55&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We have identified the cause of the current issue and our team is actively working to resolve it. Rest assured, we are making every effort to restore full functionality as quickly as possible.

We appreciate your patience and understanding during this time. Further updates will be provided as we make progress toward a resolution..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 4 Mar 2025 12:45:49 +0000</pubDate>
  <link>https://it-ops-clubs.status.pricesmart.io/incident/cm7uhfmka00nb2qim5us27t2c</link>
  <guid>https://it-ops-clubs.status.pricesmart.io/incident/cm7uhfmka00nb2qim5us27t2c</guid>
</item>

<item>
  <title>The Elera report for sales closing is having issues on 2025-02-26</title>
  <description>
    Type: Incident
    Duration: 54 minutes

    Affected Components: POS Elera
    Feb 27, 01:12:11 GMT+0 - Investigating - We are currently addressing an incident affecting our systems, which is impacting the Elera closing report. Our team is actively investigating the cause and working diligently to restore full functionality as soon as possible.

We will provide further updates as we make progress. Thank you for your understanding and patience as we work to resolve this issue. Feb 27, 02:05:53 GMT+0 - Resolved - The recent incident has been successfully resolved, and all affected systems are now back to normal operation.

### **Incident Summary**

**Brief Description of the Problem:**  
The Elera report for sales closing was experiencing issues, specifically affecting sales closure in Trinidad.

### **Current Status**

All systems have been fully restored, and normal functionality has been confirmed. We are monitoring the systems closely to ensure continued stability.

### **Root Cause**

A recent change in Domo modified a field that was essential for the sales closing process. This change caused missing or incorrect data in the reports, impacting the final sales calculations.

The issue was resolved by adding the missing field back in both Domo and Snowflake, restoring the proper data flow for sales closing.

Thank you for your patience and understanding as we worked to resolve this issue. We appreciate your continued support and trust in our commitment to ensuring system reliability. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 54 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:12:11&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently addressing an incident affecting our systems, which is impacting the Elera closing report. Our team is actively investigating the cause and working diligently to restore full functionality as soon as possible.

We will provide further updates as we make progress. Thank you for your understanding and patience as we work to resolve this issue..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;02:05:53&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The recent incident has been successfully resolved, and all affected systems are now back to normal operation.

### **Incident Summary**

**Brief Description of the Problem:**  
The Elera report for sales closing was experiencing issues, specifically affecting sales closure in Trinidad.

### **Current Status**

All systems have been fully restored, and normal functionality has been confirmed. We are monitoring the systems closely to ensure continued stability.

### **Root Cause**

A recent change in Domo modified a field that was essential for the sales closing process. This change caused missing or incorrect data in the reports, impacting the final sales calculations.

The issue was resolved by adding the missing field back in both Domo and Snowflake, restoring the proper data flow for sales closing.

Thank you for your patience and understanding as we worked to resolve this issue. We appreciate your continued support and trust in our commitment to ensuring system reliability..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 27 Feb 2025 01:12:11 +0000</pubDate>
  <link>https://it-ops-clubs.status.pricesmart.io/incident/cm7mng8w7003u61zoe3knwwsx</link>
  <guid>https://it-ops-clubs.status.pricesmart.io/incident/cm7mng8w7003u61zoe3knwwsx</guid>
</item>

<item>
  <title>Incident: 8001 Terminals Frozen.</title>
  <description>
    Type: Incident
    Duration: 1 day, 5 hours and 47 minutes

    Affected Components: 8001 - Chaguanas
    Jan 30, 17:37:50 GMT+0 - Monitoring - Hello team. Now all the terminals in the club are working fine. Keep monitoring.  Jan 30, 17:00:16 GMT+0 - Investigating - Hello team, in this moment we are fencing a problem with the controllers of Elera servers on 8001 , by now all the terminals are frozen. We are currently investigating this incident. Jan 31, 22:47:16 GMT+0 - Resolved - The incident has been successfully resolved and is now closed.

Our systems are back to normal operation. Thank you for your understanding and support throughout this process. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 5 hours and 47 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 30&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:37:50&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  Hello team. Now all the terminals in the club are working fine. Keep monitoring. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 30&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:00:16&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  Hello team, in this moment we are fencing a problem with the controllers of Elera servers on 8001 , by now all the terminals are frozen. We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 31&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:47:16&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The incident has been successfully resolved and is now closed.

Our systems are back to normal operation. Thank you for your understanding and support throughout this process..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 30 Jan 2025 17:00:16 +0000</pubDate>
  <link>https://it-ops-clubs.status.pricesmart.io/incident/cm6jkzn8a002714jg58o3utld</link>
  <guid>https://it-ops-clubs.status.pricesmart.io/incident/cm6jkzn8a002714jg58o3utld</guid>
</item>

<item>
  <title>Domo reports for Elera are not updating for all Trinidad and Tobago clubs on 2025-01-23</title>
  <description>
    Type: Incident
    Duration: 22 minutes

    
    Jan 23, 18:13:14 GMT+0 - Investigating - We are currently addressing an incident affecting our systems, which is impacting the information for Elera is not being updated. Our team is actively investigating the cause and working diligently to restore full functionality as soon as possible.

We will provide further updates as we make progress. Thank you for your understanding and patience as we work to resolve this issue. Jan 23, 18:27:01 GMT+0 - Monitoring - The system is currently stable, and we are actively monitoring the situation to ensure continued stability. Our team is closely observing for any signs of potential impact and will take immediate action if necessary. We will provide additional updates as we have more information.

Thank you for your patience and understanding as we work to maintain a stable environment. Jan 23, 18:35:30 GMT+0 - Resolved - The recent incident has been successfully resolved, and all affected systems are now back to normal operation.

### **Incident Summary**

**Brief Description of the Problem:**  
A dataset used for updating Domo reports failed to execute, resulting in outdated information being displayed. This issue impacted the data updates for key reports used by Elera, affecting visibility into Trinidad and Tobago clubs.

### **Current Status**

All systems have been fully restored, and normal functionality has been confirmed. We are monitoring the systems closely to ensure continued stability.

### **Root Cause**

The root cause of the incident is still under investigation by the ADAM team. Preliminary findings indicate an issue with the dataset&#039;s execution process, which prevented it from completing successfully. Further analysis is being conducted to identify the underlying factors and prevent recurrence.

Thank you for your patience and understanding as we worked to resolve this issue. We appreciate your continued support and trust in our commitment to ensuring system reliability. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 22 minutes</p>
    
    &lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:13:14&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently addressing an incident affecting our systems, which is impacting the information for Elera is not being updated. Our team is actively investigating the cause and working diligently to restore full functionality as soon as possible.

We will provide further updates as we make progress. Thank you for your understanding and patience as we work to resolve this issue..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:27:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  The system is currently stable, and we are actively monitoring the situation to ensure continued stability. Our team is closely observing for any signs of potential impact and will take immediate action if necessary. We will provide additional updates as we have more information.

Thank you for your patience and understanding as we work to maintain a stable environment..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:35:30&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The recent incident has been successfully resolved, and all affected systems are now back to normal operation.

### **Incident Summary**

**Brief Description of the Problem:**  
A dataset used for updating Domo reports failed to execute, resulting in outdated information being displayed. This issue impacted the data updates for key reports used by Elera, affecting visibility into Trinidad and Tobago clubs.

### **Current Status**

All systems have been fully restored, and normal functionality has been confirmed. We are monitoring the systems closely to ensure continued stability.

### **Root Cause**

The root cause of the incident is still under investigation by the ADAM team. Preliminary findings indicate an issue with the dataset&#039;s execution process, which prevented it from completing successfully. Further analysis is being conducted to identify the underlying factors and prevent recurrence.

Thank you for your patience and understanding as we worked to resolve this issue. We appreciate your continued support and trust in our commitment to ensuring system reliability..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 23 Jan 2025 18:13:14 +0000</pubDate>
  <link>https://it-ops-clubs.status.pricesmart.io/incident/cm69niigq000obazb1lhbwamt</link>
  <guid>https://it-ops-clubs.status.pricesmart.io/incident/cm69niigq000obazb1lhbwamt</guid>
</item>

<item>
  <title>Elera runbook&#039;s jobs failed on 2024-11-07</title>
  <description>
    Type: Incident
    Duration: 1 hour and 26 minutes

    Affected Components: POS Elera
    Nov 7, 12:18:50 GMT+0 - Investigating - We are currently investigating an incident affecting our systems, impacting the jobs related with Elera. Our team is actively working to identify and resolve the issue. Further updates to follow. Thank you for your patience. Nov 7, 13:20:02 GMT+0 - Monitoring - The system is stable but the situation is being actively monitored. We are closely watching for any potential impact and taking necessary measures. Further updates to follow. Thank you for your patience and understanding. Nov 7, 13:44:38 GMT+0 - Resolved - The incident has been successfully resolved and is now closed.

Brief description of the problem:

The Elera jobs at Pricesmart experienced disruptions potentially related to compatibility issues with the Python version used in the runbook. The Infrastructure team has been engaged to investigate further.

Actual state:

The Elera jobs are currently operational, but monitoring and further analysis are ongoing to ensure stability and prevent recurrence.

Root Cause:

The incident may have been caused by an incompatibility between the Python version specified in the runbook and the current system requirements for Elera jobs. Further investigation by the Infrastructure team is needed to confirm the exact cause and determine any necessary adjustments.

Our systems are back to normal operation. Thank you for your understanding and support throughout this process. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 26 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 7&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:18:50&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating an incident affecting our systems, impacting the jobs related with Elera. Our team is actively working to identify and resolve the issue. Further updates to follow. Thank you for your patience..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 7&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:20:02&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  The system is stable but the situation is being actively monitored. We are closely watching for any potential impact and taking necessary measures. Further updates to follow. Thank you for your patience and understanding..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 7&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:44:38&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The incident has been successfully resolved and is now closed.

Brief description of the problem:

The Elera jobs at Pricesmart experienced disruptions potentially related to compatibility issues with the Python version used in the runbook. The Infrastructure team has been engaged to investigate further.

Actual state:

The Elera jobs are currently operational, but monitoring and further analysis are ongoing to ensure stability and prevent recurrence.

Root Cause:

The incident may have been caused by an incompatibility between the Python version specified in the runbook and the current system requirements for Elera jobs. Further investigation by the Infrastructure team is needed to confirm the exact cause and determine any necessary adjustments.

Our systems are back to normal operation. Thank you for your understanding and support throughout this process..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 7 Nov 2024 12:18:50 +0000</pubDate>
  <link>https://it-ops-clubs.status.pricesmart.io/incident/cm379y5l9001m2cttxutkbidu</link>
  <guid>https://it-ops-clubs.status.pricesmart.io/incident/cm379y5l9001m2cttxutkbidu</guid>
</item>

<item>
  <title>Improving the Speed and Efficiency of Our Communications</title>
  <description>
    Type: Maintenance
    Duration: 1 hour

    Affected Components: 6704 - Santa Ana, 6602 - Tegucigalpa, 6305 - San Cristobal, 6102 - Canasgordas, 6805 - San Isidro, 6109 - Floridablanca, 6107 - Chia, 6307 - Escuintla, 6407 - Santa Ana, 6204 - David, 6207 - Veraguas, 8902 - Ctra. Masaya, 8701 - Kingston, 6408 - Liberia, 6110 - El Poblado, 6402 - Escazu, 6205 - Brisas, 6401-Zapote, 6105 - Salitre, 6104 - Pereira, 8003 - Mausica, 6303 - Pradera, 6202 - Via Brasil, 6403 - Heredia, 6404 - Llorente, 6203 - El Dorado, 6603 - San Pedro Sula, 6405 - Alajuela, 8101 - Virgin Islands, 8004 - San Fernando, 6801 - Los Prados, 6106 - Las Americas, 8901 - Managua, 6103 - Menga, 6304 - Fraijanes, 6306 - Aranda, 6802 - Santiago, 6301 - Mira Flores, 8702 - Portmore, 6206 - Costa Verde, 6208 - Metro Park, 7802 - Offsite Bakery, 6604 - El Sauce, 6101 - Barranquilla Norte, 8002 - Port of Spain, 6406 - Tres Rios, 6804 - Arroyo Hondo, 6108 - Usaquen, 6701 - Santa Elena, 6702 - Metro Centre, 6703 - San Miguel, 8201 - Aruba, 8501 - Barbados, Agile Server App, Agile Server Database, 8001 - Chaguanas, 6806 - Bolivar, POS Elera
    Nov 1, 04:00:00 GMT+0 - Identified - Our Information Technology Network Team will implement a firmware upgrade to enhance the speed and efficiency of our Azure communications.

**Purpose of the change:** Upgrade the firmware of SD-WAN routers to improve connectivity between the Atlanta Data Center and Azure Cloud.

**Date and time of the change:** October 31, 2024 - 10:00 p.m., CST

**Expected impact:** No significant disruptions are expected, but there may be a 6-12 minute interruption for all Azure systems during the device restart.

**Benefits:** This upgrade will fix firmware bugs and improve security and speed for Azure connectivity.

**Technical support:** Please contact our PriceSmart IT Global Support Team if you experience any issues during the process.

**PriceSmart IT Global Support Team** Nov 1, 04:00:01 GMT+0 - Identified - Maintenance is now in progress Nov 1, 05:00:00 GMT+0 - Completed - Maintenance has completed successfully 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , </p>
    &lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 1&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;04:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Our Information Technology Network Team will implement a firmware upgrade to enhance the speed and efficiency of our Azure communications.

**Purpose of the change:** Upgrade the firmware of SD-WAN routers to improve connectivity between the Atlanta Data Center and Azure Cloud.

**Date and time of the change:** October 31, 2024 - 10:00 p.m., CST

**Expected impact:** No significant disruptions are expected, but there may be a 6-12 minute interruption for all Azure systems during the device restart.

**Benefits:** This upgrade will fix firmware bugs and improve security and speed for Azure connectivity.

**Technical support:** Please contact our PriceSmart IT Global Support Team if you experience any issues during the process.

**PriceSmart IT Global Support Team**.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 1&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;04:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 1&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;05:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 1 Nov 2024 04:00:00 +0000</pubDate>
  <link>https://it-ops-clubs.status.pricesmart.io/maintenance/cm2w47gmq0001be370y375vl4</link>
  <guid>https://it-ops-clubs.status.pricesmart.io/maintenance/cm2w47gmq0001be370y375vl4</guid>
</item>

<item>
  <title>Outdated data in Domo on 2024-10-29</title>
  <description>
    Type: Incident
    Duration: 1 day, 17 hours and 4 minutes

    Affected Components: POS Elera
    Oct 30, 02:35:19 GMT+0 - Investigating - We are currently investigating an incident affecting our systems, impacting the reported data in Domo for Elera. Our team is actively working to identify and resolve the issue. Further updates to follow. Thank you for your patience. Oct 30, 02:35:33 GMT+0 - Identified - The issue has been identified and our team is working on resolving it. We appreciate your patience as we work towards a resolution. Further updates to follow. Thank you for your understanding. Oct 30, 02:45:20 GMT+0 - Monitoring - The system is stable and data is completed but the situation is being actively monitored and waiting the response from Domo support. We are closely watching for any potential impact and taking necessary measures. Further updates to follow. Thank you for your patience and understanding. Oct 31, 19:39:11 GMT+0 - Resolved - The incident has been successfully resolved and is now closed.

There was a bug in Domo that was fixed by Domo Support.

Our systems are back to normal operation. Thank you for your understanding and support throughout this process. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 17 hours and 4 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 30&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;02:35:19&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating an incident affecting our systems, impacting the reported data in Domo for Elera. Our team is actively working to identify and resolve the issue. Further updates to follow. Thank you for your patience..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 30&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;02:35:33&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  The issue has been identified and our team is working on resolving it. We appreciate your patience as we work towards a resolution. Further updates to follow. Thank you for your understanding..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 30&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;02:45:20&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  The system is stable and data is completed but the situation is being actively monitored and waiting the response from Domo support. We are closely watching for any potential impact and taking necessary measures. Further updates to follow. Thank you for your patience and understanding..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 31&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:39:11&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The incident has been successfully resolved and is now closed.

There was a bug in Domo that was fixed by Domo Support.

Our systems are back to normal operation. Thank you for your understanding and support throughout this process..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 30 Oct 2024 02:35:19 +0000</pubDate>
  <link>https://it-ops-clubs.status.pricesmart.io/incident/cm2v9kxuw0007fqqy9drrpu81</link>
  <guid>https://it-ops-clubs.status.pricesmart.io/incident/cm2v9kxuw0007fqqy9drrpu81</guid>
</item>

<item>
  <title>Missing membership accounts information in Elera on 2024-10-23</title>
  <description>
    Type: Incident
    Duration: 7 hours and 13 minutes

    Affected Components: POS Elera
    Oct 23, 15:20:58 GMT+0 - Investigating - We are currently investigating an incident affecting our systems, impacting the memberships in Elera. Our team is actively working to identify and resolve the issue. Further updates to follow. Thank you for your patience. Oct 23, 16:27:24 GMT+0 - Identified - The issue has been identified and our team is working on resolving it. We appreciate your patience as we work towards a resolution. Further updates to follow. Thank you for your understanding. Oct 23, 17:12:24 GMT+0 - Monitoring - The system is stable but the situation is being actively monitored. We are closely watching for any potential impact and taking necessary measures. Further updates to follow. Thank you for your patience and understanding. Oct 23, 22:33:49 GMT+0 - Resolved - The incident has been successfully resolved and is now closed.

Brief description of the problem:

Actual state:

Root Cause:

Our systems are back to normal operation. Thank you for your understanding and support throughout this process. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 7 hours and 13 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:20:58&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating an incident affecting our systems, impacting the memberships in Elera. Our team is actively working to identify and resolve the issue. Further updates to follow. Thank you for your patience..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:27:24&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  The issue has been identified and our team is working on resolving it. We appreciate your patience as we work towards a resolution. Further updates to follow. Thank you for your understanding..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:12:24&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  The system is stable but the situation is being actively monitored. We are closely watching for any potential impact and taking necessary measures. Further updates to follow. Thank you for your patience and understanding..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:33:49&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The incident has been successfully resolved and is now closed.

Brief description of the problem:

Actual state:

Root Cause:

Our systems are back to normal operation. Thank you for your understanding and support throughout this process..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 23 Oct 2024 15:20:58 +0000</pubDate>
  <link>https://it-ops-clubs.status.pricesmart.io/incident/cm2m0umj8001h2v6ma32645wh</link>
  <guid>https://it-ops-clubs.status.pricesmart.io/incident/cm2m0umj8001h2v6ma32645wh</guid>
</item>

<item>
  <title>Improving the Speed and Efficiency of Our Communications</title>
  <description>
    Type: Maintenance
    Duration: 1 hour

    Affected Components: 6704 - Santa Ana, 6602 - Tegucigalpa, 6305 - San Cristobal, 6102 - Canasgordas, 6805 - San Isidro, 6109 - Floridablanca, 6107 - Chia, 6307 - Escuintla, 6407 - Santa Ana, 6204 - David, 6207 - Veraguas, 8902 - Ctra. Masaya, 8701 - Kingston, 6408 - Liberia, 6110 - El Poblado, 6402 - Escazu, 6205 - Brisas, 6401-Zapote, 6105 - Salitre, 6104 - Pereira, 8003 - Mausica, 6303 - Pradera, 6202 - Via Brasil, 6403 - Heredia, 6404 - Llorente, 6203 - El Dorado, 6603 - San Pedro Sula, 6405 - Alajuela, 8101 - Virgin Islands, 8004 - San Fernando, 6801 - Los Prados, 6106 - Las Americas, 8901 - Managua, 6103 - Menga, 6304 - Fraijanes, 6306 - Aranda, 6802 - Santiago, 6301 - Mira Flores, 8702 - Portmore, 6206 - Costa Verde, 6208 - Metro Park, 7802 - Offsite Bakery, 6604 - El Sauce, 6101 - Barranquilla Norte, 8002 - Port of Spain, 6406 - Tres Rios, 6804 - Arroyo Hondo, 6108 - Usaquen, 6701 - Santa Elena, 6702 - Metro Centre, 6703 - San Miguel, 8201 - Aruba, 8501 - Barbados, Agile Server App, Agile Server Database, 8001 - Chaguanas, 6806 - Bolivar, POS Elera
    Oct 23, 04:00:00 GMT+0 - Identified - Our Information Technology Network Team will implement a firmware upgrade to enhance the speed and efficiency of our Azure communications.

* **Purpose of the change:** Upgrade the firmware of SD-WAN routers to improve connectivity between the Atlanta Data Center and Azure Cloud.
* **Date and time of the change:** October 22, 2024 - 10:00 p.m., CST
* **Expected impact:** No significant disruptions are expected, but there may be a 6-12 minute interruption for all Azure systems during the device restart.
* **Benefits:** This upgrade will fix firmware bugs and improve security and speed for Azure connectivity.
* **Technical support:** Please contact our PriceSmart IT Global Support Team if you experience any issues during the process.

**PriceSmart IT Global Support Team** Oct 23, 04:00:01 GMT+0 - Identified - Maintenance is now in progress Oct 23, 05:00:00 GMT+0 - Completed - Maintenance has completed successfully 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , </p>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;04:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Our Information Technology Network Team will implement a firmware upgrade to enhance the speed and efficiency of our Azure communications.

* **Purpose of the change:** Upgrade the firmware of SD-WAN routers to improve connectivity between the Atlanta Data Center and Azure Cloud.
* **Date and time of the change:** October 22, 2024 - 10:00 p.m., CST
* **Expected impact:** No significant disruptions are expected, but there may be a 6-12 minute interruption for all Azure systems during the device restart.
* **Benefits:** This upgrade will fix firmware bugs and improve security and speed for Azure connectivity.
* **Technical support:** Please contact our PriceSmart IT Global Support Team if you experience any issues during the process.

**PriceSmart IT Global Support Team**.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;04:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;05:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 23 Oct 2024 04:00:00 +0000</pubDate>
  <link>https://it-ops-clubs.status.pricesmart.io/maintenance/cm2ji83nw000wzfk2wrm13c51</link>
  <guid>https://it-ops-clubs.status.pricesmart.io/maintenance/cm2ji83nw000wzfk2wrm13c51</guid>
</item>

<item>
  <title>Missing membership accounts information in Elera on 2024-10-18</title>
  <description>
    Type: Incident
    Duration: 1 day, 23 hours and 31 minutes

    Affected Components: POS Elera
    Oct 18, 15:37:33 GMT+0 - Investigating - We are currently investigating an incident affecting our systems, impacting the accounts information in Elera. Our team is actively working to identify and resolve the issue. Further updates to follow. Thank you for your patience. Oct 18, 15:33:38 GMT+0 - Investigating - We are currently investigating an incident affecting our systems, impacting the accounts information in Elera. Our team is actively working to identify and resolve the issue. Further updates to follow. Thank you for your patience. Oct 18, 15:37:42 GMT+0 - Identified - The issue has been identified and our team is working on resolving it. We appreciate your patience as we work towards a resolution. Further updates to follow. Thank you for your understanding. Oct 18, 18:46:59 GMT+0 - Monitoring - The system is stable but the situation is being actively monitored. We are closely watching for any potential impact and taking necessary measures. Further updates to follow. Thank you for your patience and understanding. Oct 18, 22:52:22 GMT+0 - Monitoring - The system is stable but the situation is being actively monitored. We are closely watching for any potential impact and taking necessary measures. Further updates to follow. Thank you for your patience and understanding. Oct 20, 15:04:35 GMT+0 - Resolved - The incident has been successfully resolved and is now closed.

Our systems are back to normal operation. Thank you for your understanding and support throughout this process. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 23 hours and 31 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:37:33&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating an incident affecting our systems, impacting the accounts information in Elera. Our team is actively working to identify and resolve the issue. Further updates to follow. Thank you for your patience..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:33:38&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating an incident affecting our systems, impacting the accounts information in Elera. Our team is actively working to identify and resolve the issue. Further updates to follow. Thank you for your patience..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:37:42&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  The issue has been identified and our team is working on resolving it. We appreciate your patience as we work towards a resolution. Further updates to follow. Thank you for your understanding..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:46:59&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  The system is stable but the situation is being actively monitored. We are closely watching for any potential impact and taking necessary measures. Further updates to follow. Thank you for your patience and understanding..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:52:22&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  The system is stable but the situation is being actively monitored. We are closely watching for any potential impact and taking necessary measures. Further updates to follow. Thank you for your patience and understanding..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:04:35&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The incident has been successfully resolved and is now closed.

Our systems are back to normal operation. Thank you for your understanding and support throughout this process..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 18 Oct 2024 15:33:38 +0000</pubDate>
  <link>https://it-ops-clubs.status.pricesmart.io/incident/cm2ew3n2p000rfm9fu7ar78fm</link>
  <guid>https://it-ops-clubs.status.pricesmart.io/incident/cm2ew3n2p000rfm9fu7ar78fm</guid>
</item>

<item>
  <title>Account signed up online and is not found in Elera on 2024-10-17</title>
  <description>
    Type: Incident
    Duration: 20 hours and 30 minutes

    Affected Components: POS Elera
    Oct 17, 19:01:23 GMT+0 - Investigating - We are currently investigating an incident affecting our systems, there was a problem with our CDC tool that failed to bring the information for account. Our team is actively working to identify and resolve the issue. Further updates to follow. Thank you for your patience. Oct 18, 15:26:45 GMT+0 - Monitoring - The system is stable but the situation is being actively monitored. We are closely watching for any potential impact and taking necessary measures. Further updates to follow. Thank you for your patience and understanding. Oct 18, 15:31:47 GMT+0 - Resolved - The incident has been successfully resolved and is now closed.

Our systems are back to normal operation. Thank you for your understanding and support throughout this process. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 20 hours and 30 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 17&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:01:23&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating an incident affecting our systems, there was a problem with our CDC tool that failed to bring the information for account. Our team is actively working to identify and resolve the issue. Further updates to follow. Thank you for your patience..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:26:45&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  The system is stable but the situation is being actively monitored. We are closely watching for any potential impact and taking necessary measures. Further updates to follow. Thank you for your patience and understanding..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:31:47&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The incident has been successfully resolved and is now closed.

Our systems are back to normal operation. Thank you for your understanding and support throughout this process..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 17 Oct 2024 19:01:23 +0000</pubDate>
  <link>https://it-ops-clubs.status.pricesmart.io/incident/cm2do2ynn000fopof6otz67gb</link>
  <guid>https://it-ops-clubs.status.pricesmart.io/incident/cm2do2ynn000fopof6otz67gb</guid>
</item>

<item>
  <title>Maintenance Window Notification: DB Cluster Alarm Disabling and VPN Security Group Tagging</title>
  <description>
    Type: Maintenance
    Duration: 2 hours

    Affected Components: 6704 - Santa Ana, 6602 - Tegucigalpa, 6305 - San Cristobal, 6102 - Canasgordas, 6805 - San Isidro, 6109 - Floridablanca, 6107 - Chia, 6307 - Escuintla, 6407 - Santa Ana, 6204 - David, 6207 - Veraguas, 8902 - Ctra. Masaya, 8701 - Kingston, 6408 - Liberia, 6110 - El Poblado, 6402 - Escazu, 6205 - Brisas, 6401-Zapote, 6105 - Salitre, 6104 - Pereira, 8003 - Mausica, 6303 - Pradera, 6202 - Via Brasil, 6403 - Heredia, 6404 - Llorente, 6203 - El Dorado, 6603 - San Pedro Sula, 6405 - Alajuela, 8101 - Virgin Islands, 8004 - San Fernando, 6801 - Los Prados, 6106 - Las Americas, 8901 - Managua, 6103 - Menga, 6304 - Fraijanes, 6306 - Aranda, 6802 - Santiago, 6301 - Mira Flores, 8702 - Portmore, 6206 - Costa Verde, 6208 - Metro Park, 7802 - Offsite Bakery, 6604 - El Sauce, 6101 - Barranquilla Norte, 8002 - Port of Spain, 6406 - Tres Rios, 6804 - Arroyo Hondo, 6108 - Usaquen, 6701 - Santa Elena, 6702 - Metro Centre, 6703 - San Miguel, 8201 - Aruba, 8501 - Barbados, Agile Server App, Agile Server Database, 8001 - Chaguanas, 6806 - Bolivar, POS Elera
    Oct 15, 17:27:25 GMT+0 - Identified - Dear Team,

This is to inform you about a scheduled maintenance window during which the following changes will be implemented:

* **Disabling alarms for the DB-CLUSTER1 cluster**
* **Tagging a VPN security group with Abacus**

**Maintenance Window Details:**

* **Date:** 2024-10-15
* **Time:** October 16, 2024 at 5:00 AM GMT – October 16, 2024 at 7:00 AM GMT
* **Action Required:** No immediate action is needed from your side, but please report any anomalies you may observe during or after the maintenance window.

Thank you for your cooperation! Oct 16, 07:00:00 GMT+0 - Completed - Maintenance has completed successfully Oct 16, 05:00:00 GMT+0 - Identified - Dear Team,

This is to inform you about a scheduled maintenance window during which the following changes will be implemented:

* **Disabling alarms for the DB-CLUSTER1 cluster**
* **Tagging a VPN security group with Abacus**

**Maintenance Window Details:**

* **Date:** 2024-10-15
* **Time:** 22:00:00 to 00:00:00 PST
* **Action Required:** No immediate action is needed from your side, but please report any anomalies you may observe during or after the maintenance window.

Thank you for your cooperation! Oct 16, 05:00:01 GMT+0 - Identified - Maintenance is now in progress 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , </p>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 15&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:27:25&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Dear Team,

This is to inform you about a scheduled maintenance window during which the following changes will be implemented:

* **Disabling alarms for the DB-CLUSTER1 cluster**
* **Tagging a VPN security group with Abacus**

**Maintenance Window Details:**

* **Date:** 2024-10-15
* **Time:** October 16, 2024 at 5:00 AM GMT – October 16, 2024 at 7:00 AM GMT
* **Action Required:** No immediate action is needed from your side, but please report any anomalies you may observe during or after the maintenance window.

Thank you for your cooperation!.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 16&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 16&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;05:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Dear Team,

This is to inform you about a scheduled maintenance window during which the following changes will be implemented:

* **Disabling alarms for the DB-CLUSTER1 cluster**
* **Tagging a VPN security group with Abacus**

**Maintenance Window Details:**

* **Date:** 2024-10-15
* **Time:** 22:00:00 to 00:00:00 PST
* **Action Required:** No immediate action is needed from your side, but please report any anomalies you may observe during or after the maintenance window.

Thank you for your cooperation!.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 16&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;05:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 16 Oct 2024 05:00:00 +0000</pubDate>
  <link>https://it-ops-clubs.status.pricesmart.io/maintenance/cm29hw4la0013gqihtv1fjq9t</link>
  <guid>https://it-ops-clubs.status.pricesmart.io/maintenance/cm29hw4la0013gqihtv1fjq9t</guid>
</item>

<item>
  <title>POS Elera Service Bus down on 2024-10-10</title>
  <description>
    Type: Incident
    Duration: 42 minutes

    Affected Components: POS Elera
    Oct 10, 14:42:22 GMT+0 - Investigating - We are currently investigating an incident affecting our systems, impacting the POS Elera. Our team is actively working to identify and resolve the issue. Further updates to follow. Thank you for your patience. Oct 10, 15:24:08 GMT+0 - Resolved - The incident has been successfully resolved and is now closed.

Our systems are back to normal operation. Thank you for your understanding and support throughout this process. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 42 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 10&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:42:22&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating an incident affecting our systems, impacting the POS Elera. Our team is actively working to identify and resolve the issue. Further updates to follow. Thank you for your patience..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 10&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:24:08&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The incident has been successfully resolved and is now closed.

Our systems are back to normal operation. Thank you for your understanding and support throughout this process..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 10 Oct 2024 14:42:22 +0000</pubDate>
  <link>https://it-ops-clubs.status.pricesmart.io/incident/cm23eqwr1003y5h0zyqbefro3</link>
  <guid>https://it-ops-clubs.status.pricesmart.io/incident/cm23eqwr1003y5h0zyqbefro3</guid>
</item>

<item>
  <title>AS400 slow performance and AWS tunnels down on 2024-10-10</title>
  <description>
    Type: Incident
    Duration: 2 hours and 47 minutes

    Affected Components: 6704 - Santa Ana, 6602 - Tegucigalpa, 6305 - San Cristobal, 6102 - Canasgordas, 6805 - San Isidro, 6109 - Floridablanca, 6107 - Chia, 6307 - Escuintla, 6407 - Santa Ana, 6204 - David, 6207 - Veraguas, 8902 - Ctra. Masaya, 8701 - Kingston, 6408 - Liberia, 6110 - El Poblado, 6402 - Escazu, 6205 - Brisas, 6401-Zapote, 6105 - Salitre, 6104 - Pereira, 8003 - Mausica, 6303 - Pradera, 6202 - Via Brasil, 6403 - Heredia, 6404 - Llorente, 6203 - El Dorado, 6603 - San Pedro Sula, 6405 - Alajuela, 8101 - Virgin Islands, 8004 - San Fernando, 6801 - Los Prados, 6106 - Las Americas, 8901 - Managua, 6103 - Menga, 6304 - Fraijanes, 6306 - Aranda, 6802 - Santiago, 6301 - Mira Flores, 8702 - Portmore, 6206 - Costa Verde, 6208 - Metro Park, 7802 - Offsite Bakery, 6604 - El Sauce, 6101 - Barranquilla Norte, 8002 - Port of Spain, 6406 - Tres Rios, 6804 - Arroyo Hondo, 6108 - Usaquen, 6701 - Santa Elena, 6702 - Metro Centre, 6703 - San Miguel, 8201 - Aruba, 8501 - Barbados, Agile Server App, Agile Server Database, 8001 - Chaguanas, 6806 - Bolivar
    Oct 10, 11:51:46 GMT+0 - Investigating - We are currently investigating an incident affecting our systems, impacting the communications. Our team is actively working to identify and resolve the issue. Further updates to follow. Thank you for your patience. Oct 10, 12:09:41 GMT+0 - Identified - The issue has been identified and our team is working on resolving it. We appreciate your patience as we work towards a resolution. Further updates to follow. Thank you for your understanding. Oct 10, 13:33:16 GMT+0 - Identified - The issue has been identified, and our team is still working on resolving it. We appreciate your patience as we continue working towards a resolution. Further updates will follow. Thank you for your understanding. Oct 10, 14:15:43 GMT+0 - Monitoring - The system is stable but the situation is being actively monitored. We are closely watching for any potential impact and taking necessary measures. Further updates to follow. Thank you for your patience and understanding. Oct 10, 14:39:13 GMT+0 - Resolved - The incident has been successfully resolved and is now closed.

Brief description of the problem:

There was a service disruption affecting certain resources within the VNet, leading to connectivity issues and failures in communication between services hosted in Azure.

Actual state:

* The affected services are now operational, and network connectivity between the impacted resources has been restored.
* All related VNet configurations have been reverted to their previous, working state to resolve the immediate issue.

Root Cause:

The problem was triggered by a policy change applied to the Azure Virtual Networks (VNets). Specifically, the new policy inadvertently modified network security settings, causing unexpected connectivity restrictions. This resulted in some services being unable to communicate across subnets or with external resources. The change also affected route tables and security group rules, leading to disruptions in the internal traffic flow within the VNet.

The issue was resolved by identifying and rolling back the policy change, restoring the original VNet configurations. The Azure team is investigating the need for additional safeguards to prevent such policy impacts in the future.

Our systems are back to normal operation. Thank you for your understanding and support throughout this process. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 47 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , </p>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 10&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:51:46&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating an incident affecting our systems, impacting the communications. Our team is actively working to identify and resolve the issue. Further updates to follow. Thank you for your patience..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 10&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:09:41&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  The issue has been identified and our team is working on resolving it. We appreciate your patience as we work towards a resolution. Further updates to follow. Thank you for your understanding..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 10&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:33:16&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  The issue has been identified, and our team is still working on resolving it. We appreciate your patience as we continue working towards a resolution. Further updates will follow. Thank you for your understanding..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 10&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:15:43&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  The system is stable but the situation is being actively monitored. We are closely watching for any potential impact and taking necessary measures. Further updates to follow. Thank you for your patience and understanding..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 10&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:39:13&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The incident has been successfully resolved and is now closed.

Brief description of the problem:

There was a service disruption affecting certain resources within the VNet, leading to connectivity issues and failures in communication between services hosted in Azure.

Actual state:

* The affected services are now operational, and network connectivity between the impacted resources has been restored.
* All related VNet configurations have been reverted to their previous, working state to resolve the immediate issue.

Root Cause:

The problem was triggered by a policy change applied to the Azure Virtual Networks (VNets). Specifically, the new policy inadvertently modified network security settings, causing unexpected connectivity restrictions. This resulted in some services being unable to communicate across subnets or with external resources. The change also affected route tables and security group rules, leading to disruptions in the internal traffic flow within the VNet.

The issue was resolved by identifying and rolling back the policy change, restoring the original VNet configurations. The Azure team is investigating the need for additional safeguards to prevent such policy impacts in the future.

Our systems are back to normal operation. Thank you for your understanding and support throughout this process..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 10 Oct 2024 11:51:46 +0000</pubDate>
  <link>https://it-ops-clubs.status.pricesmart.io/incident/cm238niio001ufst0p9y4p6xa</link>
  <guid>https://it-ops-clubs.status.pricesmart.io/incident/cm238niio001ufst0p9y4p6xa</guid>
</item>

<item>
  <title>Network issue on 2024-10-08</title>
  <description>
    Type: Incident
    Duration: 1 hour and 41 minutes

    Affected Components: 6704 - Santa Ana, 6602 - Tegucigalpa, 6305 - San Cristobal, 6102 - Canasgordas, 6805 - San Isidro, 6109 - Floridablanca, 6107 - Chia, 6307 - Escuintla, 6407 - Santa Ana, 6204 - David, 6207 - Veraguas, 8902 - Ctra. Masaya, 8701 - Kingston, 6408 - Liberia, 6110 - El Poblado, 6402 - Escazu, 6205 - Brisas, 6401-Zapote, 6105 - Salitre, 6104 - Pereira, 8003 - Mausica, 6303 - Pradera, 6202 - Via Brasil, 6403 - Heredia, 6404 - Llorente, 6203 - El Dorado, 6603 - San Pedro Sula, 6405 - Alajuela, 8101 - Virgin Islands, 8004 - San Fernando, 6801 - Los Prados, 6106 - Las Americas, 8901 - Managua, 6103 - Menga, 6304 - Fraijanes, 8001 - Chaguanas, 6306 - Aranda, 6802 - Santiago, 6301 - Mira Flores, 8702 - Portmore, 6206 - Costa Verde, 6208 - Metro Park, 7802 - Offsite Bakery, 6604 - El Sauce, 6101 - Barranquilla Norte, 8002 - Port of Spain, 6406 - Tres Rios, 6804 - Arroyo Hondo, 6108 - Usaquen, 6701 - Santa Elena, 6702 - Metro Centre, 6703 - San Miguel, 8201 - Aruba, 8501 - Barbados, Agile Server App, Agile Server Database, 6806 - Bolivar
    Oct 8, 17:28:40 GMT+0 - Investigating - We are currently investigating an incident affecting our systems, impacting the network. Our team is actively working to identify and resolve the issue. Further updates to follow. Thank you for your patience. Oct 8, 18:06:08 GMT+0 - Identified - The issue has been identified and our team is working on resolving it. We appreciate your patience as we work towards a resolution. Further updates to follow. Thank you for your understanding. Oct 8, 18:31:24 GMT+0 - Monitoring - The system is stable but the situation is being actively monitored. We are closely watching for any potential impact and taking necessary measures. Further updates to follow. Thank you for your patience and understanding. Oct 8, 19:09:38 GMT+0 - Resolved - The incident has been successfully resolved and is now closed.

Brief description of the problem:

The issue involved intermittent connectivity problems between our on-premises SD-WAN infrastructure and Azure services. This resulted in degraded performance and occasional packet loss across our VPN connections.

Actual state:

The systems have been fully restored, and all related services are back to normal operation. Our network traffic is flowing as expected without any interruptions.

Root Cause:

Upon investigation, it was identified that the issue stemmed from a misconfiguration in the routing policies of the SD-WAN network, which impacted traffic between our site and Azure. Azure&#039;s support ticket was created for a review.

Our systems are back to normal operation. Thank you for your understanding and support throughout this process. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 41 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , </p>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 8&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:28:40&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating an incident affecting our systems, impacting the network. Our team is actively working to identify and resolve the issue. Further updates to follow. Thank you for your patience..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 8&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:06:08&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  The issue has been identified and our team is working on resolving it. We appreciate your patience as we work towards a resolution. Further updates to follow. Thank you for your understanding..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 8&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:31:24&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  The system is stable but the situation is being actively monitored. We are closely watching for any potential impact and taking necessary measures. Further updates to follow. Thank you for your patience and understanding..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 8&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:09:38&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The incident has been successfully resolved and is now closed.

Brief description of the problem:

The issue involved intermittent connectivity problems between our on-premises SD-WAN infrastructure and Azure services. This resulted in degraded performance and occasional packet loss across our VPN connections.

Actual state:

The systems have been fully restored, and all related services are back to normal operation. Our network traffic is flowing as expected without any interruptions.

Root Cause:

Upon investigation, it was identified that the issue stemmed from a misconfiguration in the routing policies of the SD-WAN network, which impacted traffic between our site and Azure. Azure&#039;s support ticket was created for a review.

Our systems are back to normal operation. Thank you for your understanding and support throughout this process..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 8 Oct 2024 17:28:40 +0000</pubDate>
  <link>https://it-ops-clubs.status.pricesmart.io/incident/cm20pt2e70018ivpj6lq4m6jv</link>
  <guid>https://it-ops-clubs.status.pricesmart.io/incident/cm20pt2e70018ivpj6lq4m6jv</guid>
</item>

<item>
  <title>network inttermitency affecting POS - Logistics on 2024-10-04</title>
  <description>
    Type: Incident
    Duration: 6 minutes

    Affected Components: 6704 - Santa Ana, 6602 - Tegucigalpa, 6305 - San Cristobal, 6102 - Canasgordas, 6805 - San Isidro, 6109 - Floridablanca, 6107 - Chia, 6307 - Escuintla, 6407 - Santa Ana, 6204 - David, 6207 - Veraguas, 8902 - Ctra. Masaya, 8701 - Kingston, 6408 - Liberia, 6110 - El Poblado, 6402 - Escazu, 6205 - Brisas, 6401-Zapote, 6105 - Salitre, 6104 - Pereira, 8003 - Mausica, 6303 - Pradera, 6202 - Via Brasil, 6403 - Heredia, 6404 - Llorente, 6203 - El Dorado, 6603 - San Pedro Sula, 6405 - Alajuela, 8101 - Virgin Islands, 8004 - San Fernando, 6801 - Los Prados, 6106 - Las Americas, 8901 - Managua, 6103 - Menga, 6304 - Fraijanes, 8001 - Chaguanas, 6306 - Aranda, 6802 - Santiago, 6301 - Mira Flores, 8702 - Portmore, 6206 - Costa Verde, 6208 - Metro Park, 7802 - Offsite Bakery, 6604 - El Sauce, 6101 - Barranquilla Norte, 8002 - Port of Spain, 6406 - Tres Rios, 6804 - Arroyo Hondo, 6108 - Usaquen, 6701 - Santa Elena, 6702 - Metro Centre, 6703 - San Miguel, 8201 - Aruba, 8501 - Barbados, Agile Server App, Agile Server Database, 6806 - Bolivar
    Oct 4, 15:20:20 GMT+0 - Investigating - We are currently investigating an incident affecting our systems, impacting the POS communication. Our team is actively working to identify and resolve the issue. Further updates to follow. Thank you for your patience. Oct 4, 15:24:23 GMT+0 - Monitoring - The system is stable but the situation is being actively monitored. We are closely watching for any potential impact and taking necessary measures. Further updates to follow. Thank you for your patience and understanding. Oct 4, 15:25:55 GMT+0 - Resolved - The incident has been successfully resolved and is now closed.

Our systems are back to normal operation. Thank you for your understanding and support throughout this process. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , </p>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:20:20&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating an incident affecting our systems, impacting the POS communication. Our team is actively working to identify and resolve the issue. Further updates to follow. Thank you for your patience..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:24:23&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  The system is stable but the situation is being actively monitored. We are closely watching for any potential impact and taking necessary measures. Further updates to follow. Thank you for your patience and understanding..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:25:55&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The incident has been successfully resolved and is now closed.

Our systems are back to normal operation. Thank you for your understanding and support throughout this process..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 4 Oct 2024 15:20:20 +0000</pubDate>
  <link>https://it-ops-clubs.status.pricesmart.io/incident/cm1uvgmey000whkdsync8mbka</link>
  <guid>https://it-ops-clubs.status.pricesmart.io/incident/cm1uvgmey000whkdsync8mbka</guid>
</item>

<item>
  <title>6207 communication issue on 2024-10-02</title>
  <description>
    Type: Incident
    Duration: 47 minutes

    Affected Components: 6207 - Veraguas
    Oct 2, 15:55:40 GMT+0 - Investigating - We are currently investigating an incident affecting our systems, impacting the communication in POS 6702\. Our team is actively working to identify and resolve the issue. Further updates to follow. Thank you for your patience. Oct 2, 15:59:35 GMT+0 - Identified - The issue has been identified and our team is working on resolving it. We appreciate your patience as we work towards a resolution. Further updates to follow. Thank you for your understanding. Oct 2, 16:00:17 GMT+0 - Identified - The issue has been identified and our team is working on resolving it. We appreciate your patience as we work towards a resolution. Further updates to follow. Thank you for your understanding. Oct 2, 16:43:02 GMT+0 - Resolved - The incident has been successfully resolved and is now closed.

Our systems are back to normal operation. Thank you for your understanding and support throughout this process. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 47 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:55:40&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating an incident affecting our systems, impacting the communication in POS 6702\. Our team is actively working to identify and resolve the issue. Further updates to follow. Thank you for your patience..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:59:35&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  The issue has been identified and our team is working on resolving it. We appreciate your patience as we work towards a resolution. Further updates to follow. Thank you for your understanding..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:00:17&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  The issue has been identified and our team is working on resolving it. We appreciate your patience as we work towards a resolution. Further updates to follow. Thank you for your understanding..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:43:02&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The incident has been successfully resolved and is now closed.

Our systems are back to normal operation. Thank you for your understanding and support throughout this process..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 2 Oct 2024 15:55:40 +0000</pubDate>
  <link>https://it-ops-clubs.status.pricesmart.io/incident/cm1s1ucmy000g502gty1oi0u8</link>
  <guid>https://it-ops-clubs.status.pricesmart.io/incident/cm1s1ucmy000g502gty1oi0u8</guid>
</item>

<item>
  <title>Major outage - POS - 2024-09-23</title>
  <description>
    Type: Incident
    Duration: 4 hours and 52 minutes

    Affected Components: 6704 - Santa Ana, 6602 - Tegucigalpa, 6305 - San Cristobal, 6102 - Canasgordas, 6805 - San Isidro, 6109 - Floridablanca, 6107 - Chia, 6307 - Escuintla, 6407 - Santa Ana, 6204 - David, 6207 - Veraguas, 8902 - Ctra. Masaya, 8701 - Kingston, 6408 - Liberia, 6110 - El Poblado, 6402 - Escazu, 6205 - Brisas, 6401-Zapote, 6105 - Salitre, 6104 - Pereira, 8003 - Mausica, 6303 - Pradera, 6202 - Via Brasil, 6403 - Heredia, 6404 - Llorente, 6203 - El Dorado, 6603 - San Pedro Sula, 6405 - Alajuela, 8101 - Virgin Islands, 8004 - San Fernando, 6801 - Los Prados, 6106 - Las Americas, 8901 - Managua, 6103 - Menga, 6304 - Fraijanes, 8001 - Chaguanas, 6306 - Aranda, 6802 - Santiago, 6301 - Mira Flores, 8702 - Portmore, 6206 - Costa Verde, 6208 - Metro Park, 7802 - Offsite Bakery, 6604 - El Sauce, 6101 - Barranquilla Norte, 8002 - Port of Spain, 6406 - Tres Rios, 6804 - Arroyo Hondo, 6108 - Usaquen, 6701 - Santa Elena, 6702 - Metro Centre, 6703 - San Miguel, 8201 - Aruba, 8501 - Barbados, 6806 - Bolivar
    Sep 23, 15:52:47 GMT+0 - Identified - The issue has been identified and our team is working on resolving it. We appreciate your patience as we work towards a resolution. Further updates to follow. Thank you for your understanding. Sep 23, 12:10:57 GMT+0 - Investigating - We are currently investigating an incident affecting our systems, impacting the login and order process in the site. Our team is actively working to identify and resolve the issue. Further updates to follow. Thank you for your patience. Sep 23, 12:22:11 GMT+0 - Identified - The issue has been identified and our team is working on resolving it. We appreciate your patience as we work towards a resolution. Further updates to follow. Thank you for your understanding. Sep 23, 12:34:30 GMT+0 - Monitoring - The system is stable but the situation is being actively monitored. We are closely watching for any potential impact and taking necessary measures. Further updates to follow. Thank you for your patience and understanding. Sep 23, 14:29:09 GMT+0 - Resolved - The incident has been successfully resolved and is now closed.

Brief description of the problem:

An outage was experienced due to AWS tunnels going down, leading to loss of connectivity between our on-premise infrastructure and the cloud resources hosted on AWS. This impacted the availability and functionality of applications dependent on this connection.

Actual state:

The AWS tunnels were restored, and connectivity has been re-established.

Root Cause:

The incident was caused by a disruption in AWS Site-to-Site VPN tunnels, likely due to either network misconfigurations, a temporary issue with AWS networking services, or a failure in VPN endpoints. Further analysis revealed that the automatic failover mechanism did not engage as expected, prolonging the downtime.

Our systems are back to normal operation. Thank you for your understanding and support throughout this process. Sep 23, 16:39:54 GMT+0 - Monitoring - The system is stable but the situation is being actively monitored. We are closely watching for any potential impact and taking necessary measures. Further updates to follow. Thank you for your patience and understanding. Sep 23, 17:03:14 GMT+0 - Resolved - The incident has been successfully resolved and is now closed.

Brief description of the problem:

An outage was experienced due to AWS tunnels going down, leading to loss of connectivity between our on-premise infrastructure and the cloud resources hosted on AWS. This impacted the availability and functionality of applications dependent on this connection.

Actual state:

The AWS tunnels were restored, and connectivity has been re-established.

Root Cause:

The incident was caused by a disruption in AWS Site-to-Site VPN tunnels, likely due to either network misconfigurations, a temporary issue with AWS networking services, or a failure in VPN endpoints. Further analysis revealed that the automatic failover mechanism did not engage as expected, prolonging the downtime.

Our systems are back to normal operation. Thank you for your understanding and support throughout this process. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 hours and 52 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , </p>
    &lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:52:47&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  The issue has been identified and our team is working on resolving it. We appreciate your patience as we work towards a resolution. Further updates to follow. Thank you for your understanding..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:10:57&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating an incident affecting our systems, impacting the login and order process in the site. Our team is actively working to identify and resolve the issue. Further updates to follow. Thank you for your patience..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:22:11&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  The issue has been identified and our team is working on resolving it. We appreciate your patience as we work towards a resolution. Further updates to follow. Thank you for your understanding..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:34:30&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  The system is stable but the situation is being actively monitored. We are closely watching for any potential impact and taking necessary measures. Further updates to follow. Thank you for your patience and understanding..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:29:09&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The incident has been successfully resolved and is now closed.

Brief description of the problem:

An outage was experienced due to AWS tunnels going down, leading to loss of connectivity between our on-premise infrastructure and the cloud resources hosted on AWS. This impacted the availability and functionality of applications dependent on this connection.

Actual state:

The AWS tunnels were restored, and connectivity has been re-established.

Root Cause:

The incident was caused by a disruption in AWS Site-to-Site VPN tunnels, likely due to either network misconfigurations, a temporary issue with AWS networking services, or a failure in VPN endpoints. Further analysis revealed that the automatic failover mechanism did not engage as expected, prolonging the downtime.

Our systems are back to normal operation. Thank you for your understanding and support throughout this process..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:39:54&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  The system is stable but the situation is being actively monitored. We are closely watching for any potential impact and taking necessary measures. Further updates to follow. Thank you for your patience and understanding..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:03:14&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The incident has been successfully resolved and is now closed.

Brief description of the problem:

An outage was experienced due to AWS tunnels going down, leading to loss of connectivity between our on-premise infrastructure and the cloud resources hosted on AWS. This impacted the availability and functionality of applications dependent on this connection.

Actual state:

The AWS tunnels were restored, and connectivity has been re-established.

Root Cause:

The incident was caused by a disruption in AWS Site-to-Site VPN tunnels, likely due to either network misconfigurations, a temporary issue with AWS networking services, or a failure in VPN endpoints. Further analysis revealed that the automatic failover mechanism did not engage as expected, prolonging the downtime.

Our systems are back to normal operation. Thank you for your understanding and support throughout this process..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 23 Sep 2024 12:10:57 +0000</pubDate>
  <link>https://it-ops-clubs.status.pricesmart.io/incident/cm1eyup6j000ly061he94x7em</link>
  <guid>https://it-ops-clubs.status.pricesmart.io/incident/cm1eyup6j000ly061he94x7em</guid>
</item>

<item>
  <title>Multiples Apis &amp; devices affected due network issue on 2024-09-10 #886</title>
  <description>
    Type: Incident
    Duration: 20 minutes

    Affected Components: 6704 - Santa Ana, 6602 - Tegucigalpa, 6305 - San Cristobal, 6102 - Canasgordas, 6805 - San Isidro, 6109 - Floridablanca, 6107 - Chia, 6307 - Escuintla, 6407 - Santa Ana, 6204 - David, 6207 - Veraguas, 8902 - Ctra. Masaya, 8701 - Kingston, 6408 - Liberia, 6110 - El Poblado, 6402 - Escazu, 6806 - Bolivar, 6205 - Brisas, 6401-Zapote, 6105 - Salitre, 6104 - Pereira, 8003 - Mausica, 6303 - Pradera, 6202 - Via Brasil, 6403 - Heredia, 6404 - Llorente, 6203 - El Dorado, 6603 - San Pedro Sula, 6405 - Alajuela, 8101 - Virgin Islands, 8004 - San Fernando, 6801 - Los Prados, 6106 - Las Americas, 8901 - Managua, 6103 - Menga, 6304 - Fraijanes, 8001 - Chaguanas, 6306 - Aranda, 6802 - Santiago, 6301 - Mira Flores, 8702 - Portmore, 6206 - Costa Verde, 6208 - Metro Park, 7802 - Offsite Bakery, 6604 - El Sauce, 6101 - Barranquilla Norte, 8002 - Port of Spain, 6406 - Tres Rios, 6804 - Arroyo Hondo, 6108 - Usaquen, 6701 - Santa Elena, 6702 - Metro Centre, 6703 - San Miguel, 8201 - Aruba, 8501 - Barbados, Agile Server App, Agile Server Database
    Sep 10, 19:22:09 GMT+0 - Investigating - We are currently investigating an incident affecting our systems. Our team is actively working to identify and resolve the issue. Further updates to follow. Thank you for your patience. Sep 10, 19:27:30 GMT+0 - Monitoring - The system is stable but the situation is being actively monitored. We are closely watching for any potential impact and taking necessary measures. Further updates to follow. Thank you for your patience and understanding. Sep 10, 19:42:11 GMT+0 - Resolved - The incident has been successfully resolved and is now closed.

Brief description of the problem:

We experienced an issue that affected system connectivity, causing disruptions in communication between critical services. This resulted in delays and failures in processing requests.

Actual state:

The issue has been identified and resolved. Connectivity between services has been restored, and systems are functioning as expected.

Root Cause:

The root cause appears to be related to a failure in an AWS tunnel, which caused intermittent network interruptions. This tunnel is responsible for securely routing traffic between services, and its malfunction led to the communication breakdown. Further investigation is ongoing to confirm the exact failure point within the tunnel configuration.

Our systems are back to normal operation. Thank you for your understanding and support throughout this process. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 20 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , </p>
    &lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 10&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:22:09&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating an incident affecting our systems. Our team is actively working to identify and resolve the issue. Further updates to follow. Thank you for your patience..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 10&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:27:30&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  The system is stable but the situation is being actively monitored. We are closely watching for any potential impact and taking necessary measures. Further updates to follow. Thank you for your patience and understanding..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 10&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:42:11&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The incident has been successfully resolved and is now closed.

Brief description of the problem:

We experienced an issue that affected system connectivity, causing disruptions in communication between critical services. This resulted in delays and failures in processing requests.

Actual state:

The issue has been identified and resolved. Connectivity between services has been restored, and systems are functioning as expected.

Root Cause:

The root cause appears to be related to a failure in an AWS tunnel, which caused intermittent network interruptions. This tunnel is responsible for securely routing traffic between services, and its malfunction led to the communication breakdown. Further investigation is ongoing to confirm the exact failure point within the tunnel configuration.

Our systems are back to normal operation. Thank you for your understanding and support throughout this process..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 10 Sep 2024 19:22:09 +0000</pubDate>
  <link>https://it-ops-clubs.status.pricesmart.io/incident/cm0wtj5cz0001pg86is4rmw05</link>
  <guid>https://it-ops-clubs.status.pricesmart.io/incident/cm0wtj5cz0001pg86is4rmw05</guid>
</item>

<item>
  <title>POS Terminals - Guatemala - Communication issue. - 2024-08-09</title>
  <description>
    Type: Incident
    Duration: 4 hours and 23 minutes

    Affected Components: 6305 - San Cristobal, 6307 - Escuintla, 6303 - Pradera, 6304 - Fraijanes, 6306 - Aranda, 6301 - Mira Flores
    Aug 9, 17:17:36 GMT+0 - Investigating - We are currently investigating an incident affecting our systems, impacting the communication between the cash registers and the Guatefacturas team. Our team is actively working to identify and resolve the issue. Further updates to follow. Thank you for your patience. Aug 9, 18:50:40 GMT+0 - Identified - The issue has been identified and our team is working on resolving it. We appreciate your patience as we work towards a resolution. Further updates to follow. Thank you for your understanding. Aug 9, 20:43:58 GMT+0 - Monitoring - We inform that communication has been restored and the problem mitigated, with the exception of club 6304- Fraijanes, the technical team is working for its prompt resolution.  
  
Further updates to follow. Thank you for your understanding. Aug 9, 21:40:50 GMT+0 - Resolved - The incident has been successfully resolved and is now closed.

Brief Description of the Problem:

Communication issues between the cash registers and the Guatefacturas team, which is causing the transactions to show as contingency.

Current State:

The impact of the incident has been mitigated. The Networking team has resolved the issue.

Root Cause:

An internal job in progress caused some network rules within the firewall to be deleted, it was necessary to recreate the rules to establish correct communication.

Thank you for your understanding and support throughout this process. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 hours and 23 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 9&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:17:36&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating an incident affecting our systems, impacting the communication between the cash registers and the Guatefacturas team. Our team is actively working to identify and resolve the issue. Further updates to follow. Thank you for your patience..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 9&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:50:40&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  The issue has been identified and our team is working on resolving it. We appreciate your patience as we work towards a resolution. Further updates to follow. Thank you for your understanding..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 9&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:43:58&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We inform that communication has been restored and the problem mitigated, with the exception of club 6304- Fraijanes, the technical team is working for its prompt resolution.  
  
Further updates to follow. Thank you for your understanding..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 9&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:40:50&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The incident has been successfully resolved and is now closed.

Brief Description of the Problem:

Communication issues between the cash registers and the Guatefacturas team, which is causing the transactions to show as contingency.

Current State:

The impact of the incident has been mitigated. The Networking team has resolved the issue.

Root Cause:

An internal job in progress caused some network rules within the firewall to be deleted, it was necessary to recreate the rules to establish correct communication.

Thank you for your understanding and support throughout this process..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 9 Aug 2024 17:17:36 +0000</pubDate>
  <link>https://it-ops-clubs.status.pricesmart.io/incident/clzmyzpao75015irn71dbbml0g</link>
  <guid>https://it-ops-clubs.status.pricesmart.io/incident/clzmyzpao75015irn71dbbml0g</guid>
</item>

<item>
  <title>Communication issue - POS - 2024-07-29</title>
  <description>
    Type: Incident
    Duration: 2 hours and 56 minutes

    Affected Components: Agile Server App, Agile Server Database
    Jul 29, 15:53:10 GMT+0 - Identified - We are currently experiencing a network issue that is affecting multiple services and systems across our infrastructure. Our team is actively investigating the issue and working towards a resolution as quickly as possible. Jul 29, 15:23:49 GMT+0 - Investigating - We inform you that intermittency is being seen in the services impacting all POS clubs, the technical team is working to identify and resolve it as quickly as possible. Jul 29, 17:02:05 GMT+0 - Monitoring - The systems have returned to normal. However, we remain actively monitoring for any potential impact and will take necessary actions if needed.

Further updates to follow. Thank you for your understanding. Jul 29, 18:19:27 GMT+0 - Resolved - The incident has been successfully resolved and is now closed.

Brief description of the problem:  
A Network issue affecting multiple services and systems across our infrastructure

Actual state:  
The immediate impact of the incident has been mitigated. Traffic has returned to normal levels

Root Cause:  
An internal flow at the application level was causing countless traffic that caused a bottleneck in the link available for consumption by the applications.

Our systems are back to normal operation. Thank you for your understanding and support throughout this process. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 56 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 29&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:53:10&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are currently experiencing a network issue that is affecting multiple services and systems across our infrastructure. Our team is actively investigating the issue and working towards a resolution as quickly as possible..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 29&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:23:49&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We inform you that intermittency is being seen in the services impacting all POS clubs, the technical team is working to identify and resolve it as quickly as possible..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 29&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:02:05&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  The systems have returned to normal. However, we remain actively monitoring for any potential impact and will take necessary actions if needed.

Further updates to follow. Thank you for your understanding..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 29&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:19:27&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The incident has been successfully resolved and is now closed.

Brief description of the problem:  
A Network issue affecting multiple services and systems across our infrastructure

Actual state:  
The immediate impact of the incident has been mitigated. Traffic has returned to normal levels

Root Cause:  
An internal flow at the application level was causing countless traffic that caused a bottleneck in the link available for consumption by the applications.

Our systems are back to normal operation. Thank you for your understanding and support throughout this process..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 29 Jul 2024 15:23:49 +0000</pubDate>
  <link>https://it-ops-clubs.status.pricesmart.io/incident/clz7530lk48888gsn1ayzjb31r</link>
  <guid>https://it-ops-clubs.status.pricesmart.io/incident/clz7530lk48888gsn1ayzjb31r</guid>
</item>

<item>
  <title>Production Agile server down on 2024-07-23 #838</title>
  <description>
    Type: Incident
    

    Affected Components: Agile Server App, Agile Server Database
    Jul 23, 21:51:36 GMT+0 - Resolved - The incident has been successfully resolved and is now closed.

Brief description of the problem:  
A network infrastructure problem is being addressed that has impacted the Agile server in the Texas data center

Actual state:

Agile is up and functional.

Root Cause:

There was an issue with the Freshe provider while configuring for DR preparation.

Our systems are back to normal operation. Thank you for your understanding and support throughout this process. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:51:36&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The incident has been successfully resolved and is now closed.

Brief description of the problem:  
A network infrastructure problem is being addressed that has impacted the Agile server in the Texas data center

Actual state:

Agile is up and functional.

Root Cause:

There was an issue with the Freshe provider while configuring for DR preparation.

Our systems are back to normal operation. Thank you for your understanding and support throughout this process..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 23 Jul 2024 21:51:36 +0000</pubDate>
  <link>https://it-ops-clubs.status.pricesmart.io/incident/clyyyal91523715hjn3ffl1913l</link>
  <guid>https://it-ops-clubs.status.pricesmart.io/incident/clyyyal91523715hjn3ffl1913l</guid>
</item>

<item>
  <title>ISP problems Barbados on 2024-06-28 #805</title>
  <description>
    Type: Incident
    Duration: 2 days, 22 hours and 22 minutes

    Affected Components: 8501 - Barbados
    Jun 28, 22:13:23 GMT+0 - Investigating - We are currently investigating an incident affecting our systems, impacting the club 8501\. Our team is actively working to identify and resolve the issue. Further updates to follow. Thank you for your patience. Jul 1, 14:33:36 GMT+0 - Identified - The issue has been identified and our team is working on resolving it. We appreciate your patience as we work towards a resolution. Further updates to follow. Thank you for your understanding. Jul 1, 20:35:32 GMT+0 - Resolved - The incident has been successfully resolved and is now closed. Our systems are back to normal operation. Thank you for your understanding and support throughout this process. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 days, 22 hours and 22 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 28&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:13:23&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating an incident affecting our systems, impacting the club 8501\. Our team is actively working to identify and resolve the issue. Further updates to follow. Thank you for your patience..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 1&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:33:36&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  The issue has been identified and our team is working on resolving it. We appreciate your patience as we work towards a resolution. Further updates to follow. Thank you for your understanding..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 1&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:35:32&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The incident has been successfully resolved and is now closed. Our systems are back to normal operation. Thank you for your understanding and support throughout this process..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 28 Jun 2024 22:13:23 +0000</pubDate>
  <link>https://it-ops-clubs.status.pricesmart.io/incident/clxz92bdj141950b4olrm5mj6ss</link>
  <guid>https://it-ops-clubs.status.pricesmart.io/incident/clxz92bdj141950b4olrm5mj6ss</guid>
</item>

<item>
  <title>6806 Host Disconnected on 2024-06-06 #777</title>
  <description>
    Type: Incident
    Duration: 15 hours and 55 minutes

    Affected Components: 6806 - Bolivar
    Jun 6, 22:57:23 GMT+0 - Investigating - We are currently investigating an incident affecting our systems, impacting the 6806 response. Our team is actively working to identify and resolve the issue. Further updates to follow. Thank you for your patience. Jun 7, 12:12:09 GMT+0 - Identified - The issue has been identified and our team is working on resolving it. We appreciate your patience as we work towards a resolution. Further updates to follow. Thank you for your understanding. Jun 7, 14:52:05 GMT+0 - Resolved - The incident has been successfully resolved and is now closed. Our systems are back to normal operation. Thank you for your understanding and support throughout this process. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 15 hours and 55 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:57:23&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating an incident affecting our systems, impacting the 6806 response. Our team is actively working to identify and resolve the issue. Further updates to follow. Thank you for your patience..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 7&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:12:09&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  The issue has been identified and our team is working on resolving it. We appreciate your patience as we work towards a resolution. Further updates to follow. Thank you for your understanding..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 7&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:52:05&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The incident has been successfully resolved and is now closed. Our systems are back to normal operation. Thank you for your understanding and support throughout this process..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 6 Jun 2024 22:57:23 +0000</pubDate>
  <link>https://it-ops-clubs.status.pricesmart.io/incident/clx3uy6510031byois8cs02z3</link>
  <guid>https://it-ops-clubs.status.pricesmart.io/incident/clx3uy6510031byois8cs02z3</guid>
</item>

  </channel>
  </rss>