[peterwwillis]

If by "name" you mean hostname, not really. If you have a domain with multiple nameservers in multiple countries on multiple providers, and your site is similarly globally distributed, at least a few people on the internet will always be able to pull up your site. So at least some of your clients will be able to resolve a domain address from at least some of your nameservers and connect to at least some of your web servers. Geo-IP and Anycast are also really useful here.

edit: It's possible that you could take out an entire TLD and make it impossible to resolve domains on that TLD once all the cached records expire. But that kind of targeted attack would not be possible with a BGP error, unless it was a very specifically crafted BGP error happening over a very long period of time (weeks-months-years depending on the record TTLs).

[po]

ok, that makes sense but you'd still at least have: if the site is down due to BGP then so is the status page that is on the same domain.

I guess I'm just calling out the people who are making fun of them for having their status page dependent on the same hardware it's monitoring when it's not clear that's the case just because they are both down?

I would suppose if it's a different TLD domain, then it would be more likely to conclude that.

[peterwwillis]

A status page should be a static site hosted on multiple providers in multiple regions with multiple nameservers. So, Amazon S3 hosted in 2 regions, Azure Storage hosted in 2 different regions, 2 different nameserver providers in 2 different countries using two different backend colo providers. Costs probably <$150/year and that will survive BGP outages, backhaul link outages, hosting provider outages, DNS outages.

I'm not going to make fun of them for their status page being down, but it certainly doesn't reflect well on the brand/products.