Live data from Hacker News

Error 404 (Not Found)

spotify.com

191–197 of 197 posts

Re: Error 404 (Not Found)

#191
post #183

Earlier quoted context omitted.

Which is dumb, linking to status pages shouldn't be on HN. A blog that has analysis and explanations of outages or post mortems should. knock-knock dang

Dang doesn't see messages like that unless you use the footer Contact link, but I remember a comment from him a while back that I would summarize as "Some site users think it's a good use of HN, and other site users disagree and flag it, and we downweight/dedupe them sometimes and/or if someone emails us with the Contact link". I just didn't want you to wait for a reply that'll never come unless you Contact them.

hehe I know, was just saying more for fun, but I appreciate the comment none the less.

Re: Error 404 (Not Found)

#192
post #28

Earlier quoted context omitted.

When Spotify went down I switched to Youtube Music. Funny how that's still running but Spotify isn't, if it is in fact a Google issue.

Internal Google infra and GCP are different beasts. Sure some failure modes take both down but more likely than not they are independent.

That's why many choose AWS, they eat their own dog food.

Re: Error 404 (Not Found)

#193
post #188

Earlier quoted context omitted.

...and there's a reason for that. Automations to update the status page are rarely acceptable, since the status page statuses have legal and financial implications. Therefore, the IM usually has to update it (or tell someone to update it). But, realistically, when you get paged, you first need to figure out what exactly is wrong and at least a vague idea of why. Then, you need to tell someone to update the page. Then…

Not updating the status page, to avoid the legal and financial implications, is fraud -- taking money on false pretenses.

fraud? how? what guarantees do they make about timeliness of status updates on their services?

Re: Error 404 (Not Found)

#194
post #180
post #172

Earlier quoted context omitted.

That only says spotify.com is using GCP's DNS but not necessarily for hosting? EDIT: I was wrong, as pointed out by shizcakes.

While we are at it, looks like spotify.com is using a mix of NS1 and GCP for DNS. spotify.com. 172800 IN NS dns1.p07.nsone.net. spotify.com. 172800 IN NS dns2.p07.nsone.net. spotify.com. 172800 IN NS dns3.p07.nsone.net. spotify.com. 172800 IN NS dns4.p07.nsone.net. spotify.com. 172800 IN NS ns-cloud-a1.googledomains.com. spotify.com. 172800 IN NS ns-cloud-a2.googledomains.com. spotify.com. 172800 IN NS ns-cloud-a3.go…

How can you name your service NS1 but then not use the ns1. subdomain for the first nameserver. SMH

Re: Error 404 (Not Found)

#195
post #178
post #160

Earlier quoted context omitted.

It's Google though.. they stop automating everything? At least make the screen not show all green or something automatically

Which things should not be green? If the automation is working the services will be up. When an incident is happening it's because something is significantly broken , and automation won't properly understand what is and is not working. For instance, lots of follow-on alarms might be firing for what are not actually issues with the things being monitored: As an example, I would imagine that datacenter temperatures and…

> Which things should not be green?

The broken ones is how I usually do it.

The automation doesn't need to do that, it doesn't need to analyse the situation. It needs to communicate "Hey. Our systems have seen this and have pinged humans, bear with" rather than "nope even though half the internet is down rn, it's all good baby"

Make a green tick a blue questionmark or something. It doesn't even need to admit fault, it just needs to not be useless. My goal visiting the page is to get a link I can send clients "Updates will be posted here". Nothing more.

Also if you're hosting your monitoring system on the same system it's monitoring you've just completely missed the point. At least use a different region within your cloud provider, better would be completely different provider. I'd even go as far as using different domains/TLDs to host the page if I was Google sized

Re: Error 404 (Not Found)

#196
I don’t understand why people post website outages.

Do you think the DevOps teams at these billion dollar streaming companies are so clueless that they don’t have monitoring in place?

Do you think that people who go to a site when it’s down don’t see the same thing?

So whose awareness does this serve?

Re: Error 404 (Not Found)

#197

I don’t understand why people post website outages. Do you think the DevOps teams at these billion dollar streaming companies are so clueless that they don’t have monitoring in place? Do you think that people who go to a site when it’s down don’t see the same thing? So whose awareness does this serve?

In general, people post things on HN to discuss them. This includes high profile web outages.
Post reply on HN