And again another Friday update goes horribly wrong! This is really getting silly now - perhaps NetSuite should stop buying up companies and spend the money fixing the service they're supposed to be supplying us!

Can someone at NetSuite please respond to this - I opened the case 90 minutes ago - and have not heard anything at all since then. (Case 1944685) This is not an acceptable level of service.

We're getting constant errors on https://system.netsuite.com/app/common/entity/custjob.nl?whence=

Suffering the same issues here - unable to do anything at all. Any NetSuite Support staff able to provide an update?

One assumes that there are hopefully internal release notes - or are the engineers just doing as they wish - so surely releasing a top-level version of these wouldn't be that much work - and would save everyone else considerable work.

Welcome to the pleasure of the 'eFix' updates - I dread Friday mornings, never know what's going to be broken. As you say, a Release Note of any type would seriously help with these fixes, at least we would then know what areas to focus on to look for possible issues/causes. Right now, it's a lucky dip - anything from PDF…

Same here, down again!

I'm having the same issue, Saved Searches which ran perfectly for months have sudden;y stopped running :(

http://www.crmexposed.com/compare-netsuite-data-center-reliability-security.php Is this true?? No, very old article. They now have two data centres with a 3rd coming.

UserGroup keeps going offline too :(

Yes, all down here - exactly the same issue. if you're logged in, you're fine - but it fails on authentication.

Latest Status :( Site-wide Service Interruption All accounts are affected. Do not attempt to log in to your account. Your patience is appreciated as we work to resolve the issue. More information will be posted on this status page as it becomes available.

NetSuite - it would be nice to get some indication of what happened please.

Back up now

Down here - An error occurred while processing your request. Reference #97.fb589140.1391763761.a975fa

We've seen the same overnight. However, we do have a test@test.com email address in our records - it's inactive though, so I would suggest that if you don't see one in your own records, make sure you're able to search for inactive records.

We have an inactive test customer with this email, but that account is not set to have any access - considering that this issue seems to be affecting a lot of accounts, I am curious whether there is a single login attempt causing this. As Bill C mentions above, test@test.com is probably not that unusual test email to use -…

Could you tell me where I can view this please, I cannot see this data on the Case Issue.

We appear to be back up now.

Yes, we're still seeing the same error.

Not in the UK - all fine here

I'm now seeing "An unexpected error has occurred. Please go back and try again." when trying to login. Started at 7.20am BST. Everything appears to be offline.

Can we please have an update regarding: a] What caused the outage b] What measures are being taken to prevent it happening again. Taking our entire business offline for nearly 3 hours isn't something we can simply consider as "it was broke, we've now fixed it" - we have both directors and investors to whom we are…

We've not had any official update - but we've not had a timeout error for over 2 hours now. Hoping this means they've got a fix in place - gonna be seriously pi**ed if this comes back.

This is already open on Defect #251246 - Web Services > Response time is extremely slow

We've seen the same issue, so far we've only see it on Inventory Transfers and Deposits - already opened a case - 1680061.

Sadly we have a similar issue, our main auto-billing script is failing to run at all :( Seems to have kicked off at around 5-7am BST

Looking OK from here - been logged into system2 all morning

Likewise, would highly recommend a Basic Saved search, which then triggers an email. Nice and simple, very effective.

Also, worth looking to see if any custom fields with default sourcing/formulas were recently set up. Had a similar problem with one of these - The default value was sourcing from a field which didn't always exist - so sometimes failed, sometimes didn't.