Update From BigCommerce
Resolved - Our engineering team has resolved the issue and the V2 Orders API is now operating as expected.
Nov 5, 13:31 CST
Source: https://status.bigcommerce.com/

Update from BigCommerce - Investigating - We've received reports that certain routes on the V2 Orders API are returning 404 errors incorrectly. BigCommerce engineers are investigating and will update soon.
Nov 5, 12:49 CST
Source: https://status.bigcommerce.com/

SKULabs has detected a majority of BigCommerce stores are not syncing on-time. BigCommerce has posted an outage notice on their website.

SKULabs is designed to automatically scale back sync for your store when there are detected outages. SKULabs will automatically resume sync as soon as recovery is detected. There is no action required on your part to pause or resume your sync.

If you have a large number of sales on other channels that track the same warehouse as your BigCommerce store there is a chance you can oversell during this outage. It is recommended to keep a reserve of inventory that can hold you over for up to 24 hours of sales if you want to completely avoid the risk of overselling. Amazon for instance will not even open a ticket for you with regard to inventory feeds taking less than 24 hours to process. Such 24 hour inventory feed outages are common during peak season (November-January). Speak with SKULabs support to build your inventory reservation strategy using rules and reserve warehouses to prevent overselling.

Should I contact SKULabs support?

If there are any questions please reach out through the in-app conversation system as we will not have additional details by phone.

Contacting BigCommerce support while a posted outage is live is not recommended until BigCommerce recommends you to contact them directly if you're still having issues.

Check the status page on BigCommerce's website for updates on when you should reach out if you're still having connectivity issues.