Historical record of incidents for RyderShip
Report: "Degraded performance in Core Application"
Last updateThis incident has been resolved.
Report: "Degraded performance in Core Application"
Last updateThis incident has been resolved.
Report: "Degraded performance in Core Application"
Last updateThis incident has been resolved.
A fix has been implemented and we are monitoring the results.
The issue has been identified and a fix is being implemented.
We are currently investigating this issue.
Report: "Degraded performance in Core Application and API"
Last updateThis incident has been resolved.
Report: "Degraded performance in Core Application and API"
Last updateThis incident has been resolved.
Report: "Degraded performance in Core Application and API"
Last updateThis incident has been resolved.
Report: "Degraded performance in core application and API"
Last updateThis incident has been resolved.
We are continuing to investigate this issue.
We are currently investigating this issue.
Report: "Performance issues with Whiplash"
Last updateThis incident has been resolved.
We are currently investigating this issue.
Report: "System Outage"
Last updateThis incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are continuing to work on a fix for this issue.
The issue has been identified and a fix is being implemented.
Report: "Whiplash application is slow or unresponsive."
Last updateThe fix has been applied and the application is back to performing at acceptable levels.
The Whiplash app will have degraded performance while the fix is being applied to the system. We expect it to be completed by 1:30 pm EST
The application should be more responsive now. Fix is being applied across the system.
We are continuing to investigate this issue.
The development team is investigating. Updates will be coming shortly.
Report: "Brief down time"
Last updateThe Whiplash app and API were unresponsive for about 6 minutes due to an issue related to a code deploy. The issue has been resolved.
Report: "Payment gateway issue"
Last updateWhiplash users were unable to buy postage labels for 40 minutes due to an issue with a payment gateway.
Report: "API Token Authorization"
Last updateV2 refresh tokens now need the client_id and client_secret included in the Post body. See https://docs.getwhiplash.com/pages/authentication-for-the-v2-api#refresh-tokens for more information.
v2 API authentication has been resolved. A recent Oauth upgrade now requires refresh requests to include a `client_id` and `client_secret` in the refresh request: https://docs.getwhiplash.com/pages/authentication-for-the-v2-api#refresh-tokens
We are currently investigating an issue with the 2.0 API related to refreshing tokens.
Report: "Orders Cancelled"
Last updateAll affected orders have returned to their correct status. Please contact support if you require additional assistance.
Affected orders are continuing to return to their correct statuses.
Affected orders are returning to their correct statuses.
A fix has been implemented, and we are expecting orders to begin returning to their original status shortly.
We are continuing to work on returning affected orders to their original state. We are cautiously optimistic that we will have this issue resolved by 5:30 PST.
We are continuing to work on returning affected orders to their original state, and will share hourly updates until the issue is resolved.
We have identified an issue in which orders that were queued for shipment were unintentionally cancelled. We are working to return the orders to their original condition. We are continuing to research the origin of the problem, but have reason to believe this was an internal system issue.
Report: "3 minute downtime"
Last update3 minutes of downtime for database maintenance.
Report: "Database Update"
Last updateWhiplash User Interface unable to be accessed for about 7 minutes.
Report: "Delays in sending notifications"
Last updateThis incident has been resolved.
We are currently investigating this issue.