31–40 of 176 posts
And now they're blaming their upstream vendor! Embarrassing stuff to be writing on a public page.
GitHub needs to completely bifurcate their enterprise/paid services from their free services at the infra level.
enterprise is mostly separate, is it not? uptimes are significantly more reasonable on the enterprise status pages
> We've identified an issue with a database primary and are failing over to a replica immediately This is why it's hard to take GitHub seriously. How can a single database cause an outage for everyone? This is amateur stuff. Have they no sharding or partitioning internally? Paying customers should not be impacted in the same way as free ones are.
I wonder what is this database, and why it is hard to fall-over automatically.
> primary failover briefly improved performance but did not fully mitigate, we've throttled inbound traffic and are investigating upstream Vitess issues
We can't keep living like this.
I wonder if it was down that much, if users would get credits the way we pay when we use the services - its kind of ridiculous for a critical service to be down that much and all we do is "ah okay, its just github". Like, as if that was normal to be down that much...
>Update - primary failover briefly improved performance but did not fully mitigate, we've throttled inbound traffic and are investigating upstream Vitess issues And now they're blaming their upstream vendor! Embarrassing stuff to be writing on a public page.
>Update - primary failover briefly improved performance but did not fully mitigate, we've throttled inbound traffic and are investigating upstream Vitess issues And now they're blaming their upstream vendor! Embarrassing stuff to be writing on a public page.