NewStore Outage History

A fix has been implemented for the issue affecting NOM Insights Reporting. Reports are now loading successfully, and we are continuing to monitor the system to ensure stability. We will provide another update once we have confirmed there is no recurrence of the issue.

The fix has been successfully rolled out, and services are now recovering. We’re already seeing healthy incoming traffic returning to normal levels.

We identified and resolved an issue that caused some order and fulfillment endpoints to return 404 errors which impacted in-store returns, order injection and various other fulfillment API endpoints. We ask that you please resume normal operations and retry any operations that returned an error or 404 such as order injection or in-store returns. If you are still encountering issues, please contact NewStore Support. Our team will continue to monitor and provide further updates.

Our team is continuing to work on backfilling the missing data. We will update here once completed.

Our team is continuing to work on backfilling the missing data. The process is still in progress, and we are actively monitoring it. We will provide another update here once the backfill has been completed.

We are currently estimating that the backfill of data for this API service will be completed sometime tomorrow, 14th of March. We will update you again if this estimate changes or, otherwise, once completed.

The services have been restored and the platform has stabilized. Engineering is assessing any clean up that may be required due to the incident. If you are using the Associate App in offline mode, you can switch back to online mode. We are currently monitoring the issue and will provide another update once we have confirmed there is no reoccurrence of the issue.

We are continuing to monitor for any further issues.

The services have been restored and the platform has stabilized. Our team will continue to work on replaying any missing events. We will update this page once completed.

We have implemented a fix for the issue affecting access to NOM. The page is now loading as expected across all environments. We are currently monitoring the system to ensure continued stability. We will provide a final update once monitoring is complete.

Although we have not had any official update from Easypost, we are monitoring errors on our end and can see that they have dropped significantly since this was first reported. We will continue to update you as this Incident progresses.

We are still awaiting for an official update from Easypost, and so we continue to monitor errors on our end. We will continue to update you as this Incident progresses.

Easypost updated their incident. The issue has been identified and a fix is being implemented on their end. Our monitoring has not shown any new errors for more than 2 hours now.

We have received reports that EasyPost's API are having issues with performance and availability. Please view the current status and updates directly from EasyPost here: https://www.easypoststatus.com/ UPS shipments (rating) may be experiencing delays or errors due to API rate limitations on UPS's side. Easypost is working directly with UPS to resolve this issue. The order will show onhold for the following error Carrier Service Delivery Problem. Check the Shipping Option Reports feature in NOM under the Tools tab on the right hand side of the NOM directory. If you receive a 'Too Many Requests' error it is most likely related to this problem. If you have a reroute mechanism, there rerouting feature will retrigger the order routing otherwise try the handle exception button to reroute the order.

We are continuing to monitor the UPS API rate limitation. We have not received any further details form EasyPost or UPS, but will update this page as soon as something is changing.

While there has not been an official statement from UPS or EasyPost, we have verified that the our services have not see any further error messages regarding the rate limitation. At this moment we expect all functionality in the Associate App or in NOM to work without issue, but we will continue to monitor updates from the downstream services.

We have seen significant performance improvements for Insights reports and are monitoreing the situation.

Cloudflare implemented changes to their services and we can see Insights, docs.newstore.com, and docs.newstore.net loading properly again. We are actively monitoring the situation and will provide updates on this page.

We have just deployed a change which we suspect might caused an issue. Early indications is that login to NOM is now working again. We will provide another update here once we have confirmed no further occurrence.

The issue causing some in-store orders to display as “Pending” has been fixed. We are currently working on correcting the affected orders so that they display correctly in NOM. We will continue to observe until all orders are fully updated and confirmed resolved.

We have a fix in place and our engineering team have completed the replay of all events affected by this incident. We are actively monitoring the platform and will provide another update once we have confirmed there is no reoccurrence of the issue.

The situation has improved and the event stream is steadily processing, though some delays may persist until all events have been fully emitted. We will provide another update once processing has fully normalized.

We have implemented a fix and are actively monitoring the platform. The issue had been causing slowness in the Associate App, including during order checkout and payment processing, and order injection. All affected services are now operating normally. We will provide another update once we have confirmed the issue has been fully resolved and there is no recurrence.