No, and yes.
Facebook, hidden services, and https certs had talked on this. Facebook in fact brute forced only the first 40 bits and then made a backronym.
Their hidden service name is "facebookcorewwwi.onion". For a hash of a public key, that sure doesn't look random. Many people have been wondering how they brute forced the entire name.
The short answer is that for the first half of it ("facebook"), which is only 40 bits, they generated keys over and over until they got some keys whose first 40 bits of the hash matched the string they wanted.
Then they had some keys whose name started with "facebook", and they looked at the second half of each of them to pick out the ones with pronouncable and thus memorable syllables. The "corewwwi" one looked best to them — meaning they could come up with a story about why that's a reasonable name for Facebook to use — so they went with it.
So to be clear, they would not be able to produce exactly this name again if they wanted to. They could produce other hashes that start with "facebook" and end with pronouncable syllables, but that's not brute forcing all of the hidden service name (all 80 bits).
However, when facing a really strong adversary, 80 bits is not enough. A high-end GPU (like a GTX 1080) can yield a hash rate at about 4 GHash/s, and specially designed ASICs go far beyond this. (See https://github.com/lachesis/scallion#speed--performance for more.) Although the public key generation would slow down the hash rate, an attacker with enough resource is able to achieve a few PHash/s, at which a full collision becomes feasible.
And there is another caveat. Partial collisions are also useful. Assuming you are not always memorizing the full address, an attacker could just mess up your memory and get you to visit their fake HS.