Time: Nov. 16, 2022, 3:06 a.m.

Status: Resolved

Update: This incident has been resolved and syncs should be working as expected.

Time: Nov. 16, 2022, 1:22 a.m.

Status: Identified

Update: All syncs are back to normal. We have deployed changes to improve the performance and reliability of syncing. We are actively monitoring for any changes in performance.

Time: Nov. 15, 2022, 11:33 p.m.

Status: Identified

Update: Due to internal changes being done to optimize data syncing, e-commerce data syncs might not be going through in Frontend. This means that recently updated information may be missing from the IDE and when you publish your store. Live sites are unaffected.

Time: Oct. 25, 2022, 7 p.m.

Status: Resolved

Update: This has now been resolved and Shopify syncs should be working again as expected.

Time: Oct. 25, 2022, 5:15 p.m.

Status: Identified

Update: Shopify syncs may be impacted due to Shopify's outage. You can monitor the status at https://www.shopifystatus.com/.

Time: Oct. 22, 2022, 2:02 a.m.

Status: Resolved

Update: Maintenance is now complete.

Time: Oct. 20, 2022, 8:31 p.m.

Status: Monitoring

Update: All e-commerce data is coming through and syncing has resumed. Heroku report that maintenance may continue for the next few days. Frontend should not be affected by further updates, but Shogun will continue to monitor this incident and update it as needed. Publishing can resume and all systems are currently operational.

Time: Oct. 20, 2022, 7:14 p.m.

Status: Investigating

Update: Due to maintenance on a third party component (Heroku) e-commerce data syncs are currently delayed in Frontend. This means that recently updated information may be missing from the IDE. Live sites are unaffected, but we ask our customers not to publish until this incident is resolved.

Time: Sept. 23, 2022, 12:04 a.m.

Status: Postmortem

Update: **Summary:** From 8:40 pm ET on September 21st, 2022 to 11:52 AM ET on September 22nd, 2022, Shogun Frontend’s site builder was unavailable. When a new build was triggered, customers received an error message asking them to contact Shogun support. This was due to the underlying service that powers the site builder being unavailable for the duration of this incident. **Details:** Shogun partners with a global leader in infrastructure as a service as its infrastructure provider for storefront builds as well as storage of the resulting static assets output by the Frontend builder. Shogun maintains a geographically redundant builder and storage infrastructure within our provider. At 8:40 PM ET Shogun was alerted to errors within the Frontend builder infrastructure. The error indicated Shogun's account could no longer access the service underlying the builder. Our provider did not provide Shogun with any prior communication or warning that access to the service would be affected in any way. Shogun’s Engineering team immediately engaged with support at our provider to re-establish access to the underlying service. In parallel, Shogun’s Engineering team evaluated and planned alternative solutions if access was not restored in a timely fashion. Due to the fact that access was cut on an account level, the geographic redundancy previously established by Shogun did not allow for failover. Shogun’s Engineering team then began re-creating the Frontend builder infrastructure in a separate account at our provider to restore service. At 11:52 AM ET Shogun’s Engineering team completed the installation, configuration and testing of the new builder infrastructure. Shogun Engineering continues to work with our partners to restore access to the underlying service on our original account. **Preventative Measures:** Shogun will be investigating other technology partnerships for the Frontend site builder and will maintain backup builder infrastructure in a separate account which will allow for an instantaneous failover to a backup builder in case of similar issues in the future. Shogun is continuing to work with our provider on their own RCA for this issue and we will provide relevant updates as more information becomes available.

Time: Sept. 23, 2022, 12:03 a.m.

Status: Resolved

Update: We have resolved this incident, and have put in place additional measures to allow for instantaneous failover to a backup builder in case of similar issues in the future. A post-mortem will be posted shortly.

Time: Sept. 22, 2022, 4:37 p.m.

Status: Monitoring

Update: We are aware of intermittent build failures and are working to increase the amount of resources allocated to our builder infrastructure. In the event that a build fails, please wait a few minutes and retry.

Time: Sept. 22, 2022, 4:02 p.m.

Status: Monitoring

Update: The issue has been resolved and users can now build and publish. We will be actively monitoring this for the rest of the day. If you experience any difficulties building or publishing please contact support at https://getshogun.atlassian.net/servicedesk/customer/portals

Time: Sept. 22, 2022, 3:22 p.m.

Status: Identified

Update: We are continuing to work on a fix for this issue.

Time: Sept. 22, 2022, 7:38 a.m.

Status: Identified

Update: We are continuing to work with our hosting provider on this issue and are simultaneously working to bring redundant infrastructure online.

Time: Sept. 22, 2022, 2:43 a.m.

Status: Identified

Update: There is currently an issue preventing Frontend builds from completing. We have identified the source and are working to resolve it. Thank you for your patience.

Time: Sept. 14, 2022, 4:05 p.m.

Status: Resolved

Update: The incident has been fully resolved and all services are stable. Please note that all non-production stores may have a slight delay in full-service restoration. Should you encounter any issues, please contact Support via the Customer Portal.

Time: Sept. 14, 2022, 3:49 p.m.

Status: Monitoring

Update: The issue has been identified and a fix is now in place. We are monitoring all services.

Time: Sept. 14, 2022, 3:34 p.m.

Status: Investigating

Update: Shogun is currently experiencing an outage - we are currently investigating.