We are just as, if not more, frustrated with how long this syncing issue has taken to get rectified. Unfortunately, this isn't under our control. This is an Amazon AWS issue that we are working with Amazon to correct and as you can probably guess, they are moving at a snail's pace and we get the impression this problem isn't ranking very high on their priority schedule. We will continue to push them to correct this issue but, as it stands now, our hands are tied until they correct their problem.
UPDATE: We have moved on from waiting on Amazon to correct their issue and now are working on a Plan B. Our developers are rewriting the sync so it is taking more time than expected. We are testing now.