I know this because it happened to us. We contacted them about it but they have no solution,they don't seem to think it's a problem since "most of the time" their servers are up and quite fast. Marketing requires the tracking, so our solution is to host their javascript on our server and run a cron nightly to redownload the code from their servers in the hopes that we'll never get so far behind that the tracking stops working. So far, so good.
Google, on the other hand, offers an asyncronous, non-blocking solution. Much better.
But the tracking code is small. It's not going to make much difference at all IMHO (And anecdotally in my experience).
Async vs sync, you're still going to have a DNS lookup, and an initial GET unless it's cached. Both can block your site from loading...
By comparison, google tracking code is unfortunately massive. It sets a ton of cookies, which are then sent with every single request to your server. Wasting bandwidth. It's worse if you have it on subdomains, since then it'll set even more cookies, and send even more crap to your server every single request.
For a website with a large number of reloads, or ajax or comet, this can be a complete killer.