GitHub status updated
GitHub is working normally
This chart shows the number of user-reported issues for GitHub service health over the past 24 hours, grouped into 20-minute intervals. It's normal to see occasional reports, which may be due to individual user issues rather than a broader problem.
See where users report GitHub is down. The map shows recent GitHub outages from around the world.
GitHub Outage MapSee what users report when GitHub is down and how GitHub outages affect them.
Z - No server is currently available to service your request..
Why - Github.app made in Spark always have 429 error code wtf! Hm, something went wrong (429) Try refreshing the page or going back to the previous page..
MF - not able to load the page, its like my internet is down but internet is working and im unable to access github.com.
Web server error 503 when trying to access Github.com.
503 error on the homepage.
Hit rate limit on first request, even after switching browsers and network..
registration problem - captcha after completion generates problem. Registration not possible (tried few browsers on different devices).
No server is currently available to service your request. Sorry about that. Please try refreshing and contact us if the problem persists..
Website not responding to any requests, justsays can't load page.
spesna - Hmmm… can't reach this page github.com took too long to respond.
In the last 90 days, GitHub had 60 incidents (12 major outages and 48 minor incidents) with a median duration of 1 hour 19 minutes.
Incidents
Major Outages
Minor Incidents
Median Resolution
Check GitHub status history below. IsDown detects when GitHub is down, tracking both official outages and user-reported issues.
| Title | Started At | Duration |
|---|---|---|
|
We are investigating reports of impacted performance for some GitHub services.
|
Jan 16, 2026 at 11:53 PM UTC
|
about 3 hours |
|
We are investigating reports of degraded availability for API Requests, Actions, Issues and Pull ...
|
Jan 15, 2026 at 04:56 PM UTC
|
about 2 hours |
|
We are investigating reports of degraded performance for Actions
|
Jan 15, 2026 at 02:24 PM UTC
|
about 1 hour |
|
We are investigating reports of degraded performance for Webhooks
|
Jan 14, 2026 at 08:21 PM UTC
|
about 1 hour |
|
We are investigating reports of impacted performance for some GitHub services.
|
Jan 14, 2026 at 10:56 AM UTC
|
about 2 hours |
|
We are investigating reports of degraded performance for Copilot
|
Jan 14, 2026 at 09:24 AM UTC
|
about 1 hour |
|
We are investigating reports of impacted performance for some GitHub services.
|
Jan 13, 2026 at 10:21 PM UTC
|
about 2 hours |
|
We are investigating reports of impacted performance for some GitHub services.
|
Jan 13, 2026 at 09:38 AM UTC
|
about 1 hour |
|
We are investigating reports of impacted performance for some GitHub services.
|
Jan 12, 2026 at 10:02 AM UTC
|
19 minutes |
|
We are investigating reports of impacted performance for some GitHub services.
|
Jan 09, 2026 at 05:53 PM UTC
|
about 9 hours |
Check if any GitHub component is down. View the current status of 11 services and regions.
| Component | Status |
|---|---|
| Actions | OK |
| API Requests | OK |
| Codespaces | OK |
| Copilot | OK |
| GitHub Pages | OK |
| Git Operations | OK |
| Issues | OK |
| Packages | OK |
| Pull Requests | OK |
| Visit www.githubstatus.com for more information | OK |
| Webhooks | OK |
IsDown monitors GitHub service health to detect when GitHub is down before it's officially reported.
Compare GitHub status, outages, and service health against alternatives. See which services go down less often.
IsDown has monitored GitHub continuously since April 2020, tracking this Version Control & Collaboration for 6 years. Over that time, we've documented 790 outages and incidents, averaging 11.4 per month. When GitHub goes down, incidents typically resolve within 137 minutes based on historical data.
We monitor GitHub's official status page across 11 components. IsDown interprets GitHub statuses (operational, degraded performance, partial outage, and major outage) to deliver precise health metrics and filter alerts by the components you actually use.
When GitHub is down, IsDown combines official status data with user reports for early detection. Vendors often delay acknowledging problems, so user reports help us alert you before the official announcement.
Engineering and operations teams rely on IsDown to track GitHub status and receive verified outage alerts through Slack, Teams, PagerDuty, or 20+ other integrations.
IsDown checks GitHub's status page every few minutes, across all 11 components. We combine official status data with user reports to detect when GitHub is down, often before the vendor announces it.
When GitHub status changes, IsDown sends alerts to your preferred channels. Filter by severity to skip noise and focus on outages that affect your business.
IsDown checks GitHub official status page for major/minor outages or downtimes. A major outage is when GitHub experiences a critical issue that severely affects one or more services/regions. A minor incident is when GitHub experiences a small issue affecting a small percentage of its customer's applications. An example is the performance degradation of an application. The moment we detect a GitHub outage, we send you an alert and update your dashboard and status page.
GitHub and other vendors don't always report outages on time. IsDown collects user reports to provide early detection of outages. This way, even without an official status update, you can stay ahead of possible problems.
IsDown collects all information from the outages published in GitHub status page to provide the context of the outage. If available, we gather the title, description, time of the outage, status, and outage updates. Another important piece of information is the affected services/regions which we use to filter the notifications that impact your business.
GitHub publishes scheduled maintenance events on their status page. IsDown collects all the information for each event and creates a feed that people can follow to ensure they are not surprised by unexpected downtime or problems. We also send the feed in our weekly report, alerting the next maintenances that will take place.
IsDown monitors GitHub and all their 11 components that can be affected by an outage. IsDown allows you to filter the notifications and status page alerts based on the components you care about. For example, you can choose which components or regions affect your business and filter out all other outages. This way you avoid alert fatigue in your team.
GitHub is just one of 5,421 services IsDown monitors. Add all your critical dependencies to one dashboard, get alerts when any service is down, and share a status page with your team.
Monitor GitHub health alongside all your other vendors in a single view.
Get notified when GitHub is down. Filter by severity to skip noise.
Route GitHub outage alerts to Slack, Teams, PagerDuty, or webhooks.
Share GitHub service status with your team or customers on a branded page.
Looking for GitHub outage alerts like Downdetector? IsDown monitors GitHub's official status page for verified incident data, not just user reports. Know exactly when GitHub is down, which components are affected, and when service health is restored. Here's why official GitHub status monitoring beats crowdsourced detection:
| Features |
|
Downdetector |
|---|---|---|
| Official GitHub status page monitoring. Know when GitHub is down with real time incident details. | ||
| Monitor 5,420+ services including GitHub in a single dashboard. | ||
| Instant GitHub outage alerts sent to Slack, Teams, PagerDuty, and more. | ||
| Combined monitoring: GitHub official status plus user reports for early outage detection. | ||
| Maintenance feed for GitHub | ||
| Granular alerts filtering by GitHub components and regions. |
14-day free trial • No credit card required
When GitHub is down, start by checking the official status page and IsDown's monitoring. If PRs, repository access, or deployment processes are affected, try using alternative workflows. If it's a network or connectivity issue, verify whether it's on GitHub's end or a local problem by testing a different network or clearing the DNS cache.
Keeping track of GitHub status updates helps in understanding the outage. In cases of widespread disruptions, teams can mitigate the impact by delaying non-critical tasks or working offline until service is restored.
IsDown provides real-time alerts when GitHub experiences disruptions. Users can set up notifications via Slack, PagerDuty, or email to stay informed. Whether it's a network problem, database failure, or deployment delay, IsDown keeps users updated. Tracking GitHub status checks ensures teams are aware of potential service interruptions before they escalate.
Yes, when GitHub experiences an outage, it can significantly disrupt software development workflows. Developers may be unable to push code, merge pull requests (PRs), or access repositories. This can delay releases, hinder collaboration, and affect automation pipelines, particularly in DevOps and CI/CD environments where GitHub is integrated with build and deployment processes.
GitHub outages can be caused by infrastructure failures, database issues, network congestion, or planned/unplanned system maintenance. Problems with query performance, API rate limits, or repository indexing may slow down searches and repository access. To determine whether an issue is widespread or isolated, developers should check GitHub's official status page and third-party monitoring platforms like IsDown for real-time outage reports.
To reduce the impact of GitHub downtime, teams should implement contingency workflows. This may include maintaining local repositories for offline work, setting up alternative version control systems (e.g., GitLab, Bitbucket), or using mirrored repositories. For CI/CD pipelines, integrating multiple service providers can ensure redundancy. Regularly monitoring GitHub status updates allows teams to react proactively and adjust workflows as needed.
Currently there's no report of GitHub being slow. Check on the top of the page if there are any reported problems by other users.
IsDown monitors the GitHub official status page every few minutes. We also get reports from users like you. If there are enough reports about an outage, we'll show it on the top of the page.
GitHub last outage was on January 16, 2026 with the title "Disruption with some GitHub services"
Because IsDown is a status page aggregator, which means that we aggregate the status of multiple cloud services. You can monitor GitHub and all the services that impact your business. Get a dashboard with the health of all services and status updates. Set up notifications via Slack, Datadog, PagerDuty, and more, when a service you monitor has issues or when maintenances are scheduled.
IsDown and DownDetector help users determine if GitHub is having problems. The big difference is that IsDown is a status page aggregator. IsDown monitors a service's official status page to give our customers a more reliable source of information instead of just relying on reports from users. The integration allows us to provide more details about GitHub's Outages, like incident title, description, updates, and the parts of the affected service. Additionally, users can create internal status pages and set up notifications for all their third-party services.
14-day free trial · No credit card required · No code required