Last checked from GitHub Packages official status page 58 sec. ago
GitHub Packages Status
Collaborative platform for software development and version control.
Not working for you?
Is GitHub Packages down?
GitHub Packages is up
Not working for you?
StatusGator last checked the status of GitHub on and the service was operational. There have been 1282 user-submitted reports of outages in the past 24 hours, but the outage is now resolved.
GitHub Packages service health graph
Shows recent status reports over time, including possible and confirmed outages.
This chart represents GitHub Packages 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 Packages status data.
GitHub Packages outage reports
Lists recent GitHub Packages incidents, including duration, acknowledgement status, and severity.
5,769 outage reports in the last 24 hours
Recent community and social reports
Antioquia, Colombia
"Continue Down!"
• about 2 hours ago
Arizona, United States
"Copilot still down, can't sign in "
• about 3 hours ago
Bogota D.C., Colombia
"down"
• about 3 hours ago
National Capital Territory of Delhi, India
"Sorry, your request failed. Please try again. Client Request Id: hidden Reason: key is missing Note: GitHub is currently experiencing a service disruption. This may be affecting Copilot. Check GitHub Status for details."
• about 3 hours ago
California, United States
"copilot not working at all"
• about 3 hours ago
Michigan, United States
"Copilot not working and some website areas working inconsistently"
• about 3 hours ago
Prague, Czechia
Sign in problem
• about 3 hours ago
California, United States
"Sorry, your request failed. Please try again. Client Request Id: {hidden} Reason: key is missing"
• about 3 hours ago
Punjab, India
"In India Its down"
• about 3 hours ago
West Bengal, India
"NOT WORKING "
• about 3 hours ago
State of Vienna, Austria
"Language model unavailable"
• about 3 hours ago
Massachusetts, United States
"This blows. Down all day"
• about 3 hours ago
Tyrol, Austria
"completely down"
• about 3 hours ago
Oklahoma, United States
"No connection inside of IntelliJ. Keep saying it was unable to authenticate workflow"
• about 3 hours ago
England, United Kingdom
Service down
• about 3 hours ago
Saxony-Anhalt, Germany
"copilot down"
• about 4 hours ago
Karnataka, India
Service down
• about 4 hours ago
ÃŽle-de-France, France
"Yup, Copilot in VSCode not working here either. Good luck with the bug fix, and until then happy hand coding everyone !"
• about 4 hours ago
Friesland, The Netherlands
"github copilot"
• about 4 hours ago
Karnataka, India
"still not able to access github copilot from VSCode or Intellij IDE "
• about 4 hours ago
Top reported outages
Having a different problem?
Get notified about GitHub Packages outages
Stay updated with instant alerts for GitHub Packages outages by signing up now!
GitHub Packages outage map
Displays regions where users have recently reported issues. Map markers are based on user-submitted reports.
View full map
GitHub Packages incidents history
Lists recent GitHub Packages incidents, including duration, acknowledgement status, and severity.
View more history
| Incident Name | Duration | Started | Acknowledged | Severity |
|---|---|---|---|---|
|
Actions failing due to gateway errors
|
66d 18h 1m | Yes, 44m delay |
Down
|
|
|
GitHub Copilot login and connection issues
|
5h 53m | No |
Warn
|
|
|
Copilot service unavailable
|
55m | No |
Warn
|
|
|
Language model unavailable
|
14h 42m | No |
Warn
|
|
|
Service outage
|
53d 14h 31m | Yes, 36m delay |
Down
|
|
|
GitHub Copilot not responding
|
2h 56m | No |
Warn
|
|
|
GitHub Copilot unavailable due to global rate limiting errors
|
53m | No |
Warn
|
|
|
Github Copilot requests failing due to unsupported API version
|
31m | No |
Warn
|
|
|
Copilot returning 502 errors on requests.
|
22m | No |
Warn
|
|
|
504 gateway timeout errors affecting service availability
|
1h 17m | No |
Warn
|
|
|
Service unavailable due to server errors.
|
79d 21h 9m | Yes, 43m delay |
Down
|
|
|
Service unavailable due to 504 gateway errors.
|
30m | No |
Warn
|
|
|
504 Gateway Timeout errors
|
15m | No |
Warn
|
|
|
Pull requests unable to merge or rebase.
|
8m | No |
Warn
|
|
|
Cannot push or pull from private repositories.
|
28d 3h 38m | Yes, 6m delay |
Warn
|
|
|
GitHub Copilot and AI features not working in VS program.
|
7m | No |
Warn
|
|
|
Cannot push changes via SSH
|
24m | No |
Warn
|
|
|
Copilot chat not working in VS Code
|
34m | No |
Warn
|
|
|
Repository access and performance issues
|
20m | No |
Warn
|
|
|
Server not responding
|
1m | No |
Warn
|
GitHub Packages status history
Shows daily GitHub Packages status over recent days, including uptime, warnings, and outage events.
Warning for 8 Hours and 58 Minutes
Warning for 1 Day
Warning for 1 Day
Warning for 1 Day
Warning for 22 Hours and 42 Minutes
Warning for 8 Hours and 58 Minutes
Warning for 1 Day
Warning for 1 Day
Warning for 1 Day
Warning for 22 Hours and 42 Minutes
GitHub Packages status page accuracy
Learn moreGitHub status page accuracy rating
This rating evaluates how quickly GitHub acknowledges incidents, the consistency of updates, and whether reported issues align with actual service disruptions experienced by users.
| Rating grade | Average delay |
|---|---|
|
A
Excellent
|
< 15 min |
|
B
Good
|
15 - 30 min |
|
C
Fair
|
30 - 120 min |
|
D
Poor
|
2 - 4 hrs |
|
F
Failing
|
>= 4 hrs |
Get notified about GitHub Packages outages
Stay updated with instant alerts for GitHub Packages outages by signing up now!
Looking for Downdetector GitHub Packages alerts?
| Features | StatusGator | Downdetector |
|---|---|---|
| Both official and crowdsourced updates for GitHub Packages outages. |
|
|
| More than 10,250 services monitored. |
|
|
| Proactive alerts on GitHub Packages status changes sent to your Slack, Microsoft Teams, and more. |
|
|
| Monitoring of both GitHub Packages and your own apps. |
|
|
| Granular monitoring of GitHub Packages components. |
|
|
About our GitHub Packages status page integration
GitHub Packages (Collaborative platform for software development and version control) is a a DevOps solution that StatusGator has been monitoring since March 2015. Over the past over 11 years, we have collected data on on more than 2,764 outages that affected GitHub Packages users. When GitHub Packages publishes downtime on their status page, they do so across 12 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 Packages 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 Packages is experiencing a problem now or has recently resolved one, our detailed history keeps you updated.
More than 3,400 StatusGator users monitor GitHub Packages 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 946,600 notifications to our users about GitHub Packages incidents, providing transparency and peace of mind. You can get alerts by signing up for a free StatusGator account.
-
Early Warning Signals
If we detect a potential GitHub Packages 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.
-
Down Notifications
If GitHub Packages 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.
-
Warning Notifications
Warn notifications are used when GitHub Packages 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.
-
Maintenance Notifications
GitHub Packages posts separate notifications for planned maintenance work. StatusGator will notify subscribers when GitHub Packages enters a pre-planned maintenance window, keeping you up to date.
-
Status Messages
When GitHub Packages posts issues on their status page, we collect the main headline message and include that brief information or overview in notifications to StatusGator subscribers.
-
Status Details
When GitHub Packages 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.
-
Component Status Filtering
Because GitHub Packages 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.