Is Rebuy Down Right Now? Check if there is a current outage ongoing.

Rebuy services are currently degraded due to an incident with Google Cloud Services that we are reliant on to function nominally. Our teams are monitoring the situation closely and will begin testing and validating Rebuy services as soon as the Google Cloud Services interruption is resolved.

The issue involving Smart Search loading has been fully resolved, and everything is functioning as expected.An update included an improperly formatted file, which conflicted with smart search. The file was reformatted to correct the issue.

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

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

We are investigating the issue

We are currently investigating the issue.

The issue involving Smart Search loading has been fully resolved, and everything is functioning as expected.An update included an improperly formatted file, which conflicted with smart search. The file was reformatted to correct the issue.

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

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

We are investigating the issue

We are currently investigating the issue.

**Issue:** Some Shopify merchants experienced issues with widgets not displaying correctly in their checkouts. This was linked to a new feature we recently introduced within the checkout extension framework. The disruption was traced back to a logic issue that caused valid widget IDs to be misinterpreted as invalid, impacting the visibility of the widget during checkout. ‌ **Actions Taken:** * **Rollback to Stable Version:** As soon as the issue was confirmed, we rolled back to the last known-good version of the extension to limit further impact. * **Root Cause Fix:** Once identified, the root cause was addressed with a hot-fix to ensure valid widget IDs were recognized appropriately.

This incident has been resolved.

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

We are continuing to investigate this issue.

We are currently seeing issues with checkout widgets and content blocks. The team is actively engaged.

The issues have been resolved following the recent changes applied. We will conduct a post-mortem analysis and share the findings.

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

We are currently investigating reports of login and navigation difficulties within the Rebuy administrative portal. These issues appear to be affecting user access and navigation, but all on-site features, such as widgets, Smart Cart, Smart Search, and other core functionalities, remain fully operational. Our team is working to resolve the issue as quickly as possible, and we will provide further updates soon.

**Issue:** Customers experienced degraded service due to issues with product images, links, and webhooks, impacting both the admin panel and certain on-site features such as widgets and Smart Cart. The problem was identified after a scheduled webhook health check triggered which led to processing issues. **Root Cause:** The issue stemmed from the update to our APIs to align with Shopify's required version, which included changes to webhook handling and product/variant data formats. After the update, malformed data started to appear during the webhook health check. This caused increased processing load on Bigtable, leading to service degradation across other systems. The malformed data also caused errors in the Smart Cart service and issues with product images and links in the admin panel and widgets. The data corruption was traced to conflicts between new and old webhooks attempting to process similar items at the same time. **Actions Taken:** * **Bigtable Load Reduction:** Immediate actions were taken to reduce the load on Bigtable, including manual resource updates, which helped stabilize the system temporarily. * **Smart Cart Hotfix:** The Smart Cart team released hotfixes to handle the malformed data, resolving the errors in the Smart Cart service. * **Workaround for Inventory Webhooks:** A temporary solution was implemented by ignoring webhooks related to inventory levels to prevent further processing of malformed data. * **Data Resync:** We initiated the process of resyncing all affected products to remove the malformed data and prevent further issues. **Next Steps:** We are currently working on fully resolving the webhook issue related to product inventory levels. This will allow us to rollback the workaround for inventory webhooks currently in place and help to prevent similar issues from occurring in the future. **Update:** All related tasks to the post mortem have been completed and confirmed successful.

The issue has been resolved. Our team is preparing a formal RCA and will post it once complete.

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

The issue has been identified, and we are actively deploying a fix.

Product images in the widgets are still exhibiting inconsistent behavior, but the carts and checkout functionality continue to be working properly. Our team is working on identifying the root cause.

Additional improvements are being observed; however, sporadic issues persist across some stores, primarily related to product synchronization. Our team is continuing to investigate the situation.

We are continuing to see improvements and are implementing an additional change to further alleviate the issue while we continue to investigate root cause.

We're beginning to see some errors resolving and signs of improvement, but the issue is not yet fully resolved. Our team continues to actively troubleshoot and assess next steps to fully address the underlying problem.

A change is being implemented to help alleviate the issue.

We are continuing to investigate this issue.

We’re currently investigating multiple reports of sync issues that are intermittently affecting reporting features, on-site widgets, and the smart cart. This issue appears to be sporadic and does not impact all clients. Our engineering team is actively working to identify and resolve the problem. We’ll provide updates as we learn more.

