Awesome use of load balancing for request retry across multiple backend servers: > This was caused by the CMS (Certificate Management System), when it sent the

Awesome use of load balancing for request retry across multiple backend servers: > This was caused by the CMS (Certificate Management System), when it sent the signing request of the certificate to the signing server A, which had no response, then the CMS sent it to the other newly added signing server B. After a while the signing server A signed the certificate and sent to the CMS and also to the subscriber, then the subscriber installed the cert in its website and hat's why Censys recorded this certificate; in the meantime, the signing server B also signed this certificate some time later (in seconds) and sent it to the CMS, the CMS accepted it and rewrote it in the DB. > This issue happened after adding another signing server on Jan 5th 2015, and found it on April 9th 2015. When had the two signing servers added a load balancer, but the configuration was not properly done because it didn't lock the request. Mind you, that's a perfectly legit technical bug. Maybe they were using nginx for load balancing POST requests? :) https://news.ycombinator.com/item?id=11217477 https://news.ycombinator.com/item?id=11217477