Last checked from GitHub Pull Requests official status page 1 min. 31 sec. ago
GitHub Pull Requests Status
Collaborative platform for software development and version control.
Not working for you?
Is GitHub Pull Requests down?
GitHub Pull Requests is up
Not working for you?
StatusGator last checked the status of GitHub on and the service was operational. There have been 1 user-submitted report of outages in the past 24 hours.
GitHub Pull Requests service health graph
Shows recent status reports over time, including possible and confirmed outages.
This chart represents GitHub Pull 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 Pull Requests status data.
GitHub Pull Requests outage reports
Lists recent GitHub Pull Requests incidents, including duration, acknowledgement status, and severity.
0 outage reports in the last 24 hours
Recent community and social reports
Baden-Wurttemberg, Germany
"Got a unicorn with the message: No server is currently available to service your request."
• 1 day ago
Tyrol, Austria
"Site offline"
• 1 day ago
Gujarat, India
"Can't access the web as well as any other services"
• 2 days ago
Uusimaa, Finland
Server not responding
• 2 days ago
Uusimaa, Finland
"504 Gateway Time-out"
• 2 days ago
Myanmar
""We're having a really bad day. The Unicorns have taken over. We're doing our best to get them under control and get GitHub back up and running.""
• 2 days ago
Texas, United States
"Pages not loading, error placeholder says "the unicorns took over""
• 2 days ago
ÃŽle-de-France, France
"unicorn have taken over"
• 2 days ago
Punjab, India
"unicorns took over"
• 3 days ago
Hesse, Germany
"We're having a really bad day. The Unicorns have taken over. We're doing our best to get them under control and get GitHub back up and running. "
• 3 days ago
Andhra Pradesh, India
"Slow"
• 3 days ago
Uzbekistan
"We're having a really bad day. The Unicorns have taken over. We're doing our best to get them under control and get GitHub back up and running."
• 3 days ago
England, United Kingdom
Server not responding
• 3 days ago
Hesse, Germany
Server not responding
• 3 days ago
Hesse, Germany
"We're having a really bad day. The Unicorns have taken over. We're doing our best to get them under control and get GitHub back up and running. Repeatedly"
• 3 days ago
Nonthaburi, Thailand
"504"
• 3 days ago
Metro Manila, Philippines
"Github slow"
• 3 days ago
Victoria, Australia
Server not responding
• 3 days ago
Victoria, Australia
"504"
• 3 days ago
Hesse, Germany
"Website is down, cannot load, show timeout error"
• 3 days ago
Top reported outages
Having a different problem?
Get notified about GitHub Pull Requests outages
Stay updated with instant alerts for GitHub Pull Requests outages by signing up now!
GitHub Pull Requests outage map
Displays regions where users have recently reported issues. Map markers are based on user-submitted reports.
View full map
GitHub Pull Requests incidents history
Lists recent GitHub Pull Requests incidents, including duration, acknowledgement status, and severity.
View more history
| Incident name | Duration | Started | Acknowledged | Severity |
|---|---|---|---|---|
|
Incident with Pull Requests
|
20m | Yes |
Warn
|
|
|
Incident with several GitHub Services
|
1h 30m | Yes |
Down
|
|
|
Website inaccessible due to server connection errors
|
19d 18h 48m | Yes, 21m delay |
Down
|
|
|
Incident with Pull Requests and Issues
|
20m | Yes |
Warn
|
|
|
Latency issues across a number of services
|
1d 11h 40m | Yes, 8m delay |
Down
|
|
|
Degradation with Webhooks, Pull Requests and Actions
|
20m | Yes |
Warn
|
|
|
Actions failing due to gateway errors
|
2h 4m | Yes, 44m delay |
Down
|
|
|
GitHub Actions workflows not running
|
12d 5h 8m | Yes, 10m delay |
Down
|
|
|
GitHub Copilot login and connection issues
|
5h 53m | No |
Warn
|
|
|
Copilot service unavailable
|
55m | No |
Warn
|
|
|
Incident with Issues and Webhooks
|
2d 3h 10m | Yes |
Down
|
|
|
Language model unavailable
|
14h 42m | No |
Warn
|
|
|
GitHub Copilot not responding
|
2h 56m | No |
Warn
|
|
|
Elevated delays in Actions workflow runs and Pull Request status updates
|
31d 4h 40m | Yes, 36m delay |
Down
|
|
|
GitHub Copilot unavailable due to global rate limiting errors
|
53m | No |
Warn
|
|
|
Repository access and login issues due to server errors
|
21d 1h 56m | Yes, 1m delay |
Down
|
|
|
Code search experiencing degraded performance
|
7d 45m | Yes, 6m delay |
Warn
|
|
|
Degraded performance in merge queue
|
55m | Yes |
Warn
|
|
|
Github Copilot requests failing due to unsupported API version
|
31m | No |
Warn
|
|
|
Incident with Pull Requests
|
3d 22h 10m | Yes |
Down
|
GitHub Pull Requests status history
Shows daily GitHub Pull Requests status over recent days, including uptime, warnings, and outage events.
Down for 1 Hour and 29 Minutes
Warning for 19 Minutes
Warning for 19 Minutes
Warning for 9 Hours and 7 Minutes
Warning for 1 Day
Warning for 1 Day
Warning for 1 Day
Warning for 14 Hours and 1 Minute
Down for 9 Hours and 57 Minutes
Down for 1 Day
Down for 1 Day
Down for 1 Day
Down for 1 Day
Down for 1 Day
Down for 1 Day
Down for 1 Day
Down for 1 Day
Warning for 58 Minutes
Down for 23 Hours and 1 Minute
Warning for 23 Hours and 59 Minutes
Warning for 1 Day
Warning for 1 Day
Warning for 1 Day
Warning for 1 Day
Warning for 16 Hours and 5 Minutes
Down for 1 Hour and 29 Minutes
Warning for 19 Minutes
GitHub Pull Requests 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 Pull Requests outages
Stay updated with instant alerts for GitHub Pull Requests outages by signing up now!
Looking for Downdetector GitHub Pull Requests alerts?
| Features | StatusGator | Downdetector |
|---|---|---|
| Both official and crowdsourced updates for GitHub Pull Requests outages. |
|
|
| More than 11,110 services monitored. |
|
|
| Proactive alerts on GitHub Pull Requests status changes sent to your Slack, Microsoft Teams, and more. |
|
|
| Monitoring of both GitHub Pull Requests and your own apps. |
|
|
| Granular monitoring of GitHub Pull Requests components. |
|
|
About our GitHub Pull Requests status page integration
GitHub Pull 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,824 outages that affected GitHub Pull Requests users. When GitHub Pull 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 Pull 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 Pull Requests is experiencing a problem now or has recently resolved one, our detailed history keeps you updated.
More than 3,400 StatusGator users monitor GitHub Pull 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 974,600 notifications to our users about GitHub Pull 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 Pull 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 Pull 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 Pull 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 Pull Requests posts separate notifications for planned maintenance work. StatusGator will notify subscribers when GitHub Pull Requests enters a pre-planned maintenance window, keeping you up to date.
-
Status messages
When GitHub Pull 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 Pull 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 Pull 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.