Status: Resolved on October 28, 2026 at about 3:15 PM PT — monitoring
Between 11:31 AM and about 3:15 PM PT on October 28, 2026, NetSuite refused every request sent from one of the internet addresses Celigo uses to reach NetSuite. Celigo made no changes to its platform or network before this began; the address had been in use unchanged. Requests from Celigo's other addresses kept working, so some records succeeded while others failed. Celigo moved all NetSuite traffic to a different address, which stopped the errors, and opened a case with NetSuite to understand why NetSuite refused the address. Only the North America region was affected.
What to do now
- You do not need to re-authorize or change any NetSuite connection. Connections that went offline are re-tested automatically and come back online on their own. Re-authorize only if a connection is still offline after about 4:50 PM PT.
- Retry the records that failed. In Error Management, open each affected flow step and choose Manage all > Retry All (up to 20,000 errors per pass; repeat if there are more). Retry flows in order — customers and orders before fulfillments and invoices — and spread large retries over the day.
- Retrying is safe: the refused requests never reached NetSuite, so retrying does not create duplicate records.
- If a scheduled NetSuite export ran during the window and failed partway, run it once with a custom start date of 11:30 AM PT, October 28, to pick up anything it missed.
- If you created extra NetSuite connections or regenerated tokens while troubleshooting, point your flows back to the original connection and remove the extras.
- Errors from 10:30 to 11:46 AM PT that say the request timed out are different: those requests may have completed in NetSuite, so check before retrying them.
Applies to
- integrator.io accounts in the North America region. EU, Canada and Australia are not affected.
- Every NetSuite connection: custom flows and all NetSuite integration apps (Shopify, Salesforce, Amazon, WooCommerce, BigCommerce, Magento 2 and others).
- NetSuite exports, lookups and imports; connection tests; API Builder calls that reach NetSuite.
Symptoms
Where you see it
| Error message
|
|---|---|
Any NetSuite export, lookup or import step
| invalid_response with an empty message, or HTTP 403 Forbidden with no response body
|
Shopify – NetSuite integration app, order flows
| Failed to add/update customer for Shopify order #12345.
|
Connections page
| NetSuite connections flip offline, come back after re-authorizing, and go offline again on the next run
|
Edit connection drawer
| The connection associated with this resource is currently offline and configuration is limited.
|
Why this happens
NetSuite is refusing requests that leave one group of Celigo's NA servers. Requests from Celigo's other NA servers and from the EU, Canada and Australia regions reach the same NetSuite accounts normally, and no Celigo release was deployed. Your NetSuite roles, tokens, IP allow lists and integration records did not change and do not need to.