ShipStation Underreports or Misleads About Their Outages
Oct 20, 2025Web and InternetComments (0)
On ShipStation's Status page they give an overview of their services as well as historical uptime, summarized by day. They generally report a "Partial Outage" or a "Major Outage" when there is a problem, or note it as "Degraded Performance".
From my experience, ShipStation overuses "Partial Outage" or "Degraded Performance" when they are experiencing complete service failures. To illustrate my point, I'm going to talk about an outage they're having right now as I type.
Amazon is having major issues at their N Virginia AWS location. This appears to be where ShipStation hosts their web platform (either partially or fully). Due to these AWS issues, ShipStation is down and responding with 504 Gateway Time-out to all requests, including their API. This is across multiple accounts I manage.
Checking ShipStation's Status page and they are reporting this as "Degraded Performance" and a "Partial Outage". For their API status they are reporting it as "Operational".
Yet, ShipStation services, both the main dashboard and API, have been completely inaccessible for over 2 hours now. Their API stopped responding at 7:50 AM (Pacific Time) and has yet to recover as of 10:00 AM. Their latest update, from 2 hours ago, reads:
One could argue that this could still be technically a "partial outage" if at least some customers can access ShipStation services, though I think that is a disingenuous argument, assuming that is even the case. Plus, "degraded performance" and "performance issues" implies you can still use the service, with delays or at a slower speed. This is not the case.
ShipStation is obviously experiencing a major outage, caused by AWS where they host their services, and they aren't being honest about it. Certainly, once this is all resolved, this incident will be simply shown as a "Partial Outage" in their uptime history. Keep this in mind when you view ShipStation's historical uptime. They have a lot of partial outages, and speaking from experience over the last 12 years, these partial outages often entail a full inability to access the platform, and sometimes the API, login, and support systems are down too (though rarely mentioned).
At around 12:00 PM Pacific Time, partial access to ShipStation services was available again, with consistent errors and interruptions. Around 12:30 PM, the API started functioning, and ShipStation front-end functionality was improving. By 1:00 PM, everything appeared to be back to operating normally.
This event is still being labeled as a "partial outage" with "degraded performance" or "performance issues". What we experienced however was a major outage, which lasted from 7:50 AM to about 12:00 PM (4 hours), with a partial outage continuing for the next hour or so. During the entire outage, ShipStation reported that their Companion API V1 and V2, and Order Management API, were "Operational", which was incorrect.
From my experience, ShipStation overuses "Partial Outage" or "Degraded Performance" when they are experiencing complete service failures. To illustrate my point, I'm going to talk about an outage they're having right now as I type.
ShipStation Outage, October 20, 2025
Amazon is having major issues at their N Virginia AWS location. This appears to be where ShipStation hosts their web platform (either partially or fully). Due to these AWS issues, ShipStation is down and responding with 504 Gateway Time-out to all requests, including their API. This is across multiple accounts I manage.
Checking ShipStation's Status page and they are reporting this as "Degraded Performance" and a "Partial Outage". For their API status they are reporting it as "Operational".
Yet, ShipStation services, both the main dashboard and API, have been completely inaccessible for over 2 hours now. Their API stopped responding at 7:50 AM (Pacific Time) and has yet to recover as of 10:00 AM. Their latest update, from 2 hours ago, reads:
Update - ShipStation is currently experiencing performance issues due to an ongoing AWS service issue. We are actively monitoring their status and its impact on our platform. We will provide updates as they become available. Thank you for your patience.
One could argue that this could still be technically a "partial outage" if at least some customers can access ShipStation services, though I think that is a disingenuous argument, assuming that is even the case. Plus, "degraded performance" and "performance issues" implies you can still use the service, with delays or at a slower speed. This is not the case.
ShipStation is obviously experiencing a major outage, caused by AWS where they host their services, and they aren't being honest about it. Certainly, once this is all resolved, this incident will be simply shown as a "Partial Outage" in their uptime history. Keep this in mind when you view ShipStation's historical uptime. They have a lot of partial outages, and speaking from experience over the last 12 years, these partial outages often entail a full inability to access the platform, and sometimes the API, login, and support systems are down too (though rarely mentioned).
Update
At around 12:00 PM Pacific Time, partial access to ShipStation services was available again, with consistent errors and interruptions. Around 12:30 PM, the API started functioning, and ShipStation front-end functionality was improving. By 1:00 PM, everything appeared to be back to operating normally.
This event is still being labeled as a "partial outage" with "degraded performance" or "performance issues". What we experienced however was a major outage, which lasted from 7:50 AM to about 12:00 PM (4 hours), with a partial outage continuing for the next hour or so. During the entire outage, ShipStation reported that their Companion API V1 and V2, and Order Management API, were "Operational", which was incorrect.