This incident has been resolved. We will not provide further information in a public incident report.

Summary

On May 16, 2025, from 14:00 to 16:50 UTC, some merchants experienced errors updating products, prices and collections, with the error message: Product # update error: The transaction log for database 'tempdb' is full due to 'ACTIVE_TRANSACTION' .

This started after the transaction log for database 'tempdb' became full for one of our catalog database instances. This was solved by shrinking and restarting the impacted database. We will follow-up by creating a new alarm to warn us earlier and prevent this from happening again.

Our global sales flow was unaffected during this incident.

We apologize for any inconvenience this may have caused.

Timeline

At 16:01 UTC, our incident response team was notified of the issue.

At 16:11 UTC, our team identified the impacted catalog database instance.

At 16:18 UTC, we attempted to shrink the impacted database, but it was not effective.

At 16:38 UTC, we restarted the impacted database.

At 16:50 UTC, the incident was fully mitigated.

This incident has been resolved. We will provide further information in a public incident report.

Summary

On May 12, 2025, from 19:42 to 20:05 UTC, a subset of accounts experienced an increase in HTTP status 500 errors in Checkout API and Order Management API. As a result, some shoppers experienced issues with order placement and some merchants experienced issues with order management.

Additionally, some accounts reported errors in Intelligent Search after the incident was considered mitigated. We are still investigating the potential correlation between this symptom and the contributing factors to this incident.

Our global sales flow was affected for 23 minutes during this incident, although only a subset of accounts were impacted.

We apologize for any inconvenience this may have caused.

This incident has been resolved. We will not provide further information in a public incident report.

Summary

On May 08, 2025, from 15:15 UTC to May 09, 14:40 UTC, Affected Accounts experienced errors when uploading new banners and showing them on the storefront during this timeline.

Our global sales flow was unaffected during this incident.

We apologize for any inconvenience this may have caused.