**Issue:** Customers experienced 503 Service Unavailable errors, impacting On-site functionality. The issue was identified during routine alert monitoring and in response to reports of degraded service. **Root Cause:** The issue stemmed from the Ingress configuration not being properly applied after an update to the NGINX controller. Specifically, the upgrade to NGINX version 1.12.1 as part of a critical security vulnerability update led to a misapplication of the configuration. The security evaluation process on the configuration snippets caused delays in loading, resulting in traffic being directed to default configurations, which led to service disruptions. **Actions Taken:** * **Stage Environment Rollback:** To resolve the issue, the rollback plan was initiated, downgrading from NGINX version 1.12.1 to 1.12.0 in the staging environment. While this did not immediately restore full functionality, it was a key first step in addressing the issue. * **Configuration Investigation and Fix:** Further investigation revealed that the Ingress configurations were not properly loaded due to the security evaluation process and an additional contributing factor. Once identified, configuration changes were made to resolve the snippet evaluation issue. The controller configurations were purged and redeployed, correcting the “default” routing behavior and restoring service. * **Production Environment Fix:** This same resolution was applied to the production environment \([Rebuyengine.com](http://Rebuyengine.com)\), which was fully restored to normal operation. **Next Steps:** All necessary actions to address the vulnerability have been completed, and no further steps are required at this time. Moving forward, we’ve enhanced our testing process to ensure that if this error is encountered, we can take appropriate actions prior to any impact to the Rebuy services.

The issue has been resolved. Our team will prepare a formal Root Cause Analysis and post it on the status page incident. Thank you for your patience throughout this process.

We are continuing to monitor for any further issues.

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

A fix has been implemented, and we are beginning to see a decrease in errors. More updates to follow.

We are continuing to work on resolving the issue. Thank you for your patience as we address this.

We have identified a potential root cause of the issue and are taking the necessary actions to resolve it.

We are currently experiencing a high volume of 503 errors, which is impacting service availability. Our team is actively investigating and working to resolve the issue as quickly as possible. Thank you for your patience.

We recently made an update to our infrastructure to improve efficiency and performance. Following the release, some merchants experienced issues with Widgets and Post Purchase Offers due to CORS-related errors. Our team quickly identified the cause and implemented the necessary changes to resolve these issues. To prevent similar occurrences in the future, we’ve made improvements to our testing processes to catch the specific errors that were seen during this maintenance. We appreciate your patience and understanding as we continue to optimize our systems. If you have any questions or need assistance, our support team is here to help.

The issue has been fully resolved, and the fix has been implemented successfully. We are now seeing the expected behavior. The team will continue to monitor the situation to ensure everything remains stable. Additionally, we will investigate the root cause to prevent similar issues in the future. Please reach out if any further issues arise.

The fix has been successfully implemented, and we're seeing positive results. The team is continuing to monitor the situation.

The issue has been identified, and the team is currently implementing a fix.

In some cases, the post-purchase offer (PPO) doesn’t appear, and users are redirected straight to the Thank You page. In other instances, the PPO does render, but users can't add items due to an error, though they can still decline the offer(s) and proceed to the Thank You page as expected. This issue isn't occurring on all sites, but our team has identified some errors and is actively working on a fix.

We recently made an update to our infrastructure to improve efficiency and performance. Following the release, some merchants experienced issues with Widgets and Post Purchase Offers due to CORS-related errors. Our team quickly identified the cause and implemented the necessary changes to resolve these issues. To prevent similar occurrences in the future, we’ve made improvements to our testing processes to catch the specific errors that were seen during this maintenance. We appreciate your patience and understanding as we continue to optimize our systems. If you have any questions or need assistance, our support team is here to help.

The issue has been fully resolved, and all systems are stable. Testing has confirmed functionality, and we will be conducting a post-mortem review to analyze the root cause and identify any improvements for the future. Thank you for your patience, and we appreciate your support. Please reach out if you experience any further issues.

The issue appears to be resolved after the implemented fix. We are actively monitoring the situation to ensure stability and will provide updates as needed.

We've identified the issue and implemented a fix. Widgets should now begin loading properly.

We're aware of an issue causing widgets to not load on the site and are actively working to resolve it. Thank you for your patience.

**What Happened** During a migration a configuration setting was unintentionally missed. This setting controlled rate limits for one of our key services, causing errors that disrupted functionality. ‌ **What We Did to Resolve It** After identifying the root cause, we implemented a temporary fix by adjusting the configuration to restore functionality. We also worked to port the missing configuration to V2 to prevent further disruptions. ‌ #### **Next Steps** We’ve now updated our processes to ensure all necessary configurations are accounted for in future migrations. This includes adding safeguards and testing mechanisms to catch similar issues before they impact functionality.

The issue with Smart Search loading has been fully resolved, and everything is functioning as expected. We will conduct a root cause analysis and take appropriate steps to prevent similar occurrences in the future. Thank you for your patience.

The fix implemented for the intermittent Smart Search loading issue continues to show positive results. We are monitoring the situation closely and can confirm that the issue remains resolved at this time.

A fix has been implemented to address the intermittent issue with Smart Search loading on-site and in admin settings. We are seeing positive results, and continuing to monitor.

We are currently investigating an intermittent issue affecting the loading of Smart Search on-site and within admin settings for some users. Our team is working to identify the root cause and resolve this as quickly as possible. Thank you for your patience.

When attempting to add an item to the cart, the cart remained empty, and the Smart Cart does not load upon refreshing the page. The issue has since been resolved and our teams are investigating root cause.

#### **What Happened** A high-demand process coincided with a scheduled daily job, leading to excessive resource usage in our database. This caused an overload, which resulted in an interruption of the **SmartCartV2 service**. ‌ **Initial Actions to Resolve the Outage** We adjusted the memory allocation for operations by increasing it from the default value. This change was applied dynamically without needing a full MySQL restart, minimizing disruption. ‌ #### **What We’re Doing Going Forward** 1. **Improved Resource Management:** * We’ve restructured how **SmartCartV2** data is processed to prevent resource conflicts between different tasks, such as the one that occurred in this instance. 2. **Update System Logic:** * Our applications will be updated to work seamlessly with this new data process, ensuring smooth and efficient performance with the new model.

The issue has been resolved, and our engineering team will conduct a root cause analysis. We will provide an update in this outage with the post-mortem once it is complete.

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

We are currently receiving reports that Smart Cart v2 is experiencing intermittent loading issues for some customers. Legacy carts continue to function as expected, while v2 carts have temporarily reverted to the native cart. Our team is actively investigating the situation. Thank you for your patience.

We are now observing normal utilization levels with no unexpected spikes. The system is performing well, and we’re confident that things are stable. Our team will continue to monitor closely for any potential issues.

The system remains stable, and we are seeing consistent performance. Our teams will continue to closely monitor the situation to address any potential issues promptly.

We are seeing continued stability across the board and are closely monitoring the situation to take proactive measures and prevent a recurrence of the latency experienced earlier today. We will continue to share updates as they become available.

We are continuing to see improving latency across the board. However, we are currently running behind on reporting analytics and Klaviyo events. Our teams are actively addressing these delays and working to catch up as quickly as possible.

We’re seeing latency begin to level out and performance improving. Our teams are continuing to monitor the situation closely and actively work on ensuring everything returns to optimal performance.

We are aware of reports from some customers experiencing delays with Rebuy loading and are actively working on it.

**Summary:** An unexpected issue caused a cache-clearing function to trigger unintentionally, leading to an overload that ultimately locked a database. Customers experienced intermittent issues, though some were unaffected, others saw various symptoms. To address this, we disabled key functions suspected to be the cause and implemented a hotfix to prevent further database locks. Once these measures were implemented and services were restarted, the issue was fully resolved. ‌ **Next Steps:** As a preventative measure, we will conduct a thorough code review of the cache-clearing function to identify and address any vulnerabilities that could lead to unintended triggers.

The issue has been resolved. We'll be conducting a thorough review and will share a post-mortem with insights on what occurred and the steps we're taking to prevent it in the future. Thank you for your patience!

A fix has been published for Smart Cart and the issue appears resolved. We are continuing to monitor.

A fix has been implemented, and we’re seeing resolution across most features. Our team is still working on Smart Cart and continues to test and monitor to ensure stability for all other features. Thank you for your patience!

Restarts and remediation efforts are ongoing as we work toward full resolution. Thank you for your patience.

The additional changes have been released, and we are restarting services to ensure they take effect.

We're implementing additional measures to expedite the resolution for the impacted sites.

We're seeing intermittent success with Rebuy loading, and our team is actively working on a full resolution. Thank you for your patience.

Issues are beginning to resolve for some customers, and the list of restored functionality continues to grow. We're actively working to complete the fix for all users. Thank you for your patience.

We are continuing to work on a fix for this issue.

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

We're experiencing an unexpected issue causing Rebuy to be temporarily unavailable for some stores. Our team is working to restore full functionality as quickly as possible. We apologize for the inconvenience and appreciate your patience. Please check back soon for updates, and thank you for being a valued Rebuy user.

**Incident Overview:** An issue occurred due to a high-data processing job, leading to performance impacts. The job has been temporarily paused to prevent further issues while a fix is implemented. **Next Steps:** We'll be enhancing the processing flow to improve stability, testing the fix in a controlled environment. Once confirmed, the job will resume with close monitoring to ensure resolution.

The issue has been resolved, and Rebuy is fully operational again. We’ll be conducting a thorough review and will provide a post-mortem to share insights on what happened and how we’re preventing it in the future. Thank you for your patience!

We are continuing to monitor for any further issues.

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

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

]We are continuing to investigate the issue to understand the cause and ensure a full resolution.

We are continuing to investigate this issue.

We’re currently experiencing an unexpected issue causing Rebuy to render unavailable. Our team is actively working to restore full functionality as quickly as possible. We apologize for any inconvenience this may cause and appreciate your patience as we resolve the issue. Please check back soon for updates, and thank you for being a valued Rebuy user

**Post-Mortem: Service Disruption** We recently experienced an issue that temporarily impacted one of our core services, while other systems continued running normally. This occurred during a routine system update, where one service didn’t adapt to new settings as expected. We’re actively reviewing our processes and related integrations to understand the cause and ensure smoother transitions in the future.

This incident has been resolved.

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

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

We're currently experiencing technical difficulties. Our team is investigating the issue and will provide updates soon.

On October 24, some merchants experienced issues with their Smart Cart functionality due to a data inconsistency that occurred during a planned system update. This impacted merchants using Smart Cart V2, particularly those who had recently modified their Smart Cart settings, though no data was lost. The issue was caused by an incompatibility between how cart configuration data was formatted in the backend and how it was processed on the frontend during the update. Our engineering team quickly identified the problem and implemented an emergency fix to restore proper functionality, clearing caches to ensure the issue was fully resolved. Moving forward, we have added additional steps to our deployment validation checks, and strengthened our testing protocols for configuration updates to help prevent similar incidents. We apologize for any disruption this may have caused and remain committed to enhancing the reliability of our system.

The team is confident that the issue has been resolved and is now conducting a thorough investigation to determine the root cause. Once the investigation is complete, we will provide a post-mortem report.

We are continuing to monitor for any further issues.

We are beginning to see issues resolved for the affected customers. Our team is actively monitoring and addressing any shops that are still experiencing problems at this time.

The issue has been identified and we are taking corrective actions at this time.

Some customers are seeing issues concerning Smart Cart not loading properly.

We've detected latency and timeout errors with a third-party service that supplies compute power for our search engine. While the impact was mainly on search functionality, some customers also reported errors within Smart Cart, which we believe may be connected to this incident.

**Cause:** We observed an unexpected increase in system activity over the past 24-48 hours, which revealed some challenges with the search system's ability to scale effectively under higher demand. **Resolution:** The search team addressed the issue by increasing system resources and rebalancing the search cluster, which restored full production health. **Prevention:** We are collaborating with our partners to conduct a comprehensive review of the incident and will continue to monitor the system to maintain stability. Additionally, there are several potential optimizations that are being evaluated for potential implementation to enhance overall system performance.

The team is confident that the issue was resolved as of 17:28 EDT. They are currently conducting a full investigation to determine the root cause. Once identified, we will provide a post-mortem report.

A fix has been implemented, and search functionality has been fully restored. We are actively monitoring the situation to ensure continued stability.

We are currently experiencing memory spikes related to the search engines, which we believe are causing the degraded performance. Our team is investigating the issue to resolve it as quickly as possible.

We’ve identified an issue with Smart Search experiencing intermittent loading problems within both the admin portal and on-site. Our team is fully engaged and actively troubleshooting the problem.

We identified an issue that led to severe latency, which was causing the Smart Search loading problems. With the changes we've implemented, the latency spike has decreased, and operations have returned to normal. Our developers are now investigating the root cause and will make the necessary adjustments to prevent this from recurring in the future.

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

The issue has been identified, and we are currently implementing changes to resolve it.

We are currently receiving reports that the administrative settings for Smart Search are not loading properly. Additionally, the on-site experience appears to be intermittently loading inconsistently across different sites. Our developers are actively investigating the issue.

This incident has been resolved.

The historical data appears to have been successfully restored. We are currently conducting further tests to confirm everything is functioning as expected.

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

We've discovered a bug related to a recent update, which is affecting historical chats within the in-app chat feature. Our team is actively working on resolving the issue and restoring access to previous conversations. During this process, you may experience some interruptions. We apologize for any inconvenience caused and will provide updates in the app as soon as possible.

We recently introduced a new feature that required additional GCP privileges, controlled by a setting managed through a secure password app. When the setting was toggled to enable the feature, the connector failed to restart the service immediately. This delay inadvertently triggered the downstream effects that were experienced. ‌ We apologize for any inconvenience this incident may have caused and appreciate your understanding as we work to prevent such issues in the future.

During the incident, customers experienced sporadic issues. Some were unable to log in, while others encountered problems with on-site features not loading properly.

This incident has been resolved.

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

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

The errors have subsided, and Rebuy Admin is no longer impacted. However, the investigation is still ongoing.

Our team has noticed an increase in errors within the Rebuy administrative portal and is currently investigating the issue. All on-site functionality remains unaffected. Further updates will be provided shortly.

This incident has been resolved.

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

Our team has observed a surge in errors in the Rebuy administrative portal and are researching the issue. All on-site functionality remains in tact. More updates to follow shortly.

Our main JavaScript file was retrieving modules from our origin server instead of Fastly, our content delivery network. Occasionally, it was caching an outdated version due to incomplete construction of the pod it was pulling from. Clearing Fastly cache promptly resolved the issue. We have put in safe guards to prevent this type of behavior from occurring in the future.

This incident has been resolved. Our engineering team will determine root cause and work towards steps to prevent any future issues such as this. Thank you for your patience and understanding. If there are any remaining issues, please reach out to support.

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

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

Rebuy Engineering is currently examining a problem concerning Smart Cart and various other Widget components not loading properly for some customers.

This incident has been resolved.

Our customer service platform vendor is currently experiencing issues with latency for chat functionality. Rebuy functionality is not impacted but our time to respond to chats may be delayed. Thank you for your patience.

This incident has been resolved.

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

Our customer service platform vendor is currently experiencing issues with routing new tickets properly. Rebuy functionality is not impacted but our time to respond to chats may be delayed. Thank you for your patience.

The incident has been marked as resolved. We'll now work on identifying the root cause and implementing preventive measures to mitigate future risk of reoccurrence. Thank you for your patience.

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

Some customers are seeing issues concerning Smart Cart not loading properly. Rebuy has identified the issue and is working on a fix.

This incident has been resolved and there should be no further issues with logins.

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

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

Our team has observed login issues into the the Rebuy administrative portal and are researching the issue. As of now, there is no impact on the storefront; the problem is solely related to the login process.

There was a legacy Redis address in the product engine led to unresolved connections, triggering a cascading failure and impacting overall functionality. The resolution involved the removal of the address. A comprehensive address audit will be conducted to prevent any recurrence of similar issues.

The issue has been resolved. We will investigate root cause and document in a post mortem. Thank you for your patience.

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

Our team has observed a surge in errors within Rebuy causing impact for some merchants and thus not loading in widgets or other aspects of the product. Our product team is aware and investigating.

The issue has been resolved. We will review and update the incident with a post mortem after we have had time to analyze the issue. Thank you for your patience.

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

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

Our team has observed a surge in errors in the Rebuy administrative portal and are researching the issue.

In a post-event analysis, it was identified that a hosting vendor experienced a 10-minute disruption, leading to loading problems with Rebuy.JS for some customers. The issue has been resolved, and there are no ongoing impacts. We are investigating the root cause with the vendor for further clarity.

The incident has been declared resolved. Should you encounter any additional problems, please contact our Support team, and we will thoroughly investigate your issue. We appreciate your patience.

On Monday, October 9th at 8:00am ET we began to receive inquiries about Rebuy services being unresponsive. After an investigation, we identified the issue to be related to DNS resolution, causing intermittent disruptions in accessing Rebuy services, including both admin and onsite features. The impact varied based on the region from which the services were accessed, affecting select customers. Our team located and resolved the DNS routing problem around 12:00 pm ET. DNS records have been flushed and updated in most major regions to ensure proper routing to the correct resources.

We are continuing to work on a fix for the issues.

We believe we've pinpointed a DNS problem causing sporadic regionalized issues and are collaborating with our service provider for next steps.

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

We're receiving reports of elevated level of errors with widgets and are currently looking into the issue.

The sporadic login issues were caused by a database table locking problem. By optimizing the database, we resolved the issue's impact, and overall put in preventative measures to mitigate the risk of reoccurrence.

This incident has been resolved.

We are continuing to monitor for any further issues.

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

Our team is continuing to investigate the issue.

We've detected issues with the Rebuy administrative portal, causing certain users to experience difficulties accessing it. However, functionalities like Widgets and Smart Cart are operating normally. Our team is actively addressing the situation.

According to the latest update from Shopify support, they were not aware of any changes on their part that could have either caused or resolved the issue. They informed us that their developers might have identified and fixed the problem internally, although they couldn't provide detailed information about it. In the event that the issue reoccurs, we will promptly escalate it.

The issue has been confirmed resolved at this time. We will update with the postmortem once we receive further feedback from Shopify.

The issue has appeared to have subsided at this time. We are currently testing to confirm.

We are continuing to investigate this issue.

Based on the logs, it seems that the post purchase script is configured to render properly. However, upon clicking the checkout button, the offer is not being submitted as indicated in the logs. We have submitted an escalation to Shopify in order to further address the current issue. We will continue in seeking updates on the matter and relay them here once we have more information.

We've identified that some customers are encountering problems with the display of post-purchase offers, not behaving as intended. In light of the observed errors, we are initiating communication with Shopify to establish a collaborative effort in resolving this issue. We will keep you informed of our progress as we investigate the issue with Shopify.

There were reports of some customers experiencing login issues to the Rebuy administrative portal. The errors lasted between 4:08PM EST and 4:17PM EST.

Upon analyzing the collected data and information, there was a bottleneck caused by the Redis peaking capacity. The root cause is that Redis infrastructure did not adequately scale to handle the increasing workload from the application at the time. We have since increased the capacity of the Redis infrastructure to accommodate a situation such as this in the future.

The problem has been confirmed as resolved. Our development team will conduct a thorough investigation to identify the underlying cause and rectify any remaining issues to ensure they do not happen again in the future.

We are continuing to monitor for any further issues.

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

Our developers have identified the issue and are currently working on implementing a solution.

We have also received reports of widgets experiencing delays in loading on merchant websites. This issue seems to be interconnected, and our team is currently investigating the underlying cause and working towards a solution.

There have been multiple reports of slowness in the Rebuy administrative portal. Our team is currently researching the issue.

The 403 errors have ceased at this time. Yotpo has not provided any specific explanation for the underlying cause, but we can confirm that the situation has been resolved and things are functioning normally again. We will keep a vigilant eye for any further errors and contact Yotpo if necessary.

We have shared Yotpo with a list of customer IDs and test IDs that are encountering difficulties during the installation and/or synchronization process. Yotpo is continuing their investigation into these issues, and are actively working to identify the root causes and develop appropriate solutions.

At the moment, we are encountering 403 errors while trying to synchronize Yotpo reviews with Rebuy. Our team is actively involved in communicating with the Yotpo team to investigate and analyze this problem. Once the issue is identified, we will collaborate with them to find a swift resolution. We appreciate you bringing this matter to our attention, and we will keep you updated as soon as we have more concrete information.

Shopify has shipped the fix for the bug they identified and the issues have been confirmed resolved.

Shopify has shipped a fix for the issue, and we are now commencing the process of confirming the outcomes with the customers who were impacted.

Shopify acknowledged that a solution was implemented by them last night, which resolved the problem for some merchants, but not for all of them. They are currently working on further troubleshooting on their end and are aiming to provide a fix for the issue as soon as possible.

A subset of customers are experiencing an issue where the Post Purchase event is not being triggered. After investigation, it was found that the issue originates from Shopify's end, and we are collaborating with their development team while they work resolve their bug.

On March 22, 2023, at approximately 1:30 PM ET, there was a brief malfunction during a code release that caused the Smart Cart feature to be briefly enabled for some users who had it enabled but not yet live. The Smart Cart feature has two states, enabled \(true or false\) and live \(true or false\). During the glitch, both of these conditions were set to true, causing the Smart Cart feature to be briefly enabled before being quickly disabled. The incident lasted approximately 10-15 minutes in total. Upon discovering the issue, the development team quickly took action to disable the Smart Cart feature for those who did not have it live in order to prevent any further impact to users. The team also worked to identify the root cause of the glitch and implement measures to prevent similar incidents from occurring in the future.

Brief malfunction where the Smart Cart feature to be briefly enabled for some users who had it enabled but not yet live.

On March 8, 2023, an unexpected outage occurred on the Redis instance that was hosting essential Rebuy database functions. This outage resulted in a loss of data, which in turn caused an outage of Rebuy widgets, smart carts, and the admin portal. After conducting a comprehensive root cause analysis, we discovered that the outage was caused by an issue within the GCP infrastructure. This issue had a downstream effect on the Redis instance, which led to data loss and the resulting outage. While we understand that issues can occur unexpectedly, we regret the impact it had on our customers and assure them that we are taking all necessary measures to prevent similar incidents from happening in the future. We deeply apologize for any impact caused by the outage and appreciate our customers' patience and understanding as we worked to resolve the issue. We understand how important it is to maintain the continuity of our services and are committed to taking all necessary actions to prevent future incidents and ensure the reliability and availability of our services.

The incident has been declared resolved. Our team will be providing a post mortem of the incident on the status page.

We are continuing to monitor for any further issues.

We have implemented a fix and are now validating results.

We are continuing to work on a fix for this issue.

The problem has been identified, and we are taking steps to address it.

We're experiencing an elevated level of API errors and are currently looking into the issue.

After a code release, we observed some minor regression issues related to the refactor, which were reflected in the debug logs that appeared in the console. We traced the cause to a less restrictive debug mode enablement check, where any existing/truthy debug value in the browser's Local Storage could trigger debug mode. To rectify this, we have made the check more stringent and moving forward, we will namespace our persistent key as rebuy-debug to avoid any potential conflicts with other third-party or browser extension codes.

This incident has been resolved.

We are continuing to monitor for any further issues.

We are continuing to monitor for any further issues.

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

Rebuy admin, widgets, and smart cart are seeing elevated errors. Our team has identified the issue and is currently working on a fix.

We're experiencing an elevated level of Admin login errors and are currently looking into the issue.

This incident has been resolved. Smart Cart is 100% operational. Our team will investigate root cause and determine next steps to prevent these error in the future.

We're experiencing an issue with Smart Carts misbehaving for merchants utilizing the payment installments feature within the Smart Cart. The team is actively investigating the issue. As a temporary workaround, you can disable the payment installments which should result in normal Smart Cart functionality.

This incident has been declared resolved. A post mortem will be conducted by the Rebuy development team to determine steps to prevent this from occurring in the future.

There was a brief issue related to MySQL that caused Rebuy Admin login errors. The MySQL related issues have since subsided and we are monitoring the situation at this time.

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

We're experiencing an elevated level of Admin login errors and are currently looking into the issue.

This incident is now resolved. We will continue to investigate root cause and will take any necessary actions to prevent this in the future.

The Smart Cart and Widgets are now loading properly. Our team continues to monitor and investigate root cause at this time.

The Smart Cart and Widgets are now loading properly. Our team continues to investigate root cause at this time.

We're receiving multiple reports of Smart Cart and/or Widgets not loading properly and are currently investigating.

MySQL hits max connections causing a cascading negative impact throughout the product

Clients experienced an intermittent issue where they observed an elevated level of Admin login errors starting at 3:55PM EST. These errors were caused by an issue with MYSQL that the Rebuy development team was able to resolve at approximately 5:00PM EST.

Some customers may have been impacted by duplicate billing between the dates of May 27, 2022 and June 1, 2022. We have identified and resolved the problem. Shopify is now in the process of reversing/refunding any of the duplicate charges that occurred between that time period. Your billing statements will be updated in the coming weeks.

This incident has been resolved. Admin logins are now fully functional.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We're experiencing an elevated level of Rebuy Admin login errors and are currently looking into the issue.

There was a temporary SQL issue that caused a brief period of login errors to occur for some customers. Access to the Rebuy Engine Admin has since been restored.

SQL failed over causing a brief issue with Admin login. Access to the Rebuy Engine Admin has since been restored.