x86a

I think most enterprises that make the switch aren't moving to another cloud product. They're self hosting it. Otherwise, yeah, you are subject to the same types of outages.

We've had very few noteworthy incidents self-hosting GitLab. We can size our deployments as we need, and perform upgrades during maintenance windows we control.

Claude/codex has made the stickiness much less of a problem. We just say "no new repos in GitHub" and then put agents on refactoring the existing repos for GitLab compatibility.

Self-hosted gitlab works great for us

This is such a myopic take

Go take a flamegraph of your most CPU-bound system and optimize the most expensive function

My assumption is that they exist, but are now competing in a larger pool of asian and white applicants - who may have better access to extracurricular opportunities that are still considered in admissions decisions - and therefore are less likely to be admitted.

So, Grafana? ;)

That is very unrealistic. Infrastructure monitoring at that scale won't even be collecting metrics at that interval.

And simple HTTP monitoring would be too flappy for a public status page.

This is intentional. It's mostly a matter of discussing how to communicate it publicly and when to flip the switch to start the SLA timer. Also coordinating incident response during a huge outage is always challenging.

Maybe I've been ruined by the internet, but a grandma didn't write this.

I don't think this is ever a good idea. Even for non-enterprise use cases, you wouldn't want some public hotspot to be able to inject random garbage into responses, even if not done with malicious intent.

As a solidly-middle-class tech worker in Massachusetts, your stance hurts a bit.

I'm a life-long renter with a family and elderly mother to support, and an IPO windfall would give me some much needed breathing room.

I don't know who you picture when you think of a windfall recipient, but I can assure you I am not lighting any cigars with $100 bills.