Artwork Processing
Seeing a 504 from https://api.sherbert.cimpress.io/v2/assets error from studio
It has been an hour since this incident was contained, and we have not seen a recurrence. We are marking this incident as resolved. Within five business days, we will post a link the the post mortem of this incident here.
Things have remained stable for the past few minutes. We are actively monitoring the situation and will provide an update once it has been officially resolved.
The error rate has decreased, and services have appeared stable for the past 15 minutes. The team continues to work diligently, actively monitoring the logs, and we will provide you with an update shortly.
The team has initiated operations, and services are beginning to be restored in the US-East region. Deployments utilizing the Gateway are currently underway across various regions.
The team is in active collaboration with the AKeyless team, and we’ll provide you with more details shortly. Stay tuned for updates.
We’ve raised this akeyless issue to the support channel here
https://cimpress.slack.com/archives/C010TM5FCDS/p1695801577375699
Shebert’s team discovered that this is the identical problem we encountered last night. The surge in traffic to the CDN resulted in a sharp increase in calls to AKeyless, ultimately causing AKeyless to go offline.
The studio team is getting a 504 from https://api.sherbert.cimpress.io/v2/assets. The technical team is investigating. We will update this status page again as soon as we have more information or in 30 minutes, whichever is sooner.
https://api.sherbert.cimpress.io/v2/assets
{
“status”: 500,
“detail”: “Request failed with status code 429”,
“title”: “AxiosError”,
“instance”: “BfPQV0_185xyLFJO8VPbQ”
}