Is there an Stripo outage?
Stripo status: Systems Active
Last checked: 56 seconds ago
Get notified about any outages, downtime or incidents for Stripo and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 56 seconds 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: **Incident Details** At approximately 14:49, our monitoring systems detected a significant spike in database loads. This increase in load caused delays in database queries and resulted in a slowdown of our services. Our engineering team was alerted immediately and began investigating the root cause of the issue. By 15:24, we were able to identify the source of the increased load and implemented measures to mitigate it. Normal service was restored, and the database load returned to acceptable levels. **Impact** During the service interruption, users may have experienced: * Delays in email template loading * Slow response times when accessing the Stripo.email platform * Temporary inability to save or send emails **Resolution** Our engineering team took the following actions to resolve the incident: 1. Identified the source of the increased database load. 2. Implemented load balancing measures to distribute the database queries more efficiently. 3. Optimized specific database queries to reduce processing time. **Preventive Measures** To prevent similar incidents in the future, we are taking the following steps: 1. Enhancing our monitoring systems to detect and alert us to abnormal load patterns more quickly. 2. Conducting a thorough review of our database infrastructure to identify and address potential bottlenecks. 3. Implementing additional load balancing solutions to ensure better distribution of database queries. We apologize for any inconvenience this incident may have caused and appreciate your patience and understanding as we worked to resolve the issue. Our team is committed to ensuring the reliability and performance of our services.
Status: Postmortem
Impact: Critical | Started At: June 27, 2024, 2:49 p.m.
Description: **Incident Details** At approximately 14:49, our monitoring systems detected a significant spike in database loads. This increase in load caused delays in database queries and resulted in a slowdown of our services. Our engineering team was alerted immediately and began investigating the root cause of the issue. By 15:24, we were able to identify the source of the increased load and implemented measures to mitigate it. Normal service was restored, and the database load returned to acceptable levels. **Impact** During the service interruption, users may have experienced: * Delays in email template loading * Slow response times when accessing the Stripo.email platform * Temporary inability to save or send emails **Resolution** Our engineering team took the following actions to resolve the incident: 1. Identified the source of the increased database load. 2. Implemented load balancing measures to distribute the database queries more efficiently. 3. Optimized specific database queries to reduce processing time. **Preventive Measures** To prevent similar incidents in the future, we are taking the following steps: 1. Enhancing our monitoring systems to detect and alert us to abnormal load patterns more quickly. 2. Conducting a thorough review of our database infrastructure to identify and address potential bottlenecks. 3. Implementing additional load balancing solutions to ensure better distribution of database queries. We apologize for any inconvenience this incident may have caused and appreciate your patience and understanding as we worked to resolve the issue. Our team is committed to ensuring the reliability and performance of our services.
Status: Postmortem
Impact: Critical | Started At: June 27, 2024, 2:49 p.m.
Description: Today, between 10:13 and 10:27 UTC, an unexpected issue occurred during an infrastructure upgrade to improve service speed by transitioning from HTTPS 1.1 to the H2 protocol. This change inadvertently caused an authentication error during initialization, which our status page did not detect immediately due to all microservices continuing to run. However, internal monitors identified the problem, prompting our DevOps team to revert the changes swiftly. Despite the rapid response, this incident led to a brief period of downtime. We apologize for any inconvenience this may have caused. Our team is thoroughly investigating why the modifications that were successfully tested in our staging environment did not perform as expected in the production infrastructure. Next Steps: We are committed to ensuring the reliability of our services and are closely examining this incident to prevent future occurrences. We will keep our users updated as we implement further improvements. Thank you for your understanding and patience.
Status: Resolved
Impact: Critical | Started At: June 26, 2024, 7:30 a.m.
Description: Today, between 10:13 and 10:27 UTC, an unexpected issue occurred during an infrastructure upgrade to improve service speed by transitioning from HTTPS 1.1 to the H2 protocol. This change inadvertently caused an authentication error during initialization, which our status page did not detect immediately due to all microservices continuing to run. However, internal monitors identified the problem, prompting our DevOps team to revert the changes swiftly. Despite the rapid response, this incident led to a brief period of downtime. We apologize for any inconvenience this may have caused. Our team is thoroughly investigating why the modifications that were successfully tested in our staging environment did not perform as expected in the production infrastructure. Next Steps: We are committed to ensuring the reliability of our services and are closely examining this incident to prevent future occurrences. We will keep our users updated as we implement further improvements. Thank you for your understanding and patience.
Status: Resolved
Impact: Critical | Started At: June 26, 2024, 7:30 a.m.
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.
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.
