Skip to content

Which companies just had a verified incident, who lends to them and who owns them. Every claim carries its evidence level and its source. How we decide what is confirmed

US critical infrastructure monitor

GitHub

Cloud, identity and critical software · CA (headquarters)

Monitoring
Not checked: the site's robots.txt does not allow it.: last success Nov 6 12:35 UTC
Public findings
0
Provider status posts on record
52

Cyber and operational findings

Analyst-reviewed records. The grade states how well the cause is established; event, first public observation and acknowledgement are separate dates.

No public findings for this organisation.

Provider status posts

Collected from the organisation's own public status page. These are its words; DFX adds only the wording classification.

  • Degraded performance for multiple GitHub servicesNov 5 23:36 UTC · resolved · minor impact
    Service restricted or degradedInvestigation mentionedRestoration reported
    1. Nov 5 23:36 UTC investigating: We are investigating reports of degraded performance for Actions and Pages
    2. Nov 5 23:36 UTC investigating: We're investigating degraded performance and errors affecting several GitHub services, including Git operations, Issues, Actions, and API access. Some users may see failed requests or slow responses. We'll post another update by 00:05 UTC.
    3. Nov 5 23:58 UTC investigating: Issues is experiencing degraded performance. We are continuing to investigate.
    4. Nov 6 00:06 UTC monitoring: The degradation affecting Actions, Issues and Pages has been mitigated. We are monitoring to ensure stability.
    5. Nov 6 00:06 UTC monitoring: We've applied a mitigation and are seeing recovery across affected services, including Git operations, Issues, Actions, and API access. We're monitoring to confirm stability and will post another update by 00:35 UTC.
    6. Nov 6 00:19 UTC investigating: Git Operations is operating normally.
    7. Nov 6 00:19 UTC monitoring: This incident has been resolved. All affected services, including Git operations, Issues, Actions, and API access, have recovered and remained stable. Thank you for your patience. We'll share more details in our availability report.
    8. Nov 6 00:20 UTC 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.
    View on the provider's status page
  • Incident with ActionsNov 5 16:50 UTC · resolved · minor impact
    Service restricted or degradedInvestigation mentionedRestoration reported
    1. Nov 5 16:50 UTC investigating: We are investigating reports of degraded performance for Actions
    2. Nov 5 16:52 UTC investigating: Some GitHub Actions workflow runs may experience delays or errors when starting. We’re investigating and preparing a mitigation.
    3. Nov 5 17:04 UTC monitoring: The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
    4. Nov 5 17:42 UTC 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.
    View on the provider's status page
  • Incident with ActionsNov 4 17:40 UTC · resolved · major impact
    Service restricted or degradedInvestigation mentionedRestoration reported
    1. Nov 4 17:40 UTC investigating: We are investigating reports of degraded availability for Actions
    2. Nov 4 17:53 UTC investigating: We have identified an issue with events that might trigger Actions. We have applied mitigations and are monitoring for recovery at this point. Customers may observe delayed status updates for their jobs.
    3. Nov 4 18:07 UTC monitoring: The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
    4. Nov 4 18:16 UTC 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.
    View on the provider's status page
  • Incident with Actions and PagesNov 4 16:05 UTC · resolved · major impact
    Service restricted or degradedInvestigation mentionedRestoration reported
    1. Nov 4 16:05 UTC investigating: We are investigating reports of degraded performance for Actions and Pages
    2. Nov 4 16:11 UTC investigating: We are investigating reports of issues with Actions and Pages. We will continue to keep users updated on progress towards mitigation.
    3. Nov 4 16:12 UTC investigating: Webhooks is experiencing degraded performance. We are continuing to investigate.
    4. Nov 4 16:17 UTC investigating: Actions is experiencing degraded availability. We are continuing to investigate.
    5. Nov 4 16:34 UTC investigating: We have identified an issue with events that might trigger Actions. We have applied mitigations and are monitoring for recovery at this point. Customers may observe delayed status updates for their jobs.
    6. Nov 4 16:45 UTC investigating: The degradation affecting Webhooks has been mitigated. We are monitoring to ensure stability.
    7. Nov 4 16:48 UTC monitoring: The degradation affecting Actions and Pages has been mitigated. We are monitoring to ensure stability.
    8. Nov 4 16:49 UTC monitoring: The degradation has been mitigated. We are monitoring to ensure stability.
    9. Nov 4 17:01 UTC 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.
    View on the provider's status page
  • Incident with Pull Requests, Git Operations and IssuesNov 4 09:49 UTC · resolved · major impact
    Service restricted or degradedInvestigation mentionedRestoration reported
    1. Nov 4 09:49 UTC investigating: We are investigating reports of degraded performance for Git Operations, Issues and Pull Requests
    2. Nov 4 09:50 UTC investigating: Actions is experiencing degraded performance. We are continuing to investigate.
    3. Nov 4 09:53 UTC investigating: Pull Requests is experiencing degraded availability. We are continuing to investigate.
    4. Nov 4 10:38 UTC investigating: We're investigating elevated errors and intermittent failures affecting GitHub including Pull Requests, Git Operations, and Issues. We'll continue to keep users updated as we work toward mitigation.
    5. Nov 4 11:11 UTC investigating: API Requests is experiencing degraded performance. We are continuing to investigate.
    6. Nov 4 11:17 UTC investigating: We're currently working on mitigating elevated errors and intermittent failures affecting GitHub, including Pull Requests, Git Operations, and Issues. Some requests may fail or be delayed while we work to restore service. We'll provide another update as more information becomes...
    7. Nov 4 11:30 UTC investigating: The degradation affecting API Requests, Git Operations, Issues and Pull Requests has been mitigated. We are monitoring to ensure stability.
    8. Nov 4 11:43 UTC monitoring: The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
    9. Nov 4 11:50 UTC 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.
    View on the provider's status page
  • Increased task-related errors for Copilot Mission ControlNov 4 08:45 UTC · resolved · minor impact
    Investigation mentionedRestoration reported
    1. Nov 4 08:45 UTC investigating: We are investigating reports of impacted performance for some GitHub services.
    2. Nov 4 08:47 UTC investigating: Copilot Mission Control is experiencing increased error rates (approx 2.5%) in listing and creating tasks due to upstream database throttling. We are investigating two potential mitigations.
    3. Nov 4 09:11 UTC investigating: We've identified the issue with a specific client version and are deploying a mitigation. We are already seeing partial recovery.
    4. Nov 4 09:50 UTC investigating: We're continuing to see recovery as rollout continues
    5. Nov 4 10:01 UTC monitoring: The degradation has been mitigated. We are monitoring to ensure stability.
    6. Nov 4 10:01 UTC 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.
    View on the provider's status page
  • Incident with Git OperationsNov 3 20:57 UTC · resolved · minor impact
    Service restricted or degradedInvestigation mentionedRestoration reported
    1. Nov 3 20:57 UTC investigating: We are investigating reports of degraded performance for Git Operations
    2. Nov 3 21:37 UTC investigating: We have identified the issue impacting Git Operations and are beginning to roll out a mitigation. We will follow up with another update when we begin to see recovery.
    3. Nov 3 22:05 UTC investigating: Our mitigation is rolled out and customers should start seeing improvements to Git Operations. We will continue to provide updates on mitigation status.
    4. Nov 3 22:37 UTC investigating: We are seeing significant improvement, though some Git Operations may be slow for a small set of customers. We are marking this as mitigated and will continue to monitor.
    5. Nov 3 22:37 UTC monitoring: The degradation affecting Git Operations has been mitigated. We are monitoring to ensure stability.
    6. Nov 3 22:41 UTC 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.
    View on the provider's status page
  • Incident with API, Git, and Copilot requestsNov 3 13:25 UTC · resolved · minor impact
    Service restricted or degradedInvestigation mentionedRestoration reported
    1. Nov 3 13:25 UTC investigating: We are investigating reports of degraded performance for Copilot
    2. Nov 3 13:42 UTC investigating: Issues is experiencing degraded performance. We are continuing to investigate.
    3. Nov 3 13:43 UTC investigating: The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.
    4. Nov 3 13:51 UTC monitoring: The degradation affecting Copilot has been mitigated. We are monitoring to ensure stability.
    5. Nov 3 13:52 UTC investigating: API Requests is operating normally.
    6. Nov 3 13:54 UTC monitoring: The degradation has been mitigated. We are monitoring to ensure stability.
    7. Nov 3 13:56 UTC 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.
    View on the provider's status page
  • Elevated errors on GPT-5.4 NanoNov 2 17:46 UTC · resolved · minor impact
    Service restricted or degradedInvestigation mentionedRestoration reported
    1. Nov 2 17:46 UTC investigating: We are investigating reports of degraded performance for Copilot AI Model Providers
    2. Nov 2 17:46 UTC investigating: We are investigating reports of elevated errors on GPT-5.4 Nano
    3. Nov 2 17:58 UTC investigating: We are experiencing degraded availability for the GPT-5.4 Nano model in Copilot products and IDE surfaces. This is due to an issue with an upstream model provider.
    4. Nov 2 18:10 UTC monitoring: The degradation affecting Copilot AI Model Providers has been mitigated. We are monitoring to ensure stability.
    5. Nov 2 18:24 UTC 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.
    View on the provider's status page
  • Incident with DependabotOct 30 20:59 UTC · resolved · minor impact
    Service restricted or degradedInvestigation mentionedRestoration reported
    1. Oct 30 20:59 UTC investigating: We are investigating reports of impacted performance for some GitHub services.
    2. Oct 30 21:00 UTC investigating: We are investigating elevated errors when viewing some Dependabot alerts.
    3. Oct 30 21:44 UTC investigating: We are continuing to investigate elevated errors when viewing some Dependabot alerts. We’ll provide more updates as we learn more.
    4. Oct 30 22:32 UTC investigating: We have mitigated impact and are seeing recovery. We are monitoring for full recovery.
    5. Oct 30 22:32 UTC monitoring: The degradation has been mitigated. We are monitoring to ensure stability.
    6. Oct 30 23:29 UTC resolved: On October 30, 2026, between 20:15 and 21:56 UTC, an advisory-publication-driven fan-out caused an unexpected saturation of network connections to the Dependabot alerts datastore. During this period we observed a high rate of write failures on this datastore; users saw elevated...
    View on the provider's status page
  • Incident with Actions, Pages, and WebhooksOct 30 17:50 UTC · resolved · major impact
    Service restricted or degradedInvestigation mentionedRestoration reported
    View on the provider's status page
  • Disruption with GitHub servicesOct 30 14:31 UTC · resolved · critical impact
    Service restricted or degradedInvestigation mentionedRestoration reported
    View on the provider's status page
  • Disruption with Copilot Cloud servicesOct 29 10:19 UTC · resolved · minor impact
    Service restricted or degradedInvestigation mentionedRestoration reported
    View on the provider's status page
  • Disruption with some Copilot servicesOct 28 14:12 UTC · resolved · critical impact
    Service restricted or degradedSign-in disruptionInvestigation mentionedRestoration reported
    View on the provider's status page
  • Elevated 404s for GitHub App s2s tokens in git/APIOct 27 08:00 UTC · resolved
    Service restricted or degradedSign-in disruption
    View on the provider's status page
  • Incident with Actions, Issues, API Requests and Pull RequestsOct 26 18:48 UTC · resolved · minor impact
    Service restricted or degradedInvestigation mentionedRestoration reported
    View on the provider's status page
  • Grok 4.6 and Grok 4.7 Service IssuesOct 23 23:41 UTC · resolved · minor impact
    Service restricted or degradedInvestigation mentioned
    View on the provider's status page
  • Disruption with Dependabot AlertsOct 23 14:58 UTC · resolved · minor impact
    Service restricted or degradedInvestigation mentionedRestoration reported
    View on the provider's status page
  • Delayed Actions status check resultsOct 23 07:29 UTC · resolved · minor impact
    Service restricted or degradedInvestigation mentionedRestoration reported
    View on the provider's status page
  • Project updates delayedOct 22 15:28 UTC · resolved · minor impact
    Service restricted or degradedInvestigation mentionedRestoration reported
    View on the provider's status page
  • Incident with ActionsOct 22 14:18 UTC · resolved · minor impact
    Service restricted or degradedInvestigation mentionedRestoration reported
    View on the provider's status page
  • Delays for Pull Requests and Webhook deliveriesOct 21 14:52 UTC · resolved · critical impact
    Service restricted or degradedInvestigation mentionedRestoration reported
    View on the provider's status page
  • Degraded availability for GitHub Actions, GitHub Pages and WebhooksOct 19 15:49 UTC · resolved · critical impact
    Service restricted or degradedInvestigation mentionedRestoration reported
    View on the provider's status page
  • CCA Automations are delayed when starting an AutomationOct 15 18:31 UTC · resolved · minor impact
    Service restricted or degradedInvestigation mentioned
    View on the provider's status page
  • [Retroactive] Actions workflow run logs delayedOct 13 20:30 UTC · resolved · minor impact
    Service restricted or degradedRestoration reported
    View on the provider's status page

Documented dependents

Organisations publicly documented as relying on this provider. A relationship is not an impact.

GitHub
verified
  • GitBook Git SyncNo confirmed impact