21,228 outages in February - Here are the biggest:
Last checked from GitHub Actions official status page 45 sec. ago
Collaborative platform for software development and version control.
Not working for you?
StatusGator last checked the status of GitHub on and the service was operational. There have been 133 user-submitted reports of outages in the past 24 hours, but the outage is now resolved.
This chart represents GitHub Actions service health over the last 24 hours, with data points collected every 15 minutes based on issue reports, page visits, and signal strength. Sign up for free to see more GitHub Actions status data.
24 hrs ending
View and upvote the most commonly reported GitHub Actions issues to help us better indicate the service status.
Have a different problem with GitHub Actions?
See recent outage reports from real GitHub Actions users
31 outage reports in the last 24 hours
Lombardy, Italy
Slow performance
9 minutes ago
9 minutes ago
Bourgogne, France
Server not responding
11 minutes ago
11 minutes ago
Bourgogne, France
error 500
11 minutes ago
11 minutes ago
Bern, Switzerland
Extremly slow answers leading to repeated timeouts
13 minutes ago
13 minutes ago
Lublin, Poland
Slow performance
14 minutes ago
14 minutes ago
Central Jutland, Denmark
Github Copilot is REALLY SLOW
22 minutes ago
22 minutes ago
Uppsala County, Sweden
Slow performance
27 minutes ago
27 minutes ago
Hesse, Germany
Slow performance
31 minutes ago
31 minutes ago
Capital Region, Denmark
Error message
about 1 hour ago
about 1 hour ago
Harjumaa, Estonia
Server not responding
about 1 hour ago
about 1 hour ago
Explore our interactive GitHub Actions outage map to monitor real-time incidents and service issues across the globe. This dynamic map highlights regions around the world affected by recent GitHub outages, giving you a clear view of performance and downtime trends.
Top reported GitHub outage locations, last 24 hours:
StatusGator detects outages before they are officially acknowledged by providers. Here are some recent GitHub disruptions that StatusGator customers knew about before the rest of the world:
This rating evaluates how quickly GitHub acknowledges incidents, the consistency of updates, and whether reported issues align with actual service disruptions experienced by users. Learn more.
Avg. delay < 15 min
This rating evaluates how quickly GitHub acknowledges incidents, the consistency of updates, and whether reported issues align with actual service disruptions experienced by users. Learn more.
Avg. delay < 15 min
Avg. delay 15 - 30 min
Avg. delay 30 - 120 min
Avg. delay 2 - 4 hrs
Avg. delay >= 4 hrs
| Incident description | Duration | StatusGator detected | Officially acknowledged |
|---|---|---|---|
| GitHub Copilot not responding | 3h 18m |
Never acknowledged
|
|
| GitHub Copilot unavailable due to global rate limiting errors | 1h 49m |
Never acknowledged
|
|
| Home page showing errors and displaying 401 and unicorn errors | 32m |
5m later
|
|
| Repository access and login issues due to server errors | 2h 6m |
1m later
|
|
| Github Copilot not working due to server errors. | 1h 17m |
7m later
|
|
| Github Copilot requests failing due to unsupported API version | 1h 2m |
Never acknowledged
|
|
| Copilot returning 502 errors on requests. | 1h 12m |
Never acknowledged
|
|
| Service unavailable due to server errors | 24m |
4m later
|
|
| Copilot service unavailable | 1h 27m |
18m later
|
|
| 504 gateway timeout errors affecting service availability | 1h 21m |
Never acknowledged
|
| Incident Name | Duration | Started | Severity |
|---|---|---|---|
|
Elevated delays in Actions workflow runs and Pull Request status updates
|
12h 35m |
Warn
|
|
|
Elevated delays in Actions workflow runs and Pull Request status updates
|
15m |
Warn
|
|
|
Disruption with some GitHub services
|
35m |
Warn
|
|
|
Degraded performance for various services
|
1h |
Warn
|
|
|
Actions failures to download (401 Unauthorized)
|
1h 20m |
Warn
|
Stay updated with instant alerts for GitHub Actions outages by signing up now!
You can also monitor any service or website on your status page
Stay updated with instant alerts for GitHub Actions outages by signing up now!
With features designed to cover all your needs for monitoring and communicating outages or downtime, StatusGator keeps your team connected and informed. Stay updated on GitHub Actions outages, potential problems, and its current status in real-time, ensuring you're always prepared to act.
StatusGator monitors over 7,430 cloud services, hosted applications, and websites. Just add what you need to the list, and we'll automatically aggregate their statuses into a single page. You'll receive notifications for any issues affecting you and your page subscribers.
StatusGator monitors all of your services and websites and sends your team instant notifications when they go down. Stay abreast of issues that affect your team with notifications: in email, Slack, Teams, or wherever your team communicates.
Easily notify your end-users of outages using a customizable status page. Display cloud services or websites, as well as any custom monitors you add manually. Create multiple status pages tailored to different needs, customize them, and embed them for maximum effectiveness.
GitHub Actions (Collaborative platform for software development and version control) is a a DevOps solution that StatusGator has been monitoring since March 2015. Over the past about 11 years, we have collected data on on more than 2,461 outages that affected GitHub Actions users. When GitHub Actions publishes downtime on their status page, they do so across 11 components using 4 different statuses: up, warn, down, and maintenance which we use to provide granular uptime metrics and notifications.
If you're wondering, "Is GitHub Actions down?", or need to know its current status, we've got you covered. Our platform tracks every reported outage, performance issue, and maintenance window to ensure you're informed. Whether GitHub Actions is experiencing a problem now or has recently resolved one, our detailed history keeps you updated.
More than 3,200 StatusGator users monitor GitHub Actions to get notified when it's down, is under maintenance, or has an outage. This makes it one of the most popular DevOps services monitored on our platform. We've sent more than 819,900 notifications to our users about GitHub Actions incidents, providing transparency and peace of mind. You can get alerts by signing up for a free StatusGator account.
If we detect a potential GitHub Actions outage or other issue before it was reported on the official status page we will send an Early Warning Signal notification to StatusGator subscribers. We can often detect issues before they are officially acknowledged by the provider, giving you a head start on resolving any potential problems.
If GitHub Actions is having system outages or experiencing other critical issues, red down notifications appear on the status page. In most cases, it means that core functions are not working properly, or there is some other serious customer-impacting event underway.
Warn notifications are used when GitHub Actions is undergoing a non-critical issue like minor service issues, performance degradation, non-core bugs, capacity issues, or problems affecting a small number of users.
GitHub Actions posts separate notifications for planned maintenance work. StatusGator will notify subscribers when GitHub Actions enters a pre-planned maintenance window, keeping you up to date.
When GitHub Actions posts issues on their status page, we collect the main headline message and include that brief information or overview in notifications to StatusGator subscribers.
When GitHub Actions has outages or other service-impacting events on their status page, we pull down the detailed informational updates and include them in notifications. These messages often include the current details about how the problem is being mitigated, or when the next update will occur.
Because GitHub Actions has several components, each with their individual statuses, StatusGator can differentiate the status of each component in our notifications to you whenever a particular component is down. This means, you can filter your status page notifications based on the services, regions, or components you utilize. This is an essential feature for complex services with many components or services spread out across many regions.
Stay updated with instant alerts for GitHub Actions outages by signing up now!
Can't find your question? Email us to arrange a time to discuss. We'd love to chat!
