Pipe17 had 8 outages in the last 2 years totaling 31h 36m of downtime — averaging 0.3 incidents per month.
There were 8 Pipe17 outages since July 3, 2025 totaling 31h 36m of downtime. Each is summarised below — incident details, duration, and resolution information.
Delays observed in releasing orders on hold. Investigation completed, code fix ready and being validated.
Fix is deployed. Valid orders are being released. The full queue should be next 15 minutes. System under active monitoring.
All orders are processed now. System fully operational as expected.
Partial outage in the Amazon SP API affecting Orders, Fulfillments, Feeds, and Merchant Fulfillments was observed. This outage affects only those customers using Amazon integrations and is causing delays in submitting Fulfillments to Amazon. Our engineering team is closely monitoring the Amazon SP API status and will provide updates as soon as more information becomes available. Amazon API status can be viewed at: https://sellercentral.amazon.com/sp-api-status
Amazon SP API outage is still ongoing, latest investigation reveals Orders are affected along with Fulfillments. Our engineering team is continuously monitoring the situation and will provide updates as soon as more information becomes available.
Amazon SP APIs are now reporting a stable status. Our engineering team is actively working on resolving missed Orders & Fulfillments.
At 8am Pacific time / 15:00 UTC, APIs were restore and all pending transactions were processed.
Partial outage observed in database cluster hosting inventory ledger due to a forced maintenance by database service provider causing one node to be shutdown. Node restarted but cluster still recovering from the outage causing slowness in processing inventory ledger data for small subset of our customers. Root cause under investigation.
Partial outage observed in database cluster hosting inventory ledger due to a forced maintenance by database service provider causing one node to be shutdown. Node restarted but cluster still recovering from the outage causing slowness in processing inventory ledger data for small subset of our customers. Root cause under investigation.
Database cluster is fully operational. All current inventory ledger transactions are processed normally without any delay. We are actively working on processing any delayed transactions due to slow down.
All data integrity checked. Service fully operational, no delay. Vast majority of delayed transactions are processed. We are actively monitoring the service to identify any pending delayed transactions to be processed.
All checkpoints validated. No pending transactions to be reprocessed now. If you observe any issues, please file a support ticket.
Earlier today, our status page briefly indicated an issue with the Pipe17 Management Portal. After investigation, we confirmed there was no service downtime or customer impact. The alert was triggered by an error in our automated monitoring system, not by an actual availability issue. We have corrected the monitoring configuration and removed the incident from the status page. We’re continuing to review our monitoring safeguards to prevent similar false alerts in the future. Thank you for your understanding, and please reach out if you have any questions. Best regards, John Shao Pipe17
We are currently investigating issues with users being unable to log in to the Pipe17 UI. This is caused by our authentication service being impacted by an ongoing regional incident affecting Amazon Web Services (AWS) US-East-1. While this is affecting access to the Pipe17 web application, backend operations remain fully functional. All automation, order flows, and integrations continue to operate without disruption. Our engineering team is closely monitoring the AWS incident and will provide updates as soon as more information becomes available. Thank you for your understanding and patience as we work through this external service disruption.
The issue is resolved now. Pipe17 Web Application (UI) is fully operational.
Order routing engine slowdown caused delay in routing orders for some organizations. The issue started around 9:00AM PST and internal teams were alerted around 10:00AM PST. Investigation followed, a fix was deployed around 10:30AM PST. Order routing has resumed and the backlog will be cleared in the next hour. Situation is being actively monitored to ensure all orders in the queue are processed in a short period of time.
Continuing to monitor the system as the queue is getting back down to the normal size.
The issue is resolved now. The route queue is back to normal. There is no delay observed.
Database response time has slowed down causing degradation in processing time, and observed slowness in the portal with occassional timeouts. Investigation is underway, working closely with our database service provider.
A fix has been implemented and we are monitoring the results.
Our database connectivity is restored now and we are recovering now.
We are continuing to monitor for any further issues.
Service is fully restored.