Last checked from GitHub API Requests official status page 1 min. 45 sec. ago
GitHub API Requests Status
Collaborative platform for software development and version control.
Not working for you?
Is GitHub API Requests down?
GitHub API Requests is up
Not working for you?
StatusGator last checked the status of GitHub on and the service was operational. There have been 5 user-submitted reports of outages in the past 24 hours.
GitHub API Requests 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 API Requests 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 API Requests status data.
24 hrs ending
●
Service up
●
Possible outage
●
Likely outage
GitHub API Requests outage reports
Lists recent GitHub API Requests incidents, including duration, acknowledgement status, and severity.
Lists recent GitHub API Requests incidents, including duration, acknowledgement status, and severity.
5,052 outage reports in the last 24 hours
Recent community and social reports
Dhaka Division, Bangladesh
"I can not open github from web. And also when i try to push it shows timeout issue"
• about 2 hours ago
Bihor County, Romania
"503 Service Unavailable No server is available to handle this request. "
• about 11 hours ago
Missouri, United States
Slow performance
• 1 day ago
Punjab, Pakistan
Error message
• 2 days ago
Kuala Lumpur, Malaysia
"504 Gateway Time-out"
• 3 days ago
Prague, Czechia
"504 error"
• 3 days ago
West Bengal, India
Service down
• 3 days ago
Cairo Governorate, Egypt
Other
• 3 days ago
New Jersey, United States
"delay in action run-showing job in queue"
• 3 days ago
England, United Kingdom
Server not responding
• 3 days ago
Punjab, Pakistan
Service down
• 3 days ago
Telangana, India
Service down
• 3 days ago
England, United Kingdom
Service down
• 3 days ago
National Capital Territory of Delhi, India
"the actions runner is down or not able to allocate workers "
• 3 days ago
Tel Aviv, Israel
"Jobs are queuing due to unavailable runners"
• 3 days ago
Baden-Wurttemberg, Germany
Service down
• 3 days ago
Victoria, Australia
"linux machine for GitHub action not available"
• 3 days ago
Kentucky, United States
"can connect to git hub on edgde times out workes evry other site"
• 3 days ago
Israel
"can't deploy changes"
• 3 days ago
Prague, Czechia
Service down
• 3 days ago
Top reported outages
Connectivity issue
Service down
Slow performance
Error message
Server not responding
Sign in problem
Unable to download
App not loading
Other
Having a different problem?
Get notified about GitHub API Requests outages
Stay updated with instant alerts for GitHub API Requests outages by signing up now!
GitHub API Requests outage map
Displays regions where users have recently reported issues. Map markers are based on user-submitted reports.
Displays regions where users have recently reported issues. Map markers are based on user-submitted reports.
GitHub outage map
GitHub API Requests incidents history
Lists recent GitHub API Requests incidents, including duration, acknowledgement status, and severity.
View more history
Lists recent GitHub API Requests incidents, including duration, acknowledgement status, and severity.
| Incident Name | Duration | Started | Acknowledged | Severity |
|---|---|---|---|---|
|
Authentication issues related to API requests
|
1h 15m | Yes |
Down
|
|
|
Actions failing due to gateway errors
|
2h 17m | Yes, 44m delay |
Down
|
|
|
Slow git operations and Pull Request creation failures
|
1h 33m | Yes, 19m delay |
Warn
|
|
|
Actions not queueing
|
3h 36m | Yes, 6m delay |
Warn
|
|
|
GitHub Actions workflows not running
|
2h 6m | Yes, 10m delay |
Down
|
|
|
GitHub Copilot login and connection issues
|
6h 52m | No |
Warn
|
|
|
Copilot service unavailable
|
1h 37m | No |
Warn
|
|
|
Server unavailable when accessing the service
|
55m | Yes, 9m delay |
Warn
|
|
|
Service unavailable
|
2h 36m | Yes, 6m delay |
Down
|
|
|
Service outage
|
2h 12m | Yes, 1m delay |
Warn
|
|
|
Language model unavailable
|
15h 38m | No |
Warn
|
|
|
Service outage
|
1h 6m | Yes, 36m delay |
Warn
|
|
|
GitHub Copilot not responding
|
3h 18m | No |
Warn
|
|
|
GitHub Copilot unavailable due to global rate limiting errors
|
1h 49m | No |
Warn
|
|
|
Home page showing errors and displaying 401 and unicorn errors
|
32m | Yes, 5m delay |
Warn
|
|
|
Incident with Copilot and Actions
|
83d 19h 56m | Yes |
Down
|
|
|
Repository access and login issues due to server errors
|
2h 6m | Yes, 1m delay |
Down
|
|
|
Github Copilot not working due to server errors.
|
1h 17m | Yes, 6m delay |
Warn
|
|
|
Github Copilot requests failing due to unsupported API version
|
1h 2m | No |
Warn
|
|
|
Copilot returning 502 errors on requests.
|
1h 12m | No |
Warn
|
Incident name
Authentication issues related to API requests
Duration
1h 15m
Start
Acknowledged
Yes
Severity
Down
Incident name
Actions failing due to gateway errors
Duration
2h 17m
Start
Acknowledged
Yes, 44m delay
Severity
Down
Incident name
Slow git operations and Pull Request creation failures
Duration
1h 33m
Start
Acknowledged
Yes, 19m delay
Severity
Warn
Incident name
Actions not queueing
Duration
3h 36m
Start
Acknowledged
Yes, 6m delay
Severity
Warn
Incident name
GitHub Actions workflows not running
Duration
2h 6m
Start
Acknowledged
Yes, 10m delay
Severity
Down
Incident name
GitHub Copilot login and connection issues
Duration
6h 52m
Start
Acknowledged
No
Severity
Warn
Incident name
Copilot service unavailable
Duration
1h 37m
Start
Acknowledged
No
Severity
Warn
Incident name
Server unavailable when accessing the service
Duration
55m
Start
Acknowledged
Yes, 9m delay
Severity
Warn
Incident name
Service unavailable
Duration
2h 36m
Start
Acknowledged
Yes, 6m delay
Severity
Down
Incident name
Service outage
Duration
2h 12m
Start
Acknowledged
Yes, 1m delay
Severity
Warn
Incident name
Language model unavailable
Duration
15h 38m
Start
Acknowledged
No
Severity
Warn
Incident name
Service outage
Duration
1h 6m
Start
Acknowledged
Yes, 36m delay
Severity
Warn
Incident name
GitHub Copilot not responding
Duration
3h 18m
Start
Acknowledged
No
Severity
Warn
Incident name
GitHub Copilot unavailable due to global rate limiting errors
Duration
1h 49m
Start
Acknowledged
No
Severity
Warn
Incident name
Home page showing errors and displaying 401 and unicorn errors
Duration
32m
Start
Acknowledged
Yes, 5m delay
Severity
Warn
Incident name
Incident with Copilot and Actions
Duration
83d 19h 56m
Start
Acknowledged
Yes
Severity
Down
Incident name
Repository access and login issues due to server errors
Duration
2h 6m
Start
Acknowledged
Yes, 1m delay
Severity
Down
Incident name
Github Copilot not working due to server errors.
Duration
1h 17m
Start
Acknowledged
Yes, 6m delay
Severity
Warn
Incident name
Github Copilot requests failing due to unsupported API version
Duration
1h 2m
Start
Acknowledged
No
Severity
Warn
Incident name
Copilot returning 502 errors on requests.
Duration
1h 12m
Start
Acknowledged
No
Severity
Warn
GitHub API Requests status history
Shows daily GitHub API Requests status over the past 60 days, including uptime, warnings, and outage events.
Shows daily GitHub API Requests status over the past 60 days, including uptime, warnings, and outage events.
May 27, 2026
Warning for 1 Hour and 9 Minutes
Warning for 1 Hour and 9 Minutes
June 10, 2026
Down for 1 Hour and 15 Minutes
Down for 1 Hour and 15 Minutes
60 days ago
Today
Up
Down
Warn
Maint
GitHub API Requests 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 API Requests outages
Stay updated with instant alerts for GitHub API Requests outages by signing up now!
Looking for Downdetector GitHub API Requests alerts?
| Features | StatusGator | Downdetector |
|---|---|---|
| Both official and crowdsourced updates for GitHub API Requests outages. |
|
|
| More than 9,550 services monitored. |
|
|
| Proactive alerts on GitHub API Requests status changes sent to your Slack, Microsoft Teams, and more. |
|
|
| Monitoring of both GitHub API Requests and your own apps. |
|
|
| Granular monitoring of GitHub API Requests components. |
|
|
Both official and crowdsourced updates for GitHub API Requests outages.
StatusGator
Downdetector
More than 9,550 services monitored.
StatusGator
Downdetector
Proactive alerts on GitHub API Requests status changes sent to your Slack, Microsoft Teams, and more.
StatusGator
Downdetector
Monitoring of both GitHub API Requests and your own apps.
StatusGator
Downdetector
Granular monitoring of GitHub API Requests components.
StatusGator
Downdetector
About our GitHub API Requests status page integration
GitHub API Requests (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,652 outages that affected GitHub API Requests users. When GitHub API Requests 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 API Requests 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 API Requests is experiencing a problem now or has recently resolved one, our detailed history keeps you updated.
More than 3,300 StatusGator users monitor GitHub API Requests 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 902,700 notifications to our users about GitHub API Requests 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 API Requests 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 API Requests 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 API Requests 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 API Requests posts separate notifications for planned maintenance work. StatusGator will notify subscribers when GitHub API Requests enters a pre-planned maintenance window, keeping you up to date.
-
Status Messages
When GitHub API Requests 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 API Requests 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 API Requests 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.