Urgent.News

the world's headlines, one feed

Editions

Tech

Latest GitHub outage squeezes Actions, Pages to death

Look over there, Copilot - it's a beautiful AI farm where you can tend some digital rabbits

Latest GitHub outage squeezes Actions, Pages to death

GitHub's automation platform, Actions, and hosting service Pages are currently experiencing severe stability issues, as reported on the service's status site. The problems began on Thursday at 1522 UTC, with Actions suffering from degraded performance, and availability becoming compromised about 20 minutes later. GitHub stated that workflow runs were failing to initiate or were incomplete, and requests to the Actions REST API were returning errors. Users also encountered unexpected rate limits.

The root cause of the issue has not been officially disclosed, but it was acknowledged shortly after the problem was first reported. GitHub began applying mitigations and rolled out a fix across all affected systems shortly after 1740 UTC on Thursday. However, the problem has not yet been fully resolved, and Pages has now been added to the list of impacted systems.

The ongoing issues with GitHub's platform add to a history of stability problems. According to the status history page, the service has faced numerous incidents over recent months. In July alone, a single outage was reported, with 26 incidents logged. The months of June, May, and April saw 23, 23, and 26 incidents respectively. As of August 6, the status page lists six total incidents for the month, highlighting the recurring nature of the problems.

This latest GitHub outage has prompted many developers to reconsider using the platform for their projects, with some even calling it "unstable" for hosting "serious work." GitHub's apologies for the frequent outages have not seemed to improve the situation, leading to widespread frustration among the developer community.

Written by urgent.news from The Register's reporting — not their text. Machine-written — it may contain errors, so check the original before relying on it.

This story

This is one outlet's version. Read the fullest account.

Read the original at theregister.com →

More in Tech

Where exactly is the card in this photo? Image segmentation model inside a maxed-out lambda container

A crooked phone photo goes in, a clean straight card image comes out - no GPU, and nothing running when nobody uploads. It runs on the biggest lambda AWS sells, and the biggest is not the same as…

  • BiRefNet-General-Lite model used for image segmentation
  • Memory constraints addressed by reducing container memory and resizing images
  • Model chosen for efficient CPU-based segmentation in Lambda container

JWT auth without the confusion

JWT auth without the confusion JWTs are everywhere, but they're often misunderstood. Let's strip away the jargon and see what they actually are, how they work, and how to use them safely in your apps.

  • JWTs consist of three segments: header, payload, and signature
  • Authentication involves login, token creation, and token inclusion in requests
  • Avoid storing tokens in localStorage due to XSS vulnerability

Building Resilient Real-Time Systems: WebSockets, Redis, and High Availability Architectures

Originally published on tamiz.pro . Building real-time systems that are not only fast but also resilient and highly available is a critical challenge in modern software architecture.

  • WebSockets provide persistent bidirectional communication for real-time applications
  • Redis serves as a message broker with Pub/Sub mechanism for state and messaging
  • High availability achieved through horizontal scaling, Redis Sentinel, and clustering