GitHub Status
GitHub header

All Systems Operational

About This Site

Check GitHub Enterprise Cloud status by region:
- Australia: au.githubstatus.com
- EU: eu.githubstatus.com
- Japan: jp.githubstatus.com
- US: us.githubstatus.com

Uptime over the past 90 days. View historical uptime.
Git Operations Operational
90 days ago
99.99 % uptime
Today
Webhooks Operational
90 days ago
100.0 % uptime
Today
Visit www.githubstatus.com for more information Operational
API Requests Operational
90 days ago
99.94 % uptime
Today
Issues Operational
90 days ago
99.98 % uptime
Today
Pull Requests Operational
90 days ago
99.62 % uptime
Today
Actions Operational
90 days ago
99.86 % uptime
Today
Packages Operational
90 days ago
100.0 % uptime
Today
Pages Operational
90 days ago
99.96 % uptime
Today
Copilot Operational
90 days ago
99.88 % uptime
Today
Codespaces Operational
90 days ago
99.86 % uptime
Today
Copilot AI Model Providers Operational
90 days ago
99.86 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Jun 25, 2026
Degradation with Webhooks, Pull Requests and Actions
Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Jun 25, 18:27 UTC
Update - We identified an issue that caused degradation across multiple services including Webhooks, Pull Requests, Actions, and Issues. Customers may have experienced delays or failures with these services. We have applied mitigations and affected services have recovered.
Jun 25, 18:27 UTC
Monitoring - The degradation affecting Actions, Issues, Pull Requests and Webhooks has been mitigated. We are monitoring to ensure stability.
Jun 25, 18:07 UTC
Update - Issues is experiencing degraded performance. We are continuing to investigate.
Jun 25, 17:58 UTC
Update - Actions is experiencing degraded availability. We are continuing to investigate.
Jun 25, 17:53 UTC
Investigating - We are investigating reports of degraded performance for Actions, Pull Requests and Webhooks
Jun 25, 17:50 UTC
Jun 24, 2026

No incidents reported.

Jun 23, 2026
We are seeing elevated errors with Next Edit Suggestions and Completions
Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Jun 23, 23:29 UTC
Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
Jun 23, 23:27 UTC
Update - We have applied a rollback and are seeing recovery.
Jun 23, 23:26 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
Jun 23, 23:04 UTC
Jun 22, 2026

No incidents reported.

Jun 21, 2026

No incidents reported.

Jun 20, 2026

No incidents reported.

Jun 19, 2026

No incidents reported.

Jun 18, 2026

No incidents reported.

Jun 17, 2026
Disruption with Copilot next edit suggestions
Resolved - On June 17, 2026, between 16:57 UTC and 19:14 UTC, Copilot code completions were degraded and users were unable to receive Next Edit Suggestions. Standard ghost text code completions were not affected. This was due to a configuration change that caused the service's routing layer to incorrectly discard all Next Edit Suggestion model endpoints as invalid.

We mitigated the incident by deploying a corrected configuration change at 18:55 UTC, with full recovery observed at 19:14 UTC.

We are working to improve the resilience of our routing layer to limit impact due to a subset of invalid configurations, and to improve our alerting to detect sudden traffic changes that are not captured by standard error rate monitors.
Jun 17, 19:28 UTC
Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
Jun 17, 19:14 UTC
Update - We have applied mitigation and are seeing recovery
Jun 17, 19:09 UTC
Update - We have identified a likely cause and are applying a mitigation
Jun 17, 18:40 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
Jun 17, 17:57 UTC
Incident With Webhooks
Resolved - On June 17, 2026, between 11:35 UTC and 19:20 UTC, the Webhooks service was degraded and delivered webhook payloads with missing installation information. On average, 11.3% of webhook deliveries were impacted. Customers relying on the installation field for authentication or routing were unable to process affected webhooks. A smaller subset of deliveries for the security_advisory event (0.04%) were delivered successfully but were not recorded for redelivery. This was due to a defect in a new delivery code path that failed to include installation data in webhook payloads.

We mitigated the incident by disabling the feature flag controlling the new code path.

We are working to improve our automated validation of webhook payloads, and introduce automated alerting for webhook payload regressions to reduce our time to detection and mitigation of issues like this one in the future.

