GitHub mitigates errors affecting pull requests, Git operations and issues

GitHub first reported investigating degraded performance at 09:49 UTC on November 4th. At 11:30 UTC it said degradation affecting API Requests, Git Operations, Issues and Pull Requests had been mitigated and that it was monitoring stability; that update did not say Actions had recovered.

By · Published

Primary source: Hacker News

Why it matters

Pull Requests, Git Operations, Issues, Actions and API Requests form the hosted path from writing code to reviewing, checking and shipping it. When those services degrade together, teams can keep coding locally while merges, automation and integrations may fail or be delayed.

An illuminated GitHub Octocat sign is mounted on a stone wall beside glass doors, overlooking a wet terrace and a sunset skyline.

GitHub, co-founded by Chris Wanstrath, said degradation affecting API Requests, Git Operations, Issues and Pull Requests had been mitigated by 11:30 UTC on November 4th, and that it was monitoring stability, according to its incident page. GitHub first reported investigating degraded performance at 09:49 UTC; the status updates do not establish when customer impact began.…

When you purchase through links in our articles, we may earn a small commission. This doesn’t affect our editorial independence.

Reader comments

Conversation for this story loads after sign-in.