Time: July 30, 2024, 9:10 a.m.

Status: Resolved

Update: We are pleased to inform you that the issue with the Stripo API endpoint at https://stripo.email/emailgeneration has been resolved. Our technical team has corrected the Nginx configuration, and the endpoint is now functioning correctly. Resolution Details: The problem with Nginx, which was handling requests incorrectly, has been fixed. All necessary configurations and tests have been completed to ensure stable and correct operation of the endpoint. Recommendation: Despite the resolution, we encourage you to continue using the alternative endpoint at https://my.stripo.email/emailgeneration for a more reliable experience. This domain will provide enhanced stability and performance for your email generation needs. We apologize for any inconvenience caused during this period and thank you for your patience and understanding. If you have any further questions or need assistance, please do not hesitate to contact our support team.

Time: July 30, 2024, 9:06 a.m.

Status: Identified

Update: Impact: Users attempting to access the https://stripo.email/emailgeneration endpoint are encountering issues, which may affect their ability to generate emails through our API. We understand the critical nature of this functionality and are working to resolve the issue promptly. Workaround: To restore service immediately, we recommend changing the endpoint from https://stripo.email/emailgeneration to https://my.stripo.email/emailgeneration. This change will allow you to continue using the email generation feature without interruption. Resolution: Our technical team is actively working on fixing the Nginx configuration issue. We expect the problem to be resolved shortly, after which the original endpoint will function correctly again.

Time: July 30, 2024, 9:04 a.m.

Status: Identified

Update: We are currently experiencing an issue with the Stripo API endpoint at https://stripo.email/emailgeneration. The problem is related to Nginx, which handles the requests from https://stripo.email/emailgeneration to https://my.stripo.email/emailgeneration. As a result, the https://stripo.email/emailgeneration endpoint is functioning incorrectly.

Time: July 29, 2024, 9:22 a.m.

Status: Postmortem

Update: **Impact:** During the outage, users were unable to access the Stripo API, affecting their ability to perform tasks reliant on this feature. We understand the importance of the API to our users' workflows and deeply regret any inconvenience this interruption may have caused. **Root Cause:** The root cause of the outage was an unusually high load on our servers, which triggered an automatic reboot to manage the performance and stability of the system. **Resolution:** Our technical team responded swiftly to the incident, ensuring the servers were back online within 8 minutes. To prevent similar issues in the future, we have implemented additional logging to monitor server load and performance more closely. **Next Steps:** We are committed to providing a reliable and stable service. To avoid future occurrences, we will: * Analyze the logs to identify any patterns or anomalies that contributed to the high load. * Enhance our server infrastructure to better handle unexpected spikes in usage. * Continue to monitor the system closely and adjust our response strategies as needed. We apologize for any disruption this incident may have caused and appreciate your understanding and patience as we work to improve our services.

Time: July 29, 2024, 9:21 a.m.

Status: Resolved

Update: On July 29, 2024, the Stripo API experienced an outage from 07:51 AM to 07:59 AM UTC. This incident was caused by an unexpected surge in load, which resulted in the servers rebooting to handle the increased demand.

Time: July 28, 2024, 11:01 a.m.

Status: Resolved

Update: This incident has been resolved.

Time: July 28, 2024, 10:59 a.m.

Status: Investigating

Update: There might be an issue with access to the customer’s account. Time (UTC) : 2024-07-28T10:59:04

Time: July 25, 2024, 9:21 a.m.

Status: Resolved

Update: This incident has been resolved.

Time: July 25, 2024, 9:20 a.m.

Status: Investigating

Update: There might be an issue with access to the customer’s account. Time (UTC) : 2024-07-25T09:20:04

Time: July 22, 2024, 12:50 p.m.

Status: Resolved

Update: Our DevOps team has updated the configuration to ensure all necessary headers are properly whitelisted. The plugin can now be initialized without issues. The plugin is now fully functional, and users should no longer experience any initialization problems. We apologize for any inconvenience this incident may have caused and appreciate your patience while we worked to resolve it. Thank you for your understanding and continued support.

Time: July 22, 2024, 12:41 p.m.

Status: Identified

Update: Our team has identified the root cause of the plugin initialization issue. During the maintenance performed yesterday (details available here), we migrated our infrastructure from HTTP/1.1 to HTTP/2. Since this migration, we have received customer reports indicating that certain headers used in their requests are blocked. Our DevOps team has been working to add specific header fields to the whitelist as these requests come in. It appears there is a configuration issue within this process. We are continuing to work on resolving this configuration issue to ensure all necessary headers are allowed and the plugin can be initialized successfully.

Time: July 22, 2024, 12:33 p.m.

Status: Investigating

Update: We are currently experiencing an issue with our plugin infrastructure. Since 11:55 PM (UTC time), users have been unable to initialize the plugin due to a Cross-Origin Resource Sharing (CORS) error. This issue affects all users attempting to use the plugin, rendering it non-functional at this time.