Is there an Stripo outage?
Stripo status: Systems Active
Last checked: 9 minutes ago
Get notified about any outages, downtime or incidents for Stripo and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 9 minutes ago
Get notified about any outages, downtime or incidents for Stripo and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Stripo.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
| Component | Status |
|---|---|
| Image Storage | Active |
| Stripo Public API | Active |
| Online Web Editor | Active |
| AMP Validation Service | Active |
| Billing Service | Active |
| Countdown Timer Service | Active |
| Documents Service | Active |
| Draft Service | Active |
| Editor Front-End part | Active |
| Export Service | Active |
| Guid Service | Active |
| HTML Cleaner Service | Active |
| Image Stock Service | Active |
| Modules Service | Active |
| Patches Service | Active |
| PDF Creation Service | Active |
| Smart-Elements Generation Service | Active |
| Stripo Account Backend part | Active |
| Stripo Account UI part | Active |
| Testing Service | Active |
| Thumbnail Generation Service | Active |
| Stripo Plugin | Active |
| AMP Validation Service (plugin) | Active |
| API Gateway Service (plugin) | Active |
| Countdown Timer Service (plugin) | Active |
| Documents Service (plugin) | Active |
| Draft Service (plugin) | Active |
| HTML Cleaner Service (plugin) | Active |
| Image Stock Service (plugin) | Active |
| Modules Service (plugin) | Active |
| Patches Service (plugin) | Active |
| Plugin Configuration Service (plugin) | Active |
| Proxy Server (plugin) | Active |
| Smart-Elements Generation Service (plugin) | Active |
| Thumbnail Generation Service (plugin) | Active |
View the latest incidents for Stripo and check for official updates:
Description: **Root Cause:** The incident was caused by a type issue during the release process, which was inadvertently introduced by our DevOps engineers. **Resolution:** Immediate actions were taken to resolve the issue, and service was fully restored by 14:22 UTC. **Preventive Measures:** To prevent such incidents in the future, we have implemented additional checks and safeguards in our release process. This includes enhanced code review procedures and improved deployment protocols to ensure the stability and reliability of our services. We apologize for any inconvenience caused and appreciate your understanding.
Status: Postmortem
Impact: Critical | Started At: June 20, 2024, 2 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Major | Started At: June 19, 2024, 10:21 a.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Major | Started At: June 19, 2024, 10:21 a.m.
Description: **Summary:** On 18th of June, Stripo experienced an outage that affected users' ability to log in to their Stripo accounts. This incident was triggered by a release that aimed to improve our service but inadvertently caused significant issues due to high load during a database migration. **What Happened:** During a recent release, a migration process was initiated to add new columns to our database. The high load on the system during this migration caused database locks, which in turn led to all microservices becoming stuck and unable to function properly. This resulted in users being unable to log in to their Stripo accounts. **Immediate Actions Taken:** 1. **Reverted the Release**: As soon as the issue was identified, we reverted the recent release to restore normal operations. 2. **Stopped Database Scripts**: All scripts running on the database were stopped to prevent further locking and load issues. 3. **Reloaded the Database**: The database was reloaded to clear the locks and ensure stability. 4. **Reverted Microservices**: All microservices were reverted to their previous versions to ensure system stability until the root cause could be addressed. **Next Steps:** * **Root Cause Analysis**: We will conduct a thorough root cause analysis to understand why the migration caused such significant issues and how to prevent this in the future. * **Improved Load Testing**: We will enhance our load testing procedures to better simulate high-load scenarios and identify potential issues before they occur in production. * **Database Migration Strategies**: We will review and improve our database migration strategies to ensure they can handle high load without causing locks or other issues. * **Monitoring Enhancements**: Our monitoring systems will be enhanced to detect and alert on similar issues more quickly, allowing for faster response times. **Conclusion:** We apologize for the inconvenience this outage caused our users. Our team is committed to improving our processes and systems to prevent similar incidents in the future. Thank you for your understanding and patience as we work to enhance the reliability and performance of our service. **Contact:** If you have any questions or need further assistance, please contact our support team at [email protected].
Status: Postmortem
Impact: Major | Started At: June 18, 2024, 11:01 a.m.
Description: **Summary:** On 18th of June, Stripo experienced an outage that affected users' ability to log in to their Stripo accounts. This incident was triggered by a release that aimed to improve our service but inadvertently caused significant issues due to high load during a database migration. **What Happened:** During a recent release, a migration process was initiated to add new columns to our database. The high load on the system during this migration caused database locks, which in turn led to all microservices becoming stuck and unable to function properly. This resulted in users being unable to log in to their Stripo accounts. **Immediate Actions Taken:** 1. **Reverted the Release**: As soon as the issue was identified, we reverted the recent release to restore normal operations. 2. **Stopped Database Scripts**: All scripts running on the database were stopped to prevent further locking and load issues. 3. **Reloaded the Database**: The database was reloaded to clear the locks and ensure stability. 4. **Reverted Microservices**: All microservices were reverted to their previous versions to ensure system stability until the root cause could be addressed. **Next Steps:** * **Root Cause Analysis**: We will conduct a thorough root cause analysis to understand why the migration caused such significant issues and how to prevent this in the future. * **Improved Load Testing**: We will enhance our load testing procedures to better simulate high-load scenarios and identify potential issues before they occur in production. * **Database Migration Strategies**: We will review and improve our database migration strategies to ensure they can handle high load without causing locks or other issues. * **Monitoring Enhancements**: Our monitoring systems will be enhanced to detect and alert on similar issues more quickly, allowing for faster response times. **Conclusion:** We apologize for the inconvenience this outage caused our users. Our team is committed to improving our processes and systems to prevent similar incidents in the future. Thank you for your understanding and patience as we work to enhance the reliability and performance of our service. **Contact:** If you have any questions or need further assistance, please contact our support team at [email protected].
Status: Postmortem
Impact: Major | Started At: June 18, 2024, 11:01 a.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.
