3 ms·

Seems like things started to go down the drain somewhere around February 2020. https://www.githubstatus.com/uptime/kr09ddfgbfsf?page=2 https://www.githubstatus

Seems like things started to go down the drain somewhere around February 2020. https://www.githubstatus.com/uptime/kr09ddfgbfsf?page=2 https://www.githubstatus.com/uptime/kr09ddfgbfsf?page=2 Wonder what was the trigger for the reliability hit - actions went GA on nov 2019, so it's something else (or possibly a combination of things)

tjomk 6y ago
Maybe they're migrating their infra to Azure?
kenhwang 6y ago
COVID related work from home adjustments is my guess.
- kchoudhu 6y ago
  That is actually an extremely good guess, and I am ashamed I didn't think of it to begin with.
- hnlmorg 6y ago
  That might be the trigger but it wouldn't be the root cause. For example web and backend servers for cloud services shouldn't be affected by whether people are sat in one location or another. However if those systems requires lots of maintenance to keep running and people are less available due to COVID then you'd see a rise in downtime. But that would mean it's not COVID that's the problem, it's the amount of maintenance required and COVID only surfaced that problem.
  - kenhwang 6y ago
    Doesn't have to be on service side either. Could be that user patterns are changing too, testing scenarios that aren't well worn on GitHub.
deleted 6y ago
[deleted]
sairamkunala 6y ago
They started doing availability reports. Las months details in the blog post below with summary of the issue. Stay tuned till next month for the current outage. https://github.blog/2020-07-08-introducing-the-github-availability-report/ https://github.blog/2020-07-08-introducing-the-github-availa...
- victords 6y ago
  Nice, I did not know they had that! Is there a way to subscribe to this? Did not find an option for the reports neither at the Status page or at the Blog page.
steveniscom 6y ago
> Wonder what was the trigger for the reliability hit Microsoft acquisition, what can I say

tjomk 6y ago

Maybe they're migrating their infra to Azure?

kenhwang 6y ago

COVID related work from home adjustments is my guess.

kchoudhu 6y ago
That is actually an extremely good guess, and I am ashamed I didn't think of it to begin with.
hnlmorg 6y ago
That might be the trigger but it wouldn't be the root cause. For example web and backend servers for cloud services shouldn't be affected by whether people are sat in one location or another. However if those systems requires lots of maintenance to keep running and people are less available due to COVID then you'd see a rise in downtime. But that would mean it's not COVID that's the problem, it's the amount of maintenance required and COVID only surfaced that problem.
- kenhwang 6y ago
  Doesn't have to be on service side either. Could be that user patterns are changing too, testing scenarios that aren't well worn on GitHub.

deleted 6y ago

[deleted]

sairamkunala 6y ago

They started doing availability reports. Las months details in the blog post below with summary of the issue. Stay tuned till next month for the current outage. https://github.blog/2020-07-08-introducing-the-github-availability-report/ https://github.blog/2020-07-08-introducing-the-github-availa...

victords 6y ago
Nice, I did not know they had that! Is there a way to subscribe to this? Did not find an option for the reports neither at the Status page or at the Blog page.

steveniscom 6y ago

> Wonder what was the trigger for the reliability hit Microsoft acquisition, what can I say