A duplicate document somehow made it into a collection with a unique index. I did not discover that this occurred for some time – after an ensureIndex call on the collection failed. Both inserts occurred at about the same time – the timestamps for their respective ObjectId's are equivalent. What is strange is that two inserts were not actually executed against the collection, yet somehow two duplicate records ended up in the collection.