The following events were affected: branch_protection_configuration, code_scanning_alert, commit_comment, custom_property, custom_property_values, dependabot_alert, deploy_key, deployment_protection_rule, deployment_review, dismissal_request_code_scanning, dismissal_request_secret_scanning, installation_target, member, membership, merge_queue_entry, org_block, organization, projects_v2, projects_v2_item, pull_request_review_thread, repository_ruleset, secret_scanning_alert, secret_scanning_alert_location, secret_scanning_scan, security_and_analysis, star, sub_issues, team, team_add, workflow_job.
Jun 17, 19:00 UTC
Incident with Copilot Availability
Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Jun 17, 04:44 UTC
Monitoring - Copilot is operating normally.
Jun 17, 04:44 UTC
Update - We've applied a mitigation to unblock Copilot functionality. Users may start to see signs of recovery. Relaunching your client should accelerate signs of recovery. We will continue to monitor the situation.
Jun 17, 04:26 UTC
Update - We are experiencing degraded availability for chat & agent models in Copilot. Multiple models are impacted and customers may experience requests failing. We are investigating and will provide an update as soon as possible.
Jun 17, 03:52 UTC
Investigating - We are investigating reports of degraded availability for Copilot
Jun 17, 03:50 UTC
Jun 16, 2026
Disruption with some GitHub services
Resolved - On June 16, 2026, between 17:20 UTC and 18:15 UTC, the Opus 4.8 model experienced degraded availability in GitHub Copilot. During this window, some requests to Opus 4.8 failed or errored. Other Copilot models were not affected and remained available as alternatives. This was caused by an issue with an upstream model provider. The upstream provider resolved the issue, and we monitored Opus 4.8 until success rates returned to normal. The incident is fully resolved.
Jun 16, 18:15 UTC
Update - The issues with our upstream model provider have been resolved, and Opus 4.8 is once again available in Copilot products and IDE surfaces.

We will continue monitoring to ensure stability, but mitigation is complete.
Jun 16, 18:14 UTC
Monitoring - The degradation affecting Copilot AI Model Providers has been mitigated. We are monitoring to ensure stability.
Jun 16, 18:00 UTC
Update - We are experiencing degraded availability for the Opus 4.8 model in Copilot products and IDE surfaces. This is due to an issue with an upstream model provider. While we work with them to resolve the issue, we recommend choosing another model or selecting 'Auto' to continue using Copilot.
Jun 16, 17:47 UTC
Investigating - We are investigating reports of degraded availability for Copilot AI Model Providers
Jun 16, 17:45 UTC
Jun 15, 2026
Multiple services have elevated errors and endpoint failures when checking feature flags
Resolved - Between 17:38 UTC and 18:22 UTC on June 15, 2026, approximately 83% of requests to the analytics endpoint serving the /chronicle feature failed.  The cause was an internal feature-flag service that encountered a transient error and failed to recover, causing feature flag checks to fail. The analytics endpoint was gated behind one of these flags, resulting in requests being rejected. We restored service health by removing the feature flag gating the analytics endpoint and deploying that change. To avoid recurrence of similar incidents, we have changed the feature-flag client so that errors that are not known to be permanent are retried, and we are improving alerting and startup behavior so this class of failure is detected and recovered from faster.
Jun 15, 19:10 UTC
Update - We identified an issue with feature flag checks that caused elevated errors and endpoint failures across multiple GitHub Copilot services. Customers may have experienced failed requests or degraded functionality. A fix has been deployed and error rates are steadily decreasing. All affected services are now mitigated and we are monitoring recovery.
Jun 15, 19:10 UTC
Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
Jun 15, 19:02 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
Jun 15, 18:32 UTC
Increased latency with webhooks
Resolved - On June 15, 2026, between 15:27 UTC and 16:23 UTC, GitHub webhook deliveries were delayed. During this window, webhook events were delivered later than normal, with average end-to-end delivery latency peaking at approximately 8.8 minutes. No webhook deliveries were lost — delayed events were queued and delivered once processing recovered.

This was caused by a temporary throughput constraint in an internal event-processing system that moves webhook events through GitHub's delivery pipeline. The rate at which events were processed for delivery dropped below the incoming volume, creating a backlog. We restarted the affected pipeline service, after which throughput recovered and the backlog fully drained by approximately 16:29 UTC. Webhook delivery latency returned to normal, the incident was mitigated at 16:39 UTC, and fully resolved at 17:37 UTC.

To reduce the likelihood and impact of similar incidents, we are working on improving the accuracy of the utilization metrics used to scale our delivery worker pools, reviewing connection and capacity headroom in the delivery pipeline.
Jun 15, 17:37 UTC
Monitoring - The degradation affecting Webhooks has been mitigated. We are monitoring to ensure stability.
Jun 15, 16:39 UTC
Update - Webhooks delivery latency has returned to normal levels. The backlog that built up during the incident has been cleared at approximately 4:29 UTC. We consider this incident resolved.
Jun 15, 16:39 UTC
Investigating - We are investigating reports of degraded performance for Webhooks
Jun 15, 15:37 UTC
Jun 14, 2026

No incidents reported.

Jun 13, 2026

No incidents reported.

Jun 12, 2026

No incidents reported.

Jun 11, 2026
Incident with Webhooks
Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Jun 11, 22:19 UTC
Monitoring - The degradation affecting Webhooks has been mitigated. We are monitoring to ensure stability.
Jun 11, 20:00 UTC
Update - We have applied a mitigation and are monitoring for recovery.
Jun 11, 19:58 UTC
Update - We are currently experiencing delays in Web Hook delivery and are actively investigating the root cause.
Jun 11, 19:42 UTC
Investigating - We are investigating reports of degraded performance for Webhooks
Jun 11, 19:42 UTC
← Incident History Powered by Atlassian Statuspage