Last checked: 6 minutes ago
Get notified about any outages, downtime or incidents for ShipHawk and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for ShipHawk.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
Component | Status |
---|---|
ShipHawk Application | Active |
ShipHawk Website | Active |
Carrier/3PL Connectors | Active |
DHL eCommerce | Active |
FedEx Web Services | Active |
LTL / Other Carrier Web Services | Active |
UPS Web Services | Active |
USPS via Endicia | Active |
USPS via Pitney Bowes | Active |
ShipHawk APIs | Active |
Shipping APIs | Active |
WMS APIs | Active |
ShipHawk Application | Active |
WMS | Active |
ShipHawk Instances | Active |
sh-default | Active |
sh-p-2 | Active |
System Connectors | Active |
Acumatica App | Active |
Amazon Web Services | Active |
Magento | Active |
Oracle NetSuite SuiteApp | Active |
Shopify App | Active |
View the latest incidents for ShipHawk and check for official updates:
Description: Status update: This issue is resolved. Customer Impact: Some customers are seeing the following error when attempting to book some of their shipments: “There was a problem booking your shipment: Couldn’t find Shipment with ‘id’= [WHERE “shipments”.“deleted_at” IS NULL AND “shipments”.“crm_instance_id” = $1]”. This error prevents them from booking the shipment. A workaround is possible and requires an administrative change by our team. If you experience this issue, contact our support team for assistance. Start Time: April 1, 7:12 AM PST End Time: April 1, 10:00 AM PST
Status: Resolved
Impact: Minor | Started At: April 1, 2022, 3:29 p.m.
Description: Status update: This issue is resolved. Customer Impact: Some customers are seeing the following error when attempting to book some of their shipments: “There was a problem booking your shipment: Couldn’t find Shipment with ‘id’= [WHERE “shipments”.“deleted_at” IS NULL AND “shipments”.“crm_instance_id” = $1]”. This error prevents them from booking the shipment. A workaround is possible and requires an administrative change by our team. If you experience this issue, contact our support team for assistance. Start Time: April 1, 7:12 AM PST End Time: April 1, 10:00 AM PST
Status: Resolved
Impact: Minor | Started At: April 1, 2022, 3:29 p.m.
Description: Status update: A fix has been deployed and confirmed to be working as expected. Customer Impact: Some Users with more than one warehouse assigned to them cannot see/filter orders for the warehouses they are assigned to. Start Time: March 10, 6:27 AM PST End Time: March 10, 8:53 AM PST
Status: Resolved
Impact: Minor | Started At: March 10, 2022, 4:18 p.m.
Description: Status update: A fix has been deployed and confirmed to be working as expected. Customer Impact: Some Users with more than one warehouse assigned to them cannot see/filter orders for the warehouses they are assigned to. Start Time: March 10, 6:27 AM PST End Time: March 10, 8:53 AM PST
Status: Resolved
Impact: Minor | Started At: March 10, 2022, 4:18 p.m.
Description: This incident has been resolved. For more details, see https://status.netsuite.com/incidents/sn1hlv7zhzz5
Status: Resolved
Impact: Critical | Started At: Feb. 17, 2022, 7:34 p.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.