githubstatus.com | HN Simulator

	progbits 1 day ago \| parent \| context \| on: Incident with Actions Interestingly all the separate enterprise cloud instances show the same thing: https://us.githubstatus.com/posts/details/P7VGB7I https://au.githubstatus.com/posts/details/PO54BK8 https://eu.githubstatus.com/posts/details/PRESCZY https://jp.githubstatus.com/posts/details/P0N7ZG5 What's the point of (supposedly) separate and isolated data residency deployments if they all have single point of failure?
	esafak 13 days ago \| parent \| context \| on: The GitHub wiki is an anti-pattern (2022) Yes, and the rest of it is too; there's another outage today and my CI is blocked. I guess I can read the wikis while I wait, eh?? https://www.githubstatus.com/
	shric 40 days ago \| parent \| context \| on: Nvidia agrees to acquire Hugging Face for $13B What sold you on GitHub Actions? The one 9 of reliability? https://www.githubstatus.com/
	sdetheridge 41 days ago \| parent \| context \| on: Disruption with Some GitHub Services – Resolved According to their status pages (e.g. https://eu.githubstatus.com/, https://us.githubstatus.com/), their Enterprise Cloud uptime for Actions is significantly higher.
	owebmaster 41 days ago \| parent \| context \| on: Fast drilldown dashboards from a single Parquet fi... > Agreed, for a public demo like this one, GitHub Pages would work great If you are okay with it being down regularly Edit: Ironically, that would be the case now: https://www.githubstatus.com/incidents/hcbtzksccj2f
	d0vs 46 days ago \| parent \| context \| on: The August 17 outage GH didn't collapse so it's not impossible that they already implement these measures: > At peak, web/API error rates were approximately 20%, while archive and raw-content downloads reached approximately 50%. https://www.githubstatus.com/incidents/zkxwbgr0cnmx
	dcrazy 47 days ago \| parent \| context \| on: The August 17 outage The root cause analysis is separate, but linked to from the blog post: https://www.githubstatus.com/incidents/zkxwbgr0cnmx It is specific and technical.
	rvz 47 days ago \| parent \| context \| on: The August 17 outage And another outage. [0] Looking forward to the subsequent post-mortem on that one. You might want to not go all in on GitHub anymore since it is very unstable to use. A self-hosted instance would have a far better uptime than GitHub over the years. 6 years ahead [1] on not going all in an centralizing everything on GitHub. [0] https://www.githubstatus.com/incidents/bhbcjn4n3jzp [1] https://news.ycombinator.com/item?id=22867803
	dcrazy 47 days ago \| parent \| context \| on: The August 17 outage > We installed as much hardware as available power allowed in our existing data centers while accelerating our migration to Azure. And from the RCA [1]: > The immediate cause of the failure was network saturation on load balancers in Central US due to a new peak in traffic. [1]: https://www.githubstatus.com/incidents/zkxwbgr0cnmx
	michaelbuckbee 49 days ago \| parent \| context \| on: Cursor launches Origin, GitHub alternative https://www.githubstatus.com/history
	jmkni 49 days ago \| parent \| context \| on: Degraded performance for multiple models And github today lol https://www.githubstatus.com/incidents/bmpybhnrky3x
	tomjakubowski 50 days ago \| parent \| context \| on: Incident with Github.com [resolved] Strange. The back button in the UI is disabled once you get back to September 2016. https://www.githubstatus.com/uptime/8l4ygp009s5s?page=40 The earliest recorded downtime for Git Ops I could find is in December 2018. https://www.githubstatus.com/uptime/8l4ygp009s5s?page=32
	baal80spam 50 days ago \| parent \| context \| on: Ask HN: GitHub employees what's going on? Why? > They are handling it a lot better than Github. No, they are not. https://status.claude.com/ https://www.githubstatus.com/
	crucialfelix 50 days ago \| parent \| context \| on: Incident with Github.com [resolved] It's a historical record. https://www.githubstatus.com/ is today
	MallocVoidstar 50 days ago \| parent \| context \| on: Incident with Github.com [resolved] GitHub's historical uptime page is fake, they backfilled it with 100% uptime going back to 1996: https://www.githubstatus.com/uptime?page=200
	nope1000 50 days ago \| parent \| context \| on: Incident with Github.com [resolved] At least enterprise EU is partially affected https://eu.githubstatus.com/posts/dashboard We cannot pull any actions images (or how it is called) for example.
	iamcoder18 50 days ago \| parent \| context \| on: Incident with Github.com [resolved] Yes, but GitHub enterprise has different uptime (https://us.githubstatus.com/posts/dashboard) and actually does have an SLA. Edit: it seems GHE is also affected by the outage and isn't much better.
	lini 50 days ago \| parent \| context \| on: Incident with Github.com [resolved] incident was just created - https://www.githubstatus.com/incidents/zkxwbgr0cnmx
	MallocVoidstar 50 days ago \| parent \| context \| on: Incident with Github.com [resolved] https://www.githubstatus.com/ It's all green which means it's working. Ignore the unicorn error on every page. edit: After 5-10 minutes they got around to opening an incident and (apparently manually?) marking the API as having 'degraded performance'.
	bob1029 60 days ago \| parent \| context \| on: A year of fighting scrapers on my 1.5 million-page... > the real problem is that the website is poorly built This is almost always the problem. This is currently the problem that GitHub is having too. If they had remained with their crusty old rails architecture, very little of this mess [0] would be occurring right now. They would have been able to focus all their engineering talent on scaling the product rather than inventing elaborate client side state synchronization mechanisms. [0]: https://www.githubstatus.com/incidents/qcvjkzcs7j74
	tom1337 60 days ago \| parent \| context \| on: GitHub Actions and Pages are experiencing degraded... I am not sure if all Webhooks were affected or only those regarding actions. Theres not much information given besides "Webhook deliveries may be delayed." https://www.githubstatus.com/incidents/qcvjkzcs7j74
	1vuio0pswjnm7 61 days ago \| parent \| context \| on: GitHub Actions and Pages are experiencing degraded... 49199094 \| GitHub Is Experiencing Difficulties \| https://www.githubstatus.com/?d=2026/08/06 \| https://news.ycombinator.com/item?id=49199094
	tressure 61 days ago \| parent \| context \| on: GitHub Actions and Pages are experiencing degraded... We have set up a new enterprise and are migrating to GHE. For us this was a no-brainer; we get our own isolated environment, Enterprise Managed Users with Entra OIDC provisioning and Github Copilot in EU data residency. https://eu.githubstatus.com/posts/dashboard looks pretty good to me. We will still keep our github.com enterprise around for public repositories. I’m genuinely curious to know why a company would prefer github.com over GHE?