Even in the case you have a very well federated system with users very dispersed and the federation had 100% uptime and no bugs... how does it affect uptime for users? A central server going down 1% of the time for all users is the same as 1,000,000 decentralized servers being down 1% of the time for their 1/1,000,000 users. Nobody cares others can use the service during an outage they care they can use the service.
Federation capability at the protocol (even if it's not used in a truly federated way) provides a lot of great features, uptime for users isn't really one though. The most relevant is probably when Signal shuts down intentionally (tomorrow or 1,000 years from now, doesn't matter) you can't just migrate to a different Signal server without all of your contacts moving to the same one. This is akin to taking your /24 with you to your new ISP, porting your phone number to a new phone provider, or taking your custom domain email from Gmail to a different host and the ability to do that on those federated systems is probably why they remain in use today.
If so, may I suggest you read Antifragile?
There are other valid lessons for why choose decentralized but this is not a "ha, got'em" moment for that. There are also valid pros for centralized as well, hence their real world success and the reason most "decentralized" tech ends up being run in a very centralized fashion when it matures.