Is Stripo down?

We are investigating reports of users being unable to log in, seeing missing team members, or experiencing slow loading of emails. Our team is working to identify the cause.

We have identified the root cause: an internal caching service (Redis) ran out of memory and began rejecting writes. As a result, permission checks bypassed the cache and put excessive load on the account service, causing slow responses, login failures, and missing account data. We have increased the cache capacity and are preparing a permanent fix.

Cache capacity has been increased and the system is recovering. Response times are returning to normal as caches warm up. A permanent fix is being deployed.

The permanent fix has been deployed to all production clusters and all systems are operating normally. During the incident (July 30, 22:48 UTC – July 31, ~04:30 UTC, with residual slowness until ~08:49 UTC), some users experienced login failures, missing team member data, and slow loading of emails. No data was lost. We have added memory-usage alerting to detect this class of issue before it affects users. We apologize for the inconvenience.

On July 28, between approximately 1:28 PM and 1:58 PM (UTC), the Stripo Plugin failed to initialize for embedded integrations. The issue was caused by degraded performance of an internal statistics service, which slowed down plugin initialization requests. Our team restarted the affected service and temporarily disabled statistics collection for plugin initializations to restore normal operation. The plugin is now loading as expected. We apologize for any inconvenience this may have caused.

There might be issues while uploading, changing or removing customer’s images inside the editor. Time (UTC) : 2026-07-25T09:18:22

This incident has been resolved.

On July 24 between 09:20 and 09:50 UTC, real-time co-editing in the plugin editor was temporarily unavailable. During a scheduled release, a database schema update took longer than expected and briefly overloaded the database, which caused the co-editing service to restart. Our team identified the cause and fully restored the service by 09:50 UTC. No customer data was lost, and all other Stripo functionality remained available throughout. We've since added safeguards to our release process to prevent a recurrence.

There might be an issue with access to the customer’s account. Time (UTC) : 2026-07-23T09:39:04

[Comment from Opsgenie]Dmitry Kudrenko acknowledged alert: "Partial Outage in work of Stripo Account Backend part"

This incident has been resolved.