Skip to main content

Pionex.US System Upgrade Notice

Dear users,   Pionex.US will perform a scheduled system upgrade at 04:45 (UTC) on February 6th, 2023. The upgrade period will last approxi...

Dear users,

Pionex.US will perform a scheduled system upgrade at 04:45 (UTC) on February 6th, 2023. The upgrade period will last approximately 6 hours.

During this system upgrade, users will encounter the following situations:

  • All the bot's orders will not be filled during the upgrade.

  • All unfilled buy & sell limit orders will be re-placed by pionex.us on behalf of our customers once the system upgrade is complete.

  • Recurring buy instances that are scheduled to coincide with the upgrade period will be skipped. however, recurring buys will resume as scheduled once the upgrade is complete.

Please note:

  • The upgrade will only affect registered users after December 28th, 2022.

  • Advanced Trading; Buy, Sell & Convert; and Staking services will be temporarily suspended during the upgrade period.

  • The 6-hour upgrade period is an estimate only. We will communicate across our official Pionex.US channels and update this announcement once the scheduled upgrade is complete.

If you have open orders:

  • The following orders will be re-placed by Pionex.US on behalf of our customers once the system upgrade is complete:
    All unfilled buy & sell limit orders

If you have recurring crypto purchases:

  • Recurring buy instances that are scheduled to coincide with the upgrade period will be skipped. However, recurring buys will resume as scheduled once the upgrade is complete.

Thanks for your support.

Pionex.US team

February 6th, 2023


Download the Pionex.US app to trade on the go: iOS | Android

Follow us to stay up to date with Pionex.US news and announcements:

Group_67__1_.png
image
image

Pionex.US on Twitter

Trading in the crypto market carries a substantial risk and the possibility of making both significant profits and losses. Please trade cautiously, Pionex.US could not assure any profit. Risk Disclaimer

Did this answer your question?