this happened already last night about 3:00 am (germany)

Frankly, it isn't the uploading problem that is the biggest issue, aside from that the biggest problem is the completely incompetent image reviewer problems. That problem is getting worse. I'd thought I try them out with just a few images having boycotted the entire process for eight weeks. All non-approved for an absolutely ludicrous reason and I mean ludicrous.

"Model release is required"

.......... for food images with nobody in them - just macros of food. No hand, no finger, no plate no utensils, just salad leaves and feta cheese 

Unbelievable.

Just completely and totally incompetent.

EDIT - They can't even post the problem they admit to having properly, the whole place is falling apart.

Does this cause reporting delays?

Hi All,

We experienced some network latency issues today.  New uploads are currently working, but images uploaded earlier today may temporarily appear as broken thumbnails in your account.   Please **do not** delete those images; they should populate correctly into your account within the next 12-24 hours. 

Thank you for your patience and we sincerely apologize for any inconvenience!

Best,

Scott
VP of Content
Shutterstock

Really you are calling server sync issues "network latency issues"?

LOL

Snip

Lets multiply some actual network latency durations by a billion:

L1 cache reference                  0.5 s         One heart beat (0.5 s)
Branch mispredict                   5 s           Yawn
L2 cache reference                  7 s           Long yawn
Mutex lock/unlock                   25 s          Making a coffee
Main memory reference               100 s         Brushing your teeth
Compress 1K bytes with Zippy        50 min        One episode of a TV show (including ad breaks)
Send 2K bytes over 1 Gbps network   5.5 hr        From lunch to end of work day

Latency numbers every programmer should know

L1 cache reference ......................... 0.5 ns
Branch mispredict ............................ 5 ns
L2 cache reference ........................... 7 ns
Mutex lock/unlock ........................... 25 ns
Main memory reference ...................... 100 ns             
Compress 1K bytes with Zippy ............. 3,000 ns  =   3 �s
Send 2K bytes over 1 Gbps network ....... 20,000 ns  =  20 �s
SSD random read ........................ 150,000 ns  = 150 �s
Read 1 MB sequentially from memory ..... 250,000 ns  = 250 �s
Round trip within same datacenter ...... 500,000 ns  = 0.5 ms
Read 1 MB sequentially from SSD* ..... 1,000,000 ns  =   1 ms
Disk seek ........................... 10,000,000 ns  =  10 ms
Read 1 MB sequentially from disk .... 20,000,000 ns  =  20 ms
Send packet CA->Netherlands->CA .... 150,000,000 ns  = 150 ms

https://gist.github.com/hellerbarde/2843375

Quote from: Goofy on June 18, 2014, 08:49

acceptance rate has nothing to do with network issues thus try to keep on topic here...

Latency, sync problems, explains why a message there might have the wrong ID on the header for a minute which a couple of people turned into some conspiracy that SS is accessing member accounts. Leap of reason that faile. Does the crying ever end?

Scott came to tell us do not delete images missing thumbnails and it turns into another complaint about reviews. Stupid.

I know what you mean, but......

I added the review debacle (as far as it concerned me today) specifically as this thread was initiated by Scott Braunt, and presumably, he will come back and check on it from time to time.

The reason I wanted him to see my specific comment was that he is completely ignoring the threads over at SS discussing the review conundrums at this time. To the point where direct pleas are being posted to him directly to respond.

He has continuously failed to do so.

That was why I posted 'the off-topic' comment here, I don't normally due that sort of thing, it was borne simply out of frustration.

I hope that explains why I did it.

I wasn't trying to be 'stupid' as you put it.

Error started for me also in the last couple of days. So I switched to the web uploader.

Upload over the web yields less broken thumbnails than ftp upload.

This problem has been occurring since at least 2007 and shutterstock is fully aware of this fact.

The thread link below in the shutterstocks bug forum is filled with missing images and thumbs caused by essentially the same problem. And yet over the last 4 years shutterstock has done nothing to resolve these server/database issues. Server sync problems continue to pop up in one form or another year after year.

How many years do you expect contributors to deal with the issues and extra work your server/database problems are causing?

For example in just one thread you have 137 pages and thousands of instances of the same glitch causing contributors extra work and lost sales.

For Missing Images, PLEASE USE THIS THREAD
http://submit.shutterstock.com/forum/viewtopic.php?t=114196

I would like and honest answer, when do you expect to be able to resolve this problem?  Are you willing to do what it takes to put a nail in it once and for all or do you just expect us to put up with the lost productivity and sales, these server sync/database issues cause for us indefinitely?

Unfortunately most people do not have experience working with databases and online applications.

They would buy your above sidestep of ongoing issues that you fail to address year after year. I do expect you to address the issues because it is not fair to contributors to let them go on indefinitely and if you are honest with yourself you know it is not right to let these issues continue.