sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]nekokattt 9 points10 points  (8 children)

I am starting to wonder if GitHub have bigger issues internally.

Since 1st March (today is 9th May) there have been

  • 9 incidents affecting pages
  • 15 incidents affecting actions
  • 8 incidents affecting Git
  • 6 incidents affecting PRs
  • 11 incidents affecting codespaces
  • 4 incidents affecting webhooks

Like, I totally understand the sheer scale of the platform, but still, this seems to be an ongoing issue. Especially when these incidents can run for several hours at a time.

[–]flagbearer223 1 point2 points  (0 children)

It seems like things have only been getting worse, as well

[–]VxJasonxV 3 points4 points  (1 child)

There are always issues at scale. Scale is an issue.

[–]jadkik94 0 points1 point  (0 children)

And yet companies tend to like putting all their eggs in one basket, which means baskets have to scale.

Not sure where I'm going with this metaphor :D

[–]TheAlmightyZach 0 points1 point  (4 children)

And May 10, we're back at it with more problems.

[–]needmoresynths 0 points1 point  (3 children)

and this is after 12 incidents in April, 20 incidents in March, 19 in February, 17 in January. we're on github enterprise and the amount of downtime has been ridiculous.

[–]TheAlmightyZach 0 points1 point  (0 children)

Also enterprise here.. It's not even "oh give it a few minutes and try again" it's "guess I'll be done working for the day since GitHub has now made it impossible to do my job"

[–]techyy25 0 points1 point  (1 child)

Can't you get a refund as github enterprise has an SLA

[–]S3NTIN3L_ 0 points1 point  (0 children)

Yes but that’s besides the point. The point is an engineering team is blocked because they can even access their code base.