Störungsverlauf von Whiplash

This incident has been resolved.

This incident has been resolved.

We are currently investigating this issue.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

This incident has been resolved.

This incident has been resolved.

This incident has been resolved.

We are currently investigating this issue.

We are continuing to investigate this issue.

This incident has been resolved.

We are currently investigating this issue.

This incident has been resolved.

The issue has been identified and a fix is being implemented.

We are continuing to work on a fix for this issue.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

The development team is investigating. Updates will be coming shortly.

We are continuing to investigate this issue.

The application should be more responsive now. Fix is being applied across the system.

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 fix has been applied and the application is back to performing at acceptable levels.

The Whiplash app and API were unresponsive for about 6 minutes due to an issue related to a code deploy. The issue has been resolved.

Whiplash users were unable to buy postage labels for 40 minutes due to an issue with a payment gateway.

We are currently investigating an issue with the 2.0 API related to refreshing tokens.

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

V2 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.

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.

We are continuing to work on returning affected orders to their original state, and will share hourly updates until the issue is resolved.

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.

A fix has been implemented, and we are expecting orders to begin returning to their original status shortly.

Affected orders are returning to their correct statuses.

Affected orders are continuing to return to their correct statuses.

All affected orders have returned to their correct status. Please contact support if you require additional assistance.

3 minutes of downtime for database maintenance.

Whiplash User Interface unable to be accessed for about 7 minutes.

We are currently investigating this issue.

This incident has been resolved.