Outage in ShipHawk

Investigating reported issue with booking shipments

Resolved Minor
April 01, 2022 - Started over 3 years ago - Lasted about 2 hours
Official incident page

Need to monitor ShipHawk outages?
Stay on top of outages with IsDown. Monitor the official status pages of all your vendors, SaaS, and tools, including ShipHawk, and never miss an outage again.
Start Free Trial

Outage Details

Status update: We are investigating this issue. 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
Components affected
ShipHawk Dashboard
Latest Updates ( sorted recent to last )
MONITORING over 3 years ago - at 04/01/2022 05:13PM

Status update: A fix has been implemented and we are monitoring the results

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

IDENTIFIED over 3 years ago - at 04/01/2022 03:45PM

Status update: We have identified the issue and are working towards a resolution.

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

INVESTIGATING over 3 years ago - at 04/01/2022 03:29PM

Status update: We are investigating this issue.

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

Latest ShipHawk outages

WWEX / SpeedShip services outage - 8 days ago
Degraded performance with PrintNode - 4 months ago
Pitney Bowes Expedited Delivery Services partial unavailability - 5 months ago
Partial WMS Access Issue – Investigation Underway - 6 months ago
Rating API slowness - 7 months ago

Be the First to Know When Vendors Go Down

With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.

Start free trial

No credit card required · Cancel anytime · 4522 services available

Integrations with Slack Microsoft Teams Google Chat Datadog PagerDuty Zapier Discord Webhook