It's the same on Mac OS. As I said, it's not necessarily the 'server overload' issue as much as buggy software.
Yup, definitely buggy software. One of my OS X computers with a CC subscription picked up the latest updates, another required a reboot before it could find them—presumably because one of the Adobe updating processes was blocked (probably by another of the Adobe processes).
And, as I've noticed following other recent Adobe updates, the update mechanism fails to unmount the patches for each product after the update is complete:
/dev/disk2s2 on /Volumes/AdobeCameraRaw-9.1.1-CC-mul-AdobeUpdate (hfs, local, nodev, nosuid, read-only, noowners, nobrowse)
/dev/disk3s2 on /Volumes/Lightroom-6.1.1-Update (hfs, local, nodev, nosuid, read-only, noowners, nobrowse)
This isn't harmful, per se, but it's indicative of sloppy programming.
I wonder if Adobe and its customers would be better served by scrapping the multi-product updater and simply having each application poll for its own updates at launch time or, for apps that have been executing longer than 24 hours, once a day.