Pipe17 Outage History
Pipe17 is up right nowPingoru has recorded 23 incidents for Pipe17: 5 in the last 12 months and 0 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 0 | 0 of 720 (0%) |
| May 2026 | 4 | 27 of 744 (4%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 512 (0%) |
Incidents, newest first
Minor May 14, 2026 Hold order release process delayed 2h 10m API (v3)
Started May 14, 2026, 04:30 PM UTC· resolved May 14, 2026, 06:41 PM UTC
- identified May 14, 2026, 06:06 PM UTC
Delays observed in releasing orders on hold. Investigation completed, code fix ready and being validated.
- monitoring May 14, 2026, 06:28 PM UTC
Fix is deployed. Valid orders are being released. The full queue should be next 15 minutes. System under active monitoring.
- resolved May 14, 2026, 06:41 PM UTC
All orders are processed now. System fully operational as expected.
Minor May 8, 2026 Amazon API Partial Outage 8h 58m API (v3)
Started May 08, 2026, 06:02 AM UTC· resolved May 08, 2026, 03:00 PM UTC
- monitoring May 08, 2026, 06:02 AM UTC
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
- monitoring May 08, 2026, 09:36 AM UTC
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.
- monitoring May 08, 2026, 12:24 PM UTC
Amazon SP APIs are now reporting a stable status. Our engineering team is actively working on resolving missed Orders & Fulfillments.
- resolved May 08, 2026, 06:50 PM UTC
At 8am Pacific time / 15:00 UTC, APIs were restore and all pending transactions were processed.
Notice May 6, 2026 Partial outage for inventory ledger updates –
Started May 06, 2026, 11:30 AM UTC· resolved May 06, 2026, 11:30 AM UTC
- resolved May 06, 2026, 08:58 PM UTC
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.
Minor May 6, 2026 Partial outage in inventory ledger cluster 15h 37m API (v3)
Started May 06, 2026, 07:30 AM UTC· resolved May 06, 2026, 11:07 PM UTC
- investigating May 06, 2026, 09:03 PM UTC
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.
- identified May 06, 2026, 09:53 PM UTC
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.
- monitoring May 06, 2026, 10:46 PM UTC
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.
- resolved May 06, 2026, 11:07 PM UTC
All checkpoints validated. No pending transactions to be reprocessed now. If you observe any issues, please file a support ticket.
Notice February 10, 2026 Status Update: Monitoring Alert Resolved –
Started Feb 10, 2026, 10:00 PM UTC· resolved Feb 10, 2026, 10:00 PM UTC
- resolved Feb 10, 2026, 10:45 PM UTC
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
Minor October 20, 2025 Authentication and Login Issues due to AWS US-East-1 Outage 1h 43m Management Portal
Started Oct 20, 2025, 08:11 AM UTC· resolved Oct 20, 2025, 09:55 AM UTC
- monitoring Oct 20, 2025, 08:11 AM UTC
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.
- resolved Oct 20, 2025, 09:55 AM UTC
The issue is resolved now. Pipe17 Web Application (UI) is fully operational.
Notice August 5, 2025 Delayed order routing 8m API (v3)
Started Aug 05, 2025, 06:34 PM UTC· resolved Aug 05, 2025, 06:42 PM UTC
- monitoring Aug 05, 2025, 06:34 PM UTC
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.
- monitoring Aug 05, 2025, 06:41 PM UTC
Continuing to monitor the system as the queue is getting back down to the normal size.
- resolved Aug 05, 2025, 06:42 PM UTC
The issue is resolved now. The route queue is back to normal. There is no delay observed.
Notice July 3, 2025 Degradation of service response time due to Database slowness 2h 58m API (v3), Management Portal
Started Jul 03, 2025, 02:10 PM UTC· resolved Jul 03, 2025, 05:08 PM UTC
- investigating Jul 03, 2025, 02:10 PM UTC
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.
- monitoring Jul 03, 2025, 04:18 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Jul 03, 2025, 04:19 PM UTC
Our database connectivity is restored now and we are recovering now.
- monitoring Jul 03, 2025, 04:46 PM UTC
We are continuing to monitor for any further issues.
- resolved Jul 03, 2025, 05:08 PM UTC
Service is fully restored.
Major February 5, 2025 Order Routing Partial Outage impacting some customers 2h 24m API (v3)
Started Feb 05, 2025, 04:02 PM UTC· resolved Feb 05, 2025, 06:26 PM UTC
- investigating Feb 05, 2025, 04:02 PM UTC
We are currently experiencing a partial outage affecting order routing for some customer organizations. Our engineering team is actively investigating the issue and working toward a resolution. We apologize for any disruption this may cause and appreciate your patience. We will provide updates as we make progress. If you require immediate assistance, please contact our support team. Thank you for your understanding.
- identified Feb 05, 2025, 04:08 PM UTC
We have identified the cause of the partial outage affecting order routing for some customer organizations and are actively working on a resolution. Our team is addressing the issue to restore normal operations as quickly as possible. We appreciate your patience and will provide further updates as we make progress. If you need immediate assistance, please reach out to our support team. Thank you for your understanding.
- monitoring Feb 05, 2025, 05:20 PM UTC
The partial outage impacting order routing for some customer organizations has been successfully resolved. Our team is actively monitoring the system to ensure continued stability and performance. We appreciate your patience during this time. If you experience any further issues or have questions, please don’t hesitate to contact our support team. Thank you for your understanding.
- resolved Feb 05, 2025, 06:26 PM UTC
The partial outage affecting order routing has been fully resolved, and all systems are now operating normally. We will continue to monitor performance to ensure ongoing stability. Thank you for your patience and understanding. If you have any further questions or encounter any issues, please reach out to our support team.
Major January 22, 2025 Amazon Token Refresh Not Working 9m API (v3)
Started Jan 22, 2025, 08:51 PM UTC· resolved Jan 22, 2025, 09:01 PM UTC
- investigating Jan 22, 2025, 08:51 PM UTC
Amazon Seller Central token refresh is failing. Fix ETA - 30 min
- identified Jan 22, 2025, 08:54 PM UTC
Issue has been identified and fix has been applied. Connections are reestablishing now. Full recovering in another 15 min.
- resolved Jan 22, 2025, 09:01 PM UTC
All connections are fully restored. Total outage was less to 50 minutes. System will resume processing where it was disconnected. there will be no data loss. We will continue active monitoring of the system.
Major October 28, 2024 Processing delays with NetSuite Connector since 2:40 AM PT (9:40am UTC) –
Started Oct 28, 2024, 09:30 AM UTC· resolved Oct 28, 2024, 09:30 AM UTC
- resolved Oct 28, 2024, 05:06 PM UTC
NetSuite connector observed significant delays in ingesting new and updated entities (orders, product, inventory). The issue was identified and rectified. Fix is already deployed. The connector is catching up to pull impacted transactions. We expect it to completed in next 3 hours.