Last checked from GitHub Issues official status page 2 min. 19 sec. ago
GitHub Issues Status
Collaborative platform for software development and version control.
Not working for you?
Is GitHub Issues down?
GitHub Issues is up
Not working for you?
StatusGator last checked the status of GitHub on and the service was operational. There have been 114 user-submitted reports of outages in the past 24 hours, but the outage is now resolved.
GitHub Issues service health graph
Shows recent status reports over time, including possible and confirmed outages.
Shows recent status reports over time, including possible and confirmed outages.
This chart represents GitHub Issues 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 Issues status data.
Service up
Possible outage
Outage duration
– StatusGator marked the possible outage resolved
– Possible GitHub outage detected by StatusGator
– GitHub acknowledged the outage on their status page
– StatusGator marked the possible outage resolved
GitHub Issues outage reports
Lists recent GitHub Issues incidents, including duration, acknowledgement status, and severity.
Lists recent GitHub Issues incidents, including duration, acknowledgement status, and severity.
5,315 outage reports in the last 24 hours
Recent community and social reports
Botoșani County, Romania
"down"
• about 14 hours ago
Tokyo, Japan
"ERR_HTTP2_SERVER_REFUSED_STREAM"
• about 14 hours ago
France
"Not enable this site and Firefox tell it's not secure"
• about 14 hours ago
North Holland, The Netherlands
Error message
• about 14 hours ago
Massachusetts, United States
Other
• about 14 hours ago
Hesse, Germany
"Couldn't establish secure connection"
• about 14 hours ago
Central Visayas, Philippines
"web server issue "
• about 14 hours ago
Provence-Alpes-Côte d'Azur, France
"not accesssible"
• about 14 hours ago
North Rhine-Westphalia, Germany
"This site can’t be reached The webpage at https://github.com/ might be temporarily down or it may have moved permanently to a new web address. ERR_HTTP2_SERVER_REFUSED_STREAM "
• about 14 hours ago
Galicia, Spain
"ERR_HTTP2_SERVER_REFUSED_STREAM"
• about 14 hours ago
North Rhine-Westphalia, Germany
"ERR_HTTP2_SERVER_REFUSED_STREAM"
• about 14 hours ago
Pomerania, Poland
""ERR_HTTP2_SERVER_REFUSED_STREAM""
• about 14 hours ago
Lower Silesia, Poland
"ERR_HTTP2_SERVER_REFUSED_STREAM"
• about 15 hours ago
Brittany, France
Connectivity issue
• about 15 hours ago
Metro Manila, Philippines
"Website"
• about 15 hours ago
City of Zagreb, Croatia
"completely down"
• about 15 hours ago
Baden-Wurttemberg, Germany
"server not reached"
• about 15 hours ago
Lombardy, Italy
"ERR_HTTP2_SERVER_REFUSED_STREAM"
• about 15 hours ago
Piedmont, Italy
"ERR_HTTP2_SERVER_REFUSED_STREAM"
• about 15 hours ago
Gelderland, The Netherlands
"Its NOT up"
• about 15 hours ago
Top reported outages
Error message
Connectivity issue
Service down
Server not responding
App not loading
Sign in problem
Other
Unable to download
Slow performance
Having a different problem?
Get notified about GitHub Issues outages
Stay updated with instant alerts for GitHub Issues outages by signing up now!
GitHub Issues outage map
Displays regions where users have recently reported issues. Map markers are based on user-submitted reports.
View full map
Displays regions where users have recently reported issues. Map markers are based on user-submitted reports.
GitHub outage map
GitHub Issues incidents history
Lists recent GitHub Issues incidents, including duration, acknowledgement status, and severity.
View more history
Lists recent GitHub Issues incidents, including duration, acknowledgement status, and severity.
| Incident Name | Duration | Started | Acknowledged | Severity |
|---|---|---|---|---|
|
Website inaccessible due to server connection errors
|
42m | Yes, 21m delay |
Down
|
|
|
Incident with GitHub Actions
|
23d 15h 40m | Yes, 8m delay |
Down
|
|
|
Authentication issues related to API requests
|
15d 2h 40m | Yes |
Down
|
|
|
Actions failing due to gateway errors
|
2h 4m | Yes, 44m delay |
Down
|
|
|
GitHub Copilot login and connection issues
|
5h 53m | No |
Warn
|
|
|
Copilot service unavailable
|
55m | No |
Warn
|
|
|
Server unavailable when accessing the service
|
33d 12h 12m | Yes, 9m delay |
Down
|
|
|
Service unavailable
|
7h 16m | Yes, 6m delay |
Down
|
|
|
Language model unavailable
|
14h 42m | No |
Warn
|
|
|
Service outage
|
4d 19m | Yes, 36m delay |
Warn
|
|
|
GitHub Copilot not responding
|
2h 56m | No |
Warn
|
|
|
GitHub Copilot unavailable due to global rate limiting errors
|
53m | No |
Warn
|
|
|
Disruption with some GitHub services
|
30m | Yes |
Warn
|
|
|
Repository access and login issues due to server errors
|
9d 21h 16m | Yes, 1m delay |
Down
|
|
|
Github Copilot requests failing due to unsupported API version
|
31m | No |
Warn
|
|
|
Degraded Performance in Webhooks API and UI, Pull Requests
|
21d 21h 35m | Yes, 6m delay |
Down
|
|
|
Copilot returning 502 errors on requests.
|
22m | No |
Warn
|
|
|
Copilot service unavailable
|
9d 5h 3m | Yes, 18m delay |
Down
|
|
|
504 gateway timeout errors affecting service availability
|
1h 17m | No |
Warn
|
|
|
Incident with Issues and Pull Requests
|
35m | Yes |
Warn
|
Incident name
Website inaccessible due to server connection errors
Duration
42m
Start
Acknowledged
Yes, 21m delay
Severity
Down
Incident name
Incident with GitHub Actions
Duration
23d 15h 40m
Start
Acknowledged
Yes, 8m delay
Severity
Down
Incident name
Authentication issues related to API requests
Duration
15d 2h 40m
Start
Acknowledged
Yes
Severity
Down
Incident name
Actions failing due to gateway errors
Duration
2h 4m
Start
Acknowledged
Yes, 44m delay
Severity
Down
Incident name
GitHub Copilot login and connection issues
Duration
5h 53m
Start
Acknowledged
No
Severity
Warn
Incident name
Copilot service unavailable
Duration
55m
Start
Acknowledged
No
Severity
Warn
Incident name
Server unavailable when accessing the service
Duration
33d 12h 12m
Start
Acknowledged
Yes, 9m delay
Severity
Down
Incident name
Service unavailable
Duration
7h 16m
Start
Acknowledged
Yes, 6m delay
Severity
Down
Incident name
Language model unavailable
Duration
14h 42m
Start
Acknowledged
No
Severity
Warn
Incident name
Service outage
Duration
4d 19m
Start
Acknowledged
Yes, 36m delay
Severity
Warn
Incident name
GitHub Copilot not responding
Duration
2h 56m
Start
Acknowledged
No
Severity
Warn
Incident name
GitHub Copilot unavailable due to global rate limiting errors
Duration
53m
Start
Acknowledged
No
Severity
Warn
Incident name
Disruption with some GitHub services
Duration
30m
Start
Acknowledged
Yes
Severity
Warn
Incident name
Repository access and login issues due to server errors
Duration
9d 21h 16m
Start
Acknowledged
Yes, 1m delay
Severity
Down
Incident name
Github Copilot requests failing due to unsupported API version
Duration
31m
Start
Acknowledged
No
Severity
Warn
Incident name
Degraded Performance in Webhooks API and UI, Pull Requests
Duration
21d 21h 35m
Start
Acknowledged
Yes, 6m delay
Severity
Down
Incident name
Copilot returning 502 errors on requests.
Duration
22m
Start
Acknowledged
No
Severity
Warn
Incident name
Copilot service unavailable
Duration
9d 5h 3m
Start
Acknowledged
Yes, 18m delay
Severity
Down
Incident name
504 gateway timeout errors affecting service availability
Duration
1h 17m
Start
Acknowledged
No
Severity
Warn
Incident name
Incident with Issues and Pull Requests
Duration
35m
Start
Acknowledged
Yes
Severity
Warn
GitHub Issues status history
Shows daily GitHub Issues status over the past 60 days, including uptime, warnings, and outage events.
Shows daily GitHub Issues status over the past 60 days, including uptime, warnings, and outage events.
June 25, 2026
Down for 9 Minutes
Down for 9 Minutes
July 20, 2026
Down for 23 Hours and 3 Minutes
Down for 23 Hours and 3 Minutes
July 21, 2026
Down for 1 Day
Down for 1 Day
July 22, 2026
Down for 1 Day
Down for 1 Day
July 23, 2026
Down for 23 Hours and 59 Minutes
Down for 23 Hours and 59 Minutes
July 24, 2026
Warning for 59 Minutes
Warning for 59 Minutes
July 24, 2026
Down for 22 Hours and 59 Minutes
Down for 22 Hours and 59 Minutes
July 25, 2026
Down for 1 Day
Down for 1 Day
July 26, 2026
Down for 1 Day
Down for 1 Day
July 27, 2026
Down for 1 Day
Down for 1 Day
July 28, 2026
Down for 1 Day
Down for 1 Day
July 29, 2026
Down for 1 Day
Down for 1 Day
July 30, 2026
Down for 1 Day
Down for 1 Day
July 31, 2026
Down for 1 Day
Down for 1 Day
August 01, 2026
Down for 1 Day
Down for 1 Day
August 02, 2026
Down for 1 Day
Down for 1 Day
August 03, 2026
Down for 1 Day
Down for 1 Day
August 04, 2026
Down for 1 Day
Down for 1 Day
August 05, 2026
Down for 1 Day
Down for 1 Day
August 06, 2026
Down for 1 Day
Down for 1 Day
August 07, 2026
Down for 1 Day
Down for 1 Day
August 08, 2026
Down for 1 Day
Down for 1 Day
August 09, 2026
Down for 1 Day
Down for 1 Day
August 10, 2026
Down for 1 Day
Down for 1 Day
August 11, 2026
Down for 1 Day
Down for 1 Day
August 12, 2026
Warning for 19 Minutes
Warning for 19 Minutes
August 12, 2026
Down for 16 Hours and 16 Minutes
Down for 16 Hours and 16 Minutes
60 days ago
Today
Up
Down
Warn
Maint
GitHub Issues status page accuracy
Learn more
GitHub 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.
A – Excellent
| 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 Issues outages
Stay updated with instant alerts for GitHub Issues outages by signing up now!
Looking for Downdetector GitHub Issues alerts?
| Features | StatusGator | Downdetector |
|---|---|---|
| Both official and crowdsourced updates for GitHub Issues outages. |
|
|
| More than 10,120 services monitored. |
|
|
| Proactive alerts on GitHub Issues status changes sent to your Slack, Microsoft Teams, and more. |
|
|
| Monitoring of both GitHub Issues and your own apps. |
|
|
| Granular monitoring of GitHub Issues components. |
|
|
Both official and crowdsourced updates for GitHub Issues outages.
StatusGator
Downdetector
More than 10,120 services monitored.
StatusGator
Downdetector
Proactive alerts on GitHub Issues status changes sent to your Slack, Microsoft Teams, and more.
StatusGator
Downdetector
Monitoring of both GitHub Issues and your own apps.
StatusGator
Downdetector
Granular monitoring of GitHub Issues components.
StatusGator
Downdetector
About our GitHub Issues status page integration
GitHub Issues (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,738 outages that affected GitHub Issues users. When GitHub Issues 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 Issues 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 Issues is experiencing a problem now or has recently resolved one, our detailed history keeps you updated.
More than 3,400 StatusGator users monitor GitHub Issues 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 941,000 notifications to our users about GitHub Issues 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 Issues 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 Issues 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 Issues 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 Issues posts separate notifications for planned maintenance work. StatusGator will notify subscribers when GitHub Issues enters a pre-planned maintenance window, keeping you up to date.
-
Status Messages
When GitHub Issues 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 Issues 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 Issues 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.