Robert Nedelkow-Oracle · Oracle NetSuite Community Manager · Admin

An incident in our database infrastructure has resulted in an ongoing interruption of service for some customer accounts in our NA East facility. Operations Engineers were notified of the issue by monitoring and are working to resolve it as quickly as possible. Support filed Defect 505046 for this incident.

This incident has been resolved and the status page was updated. Support is focusing on coordinating case and defect updates for those impacted by this incident. We are also working on the root cause analysis and will provide additional information via your Support case. An incident in our NA East facility has resulted in…

farrago, you can reach Support by phone at 1877-NETSUITE, option 2 for Customer Service. Alternatively, you can send an email to support@netsuite.com if SuiteAnswers online case submission is unavailable.

I see what you mean. I saw a similar request to warn users when a record is being edited. A topic was started here but I don't know if they found a solution.

I think that is one way to avoid spam filters. A white-listed domain may help in your case but not all mail servers behave the same way, so additional troubleshooting steps may be needed. I found a couple of related SuiteAnswers that provide additional information: Answer Id: 70401, Answer Id: 14698.

Support may be able to provide additional information based on specific undelivered email, but a good starting point is Lists > Mailing > Undelivered Emails. This list provides information logged for undelivered email messages. A few other things to consider when emails are sent from NetSuite: [LIST] [*]DKIM compliance -…

Operations advised that this should be resolved now. Support will be reaching out to affected customers to confirm.

NA East incident update: The power interruption has been resolved and we are working to restore the NetSuite service. Our engineering teams are fully engaged on resolving this incident. The current ETA for complete service restoration is currently approximately 2 hours. Some customers may have their service restored…

status.netsuite.com was updated with the following: NA East incident update: The power interruption has been resolved and we are working to restore the NetSuite service. There is no ETA yet and our engineering teams are fully engaged on resolving this incident. We apologize for the inconvenience. 11:12 AM EST

NA East incident update: Service has been restored to approximately one third of the customers local to this data center. We expect to complete service restoration for the remaining customers within an hour. Thank you for your patience.

Network restoration is on-going however no new ETA was provided. I will post here as soon as any new details become available.

Resolution ETA is 15 minutes.

Support filed Defect 502963 : NA East > system.na1.netsuite.com > Blank page upon login | Unable to access NetSuite for this incident. Operations is investigating with highest priority. The status page has been updated with the following message: An incident in our NA East facility has resulted in a degradation in network…

We do not have an ETA however Operations has indicated this will be resolved shortly.

You can reach Support by phone at 1877-NETSUITE, option 2 for Customer Service. Alternatively, you can send an email to [EMAIL="support@netsuite.com"]support@netsuite.com[/EMAIL] if SuiteAnswers online case submission is unavailable.

Yes, we had that for around 10 minutes today also - approx 9:09 till 9:18 This incident was also posted on the status page: An incident in our EU Central facilities has resulted in a degradation in application for customers local to these datacenters when using accounting functionality. 04:05 AM - 04:20 AM EST(Resolved)

The fix for Defect 501668 is currently being released. You will receive a case update as soon as the release is complete.

This is likely due to an incident in our NA Northwest datacenter that occurred during a planned maintenance. If you haven't already done so, please submit a case to Support with your details and you will be notified once this has been resolved. Support filed Defect 499147 : Planned maintenance > OS 18C Upgrade >…

Jochen, MLS, khultquist, do you have case number for this? I haven't seen any issues reported when viewing customer records.

Kathy Woll I see the same error on the website. Do you have a case #? If not, please contact Support and they will investigate this further.

Apologies Kathy. I should have included the Support number in that case. You can reach Support by phone at 1877-NETSUITE, option 2 for Customer Service. Alternatively, you can send an email to [EMAIL="support@netsuite.com"]support@netsuite.com[/EMAIL] if SuiteAnswers online case submission is unavailable.

Support is investigating a similar issue in Defect 501668: Custom Roles > View/Edit Item record (with SUBSIDIARY / INCLUDE CHILDREN = True) > Permission Violation - The restrictions on your role deny your access to this record. Alternate Solution: Give the allow cross sub viewing temporarily. Please file a case and Support…

Same thing just happened to me... again. This new sandbox architecture(?) is hurting, and it's hurting my business. My defect number is 502415 Voltron, Operations is working on this with highest priority. Support will update your case as soon as an eta is available.

status.netsuite.com has been updated and this should be resolved now. Support filed Defect 498155 : NA East > Unable to login, for this incident.

From the Support tab, you can access the following: [LIST] [*]SuiteAnswers – In the SuiteAnswers portlet, click Go to SuiteAnswers to open the SuiteAnswers page. You can search on the SuiteAnswers page to find support articles, training videos, help topics, and best practice documents on any subject need help with. For…

This should now be resolved.

Assem, a standard Support request using SuiteAnswers is fine and they will attach your case to the existing Defect.

Defect 502415 should be resolved now. Support will begin reaching out to customers with related cases to confirm the fix.

KaylaM, can you post the Defect # here?

I haven't seen this error since 2017.2. Support will need to investigate this further and may need to file a Defect.