GitHub
—
24h Uptime
—
7d Uptime
99.90%
30d Uptime
99.69%
90d Uptime
Components
View uptime historyDeveloper Notes
GitHub hosts 100M+ repositories and is the primary source control, CI/CD (Actions), and collaboration platform for developers.
Incident Overview
Total Incidents
57
Active Now
0
Resolved
57
Avg. Resolution
1h 37m
Recent Incidents
View all incidentsDisruption with some GitHub services
Incident with Pages
Disruption with some GitHub services
Problems with third-party Claude and Codex Agent sessions not being listed in the agents tab dashboard
Disruption with some GitHub services
Disruption with some GitHub services
Disruption with GitHub notifications
Disruption with some GitHub services
Copilot Coding Agent failing to start some jobs
GitHub audit logs are unavailable
Disruption with GitHub's code search
Incident with Copilot
Incident with Pull Requests: High percentage of 500s
Issues with metered billing report generation
Elevated delays in Actions workflow runs and Pull Request status updates
Incident with Copilot
Disruption with some GitHub services
Teams Github Notifications App is down
Disruption with some GitHub services
Disruption with Copilot Coding Agent Sessions
Git operations for users in the west coast are experiencing an increase in latency
Issues with Copilot Coding Agent
Disruption with Copilot Coding Agent sessions
Disruption with some GitHub services
Webhook delivery is delayed
Errors starting and connecting to Codespaces
Degraded performance for various services
Degraded Codespaces experience
Actions failures to download (401 Unauthorized)
Disruption with some GitHub services
Incident with API Requests
Degraded experience with Copilot Code Review
Incident With Webhooks
Incident with Webhooks
Incident with Codespaces
Incident with Webhooks
Actions is experiencing degraded availability
Multiple services are affected, service degradation
Disruption with some GitHub services
Some OpenAI models degraded in Copilot
Claude Opus 4.6 Fast not appearing for some Copilot users
Incident with all GitHub services
Delayed visibility of newly added issues on project boards
Incident with Pull Requests /pulls
Incident with Copilot agent sessions
Code view fails to load when content contains some non-ASCII characters
High latency on webhook API requests
Incident with Copilot
Incident with Copilot Agent Sessions impacting CCA/CCR
Incident with Issues and Pull Requests Search
Code search experiencing degraded performance
Incident with Actions
Incident with Copilot
Extended job start delays for larger hosted runners
Incident with Copilot GPT-5.1-Codex
Degraded performance in merge queue
Intermittent authentication failures on GitHub
Related DevTools Services
Frequently Asked Questions
Is GitHub down right now?
GitHub is currently operational. DevHelm monitors GitHub's official status page continuously and updates this page every 5 minutes.
What is GitHub's current uptime?
GitHub has a measured 30-day uptime of 99.90%. Over the last 24 hours, uptime is not yet available, and over 7 days it is not yet available. These figures are computed from GitHub's official status page data.
How many incidents has GitHub had recently?
GitHub has experienced 57 incidents in the recent monitoring window. Resolved incidents were fixed in an average of 1h 37m. All incidents are currently resolved.
What components does GitHub monitor?
DevHelm tracks 11 individual components for GitHub, including Git Operations, Webhooks, Visit www.githubstatus.com for more information, API Requests, Issues, and 6 more. Each component has its own status and 90-day uptime history shown above.
How can I get notified about GitHub outages?
You can subscribe to GitHub's incident feed via Atom/RSS at devhelm.io/status/github/feed.xml for use in any feed reader. For real-time alerts via Slack, email, PagerDuty, or webhooks, add GitHub as a dependency in your DevHelm workspace.
About GitHub Status Monitoring
This page provides real-time operational status for GitHub, powered by DevHelm's continuous monitoring infrastructure. We track GitHub's official status page and aggregate component-level data into uptime percentages, incident timelines, and historical trends.
GitHub status data is refreshed every 5 minutes. We currently track 11 individual components, each with its own operational status and 90-day uptime history. When any component reports degraded performance or an outage, it is reflected here within minutes.
Uptime percentages represent the proportion of time all monitored components reported operational status. Incident data comes from vendor-published incident timelines and includes status updates, affected components, and resolution times. This methodology ensures consistent, comparable data across all services tracked by DevHelm.
Monitor your own services alongside GitHub
Get alerted when your dependencies have issues — before your users notice.
Start Free