Network operator associated with ASN/IP network resources
GitHub, Inc.
GitHub, Inc. is connected with ASN/IP network resources in United States.
- Network operator associated with ASN/IP network resources
- United States
What to know first
- IdentityGitHub, Inc., Private company, CompanyHigh confidence
- Registry relationship1 RIR membership record · United StatesMedium confidence
Basic information
- Display nameGitHub, Inc.High confidence
- Legal nameGitHub, Inc.High confidence
- Legal typePrivate companyHigh confidence
- Registration jurisdictionUnited StatesHigh confidence
- HQ countryUnited StatesHigh confidence
- Directory categoryCompanyHigh confidence
- Last updatedJun 18, 2026High confidence
Locations
- Geography scopeUnited StatesHigh confidence
- ASN/IP network resourcesUnited StatesMedium confidence
Registry and related records
- Registry and industry relationshipRegional Internet Registry membership record, United StatesHigh confidence
- Editorial contextGitHub’s Actions postmortem turns a routine deployment into a queue-recovery lesson, GitHub’s 11 August account of its earlier Actions failure identifies two linked breakdowns: replacement pods exhausted already-thin capacity, then runners kept asking for jobs that were no longer valid. Service returned on 7 August, but the postmortem shows why a green status light cannot by itself reconcile every workflow left behind.Medium confidence
- Editorial contextGitHub restored Copilot after multi-model request failures exposed a shared work queue, GitHub resolved a 92-minute Copilot incident after chat and agent requests across multiple models suffered degraded availability. The service recovered, but the public record leaves enterprises without the denominator needed to judge how much work failed, waited or succeeded on retry.Medium confidence
- Editorial contextGitHub took 17 minutes to name Fable 5 after upstream model errors began, GitHub’s second public Copilot model-provider incident on 1 August began with generic reports of upstream errors and only later identified Fable 5. Mitigation followed 28 seconds after that model-specific disclosure. The chronology shows fast recovery once the route was named, but not whether discovery itself or public attribution consumed the preceding 17 minutes.Medium confidence
- Editorial contextGitHub restored GPT-5.6 Luna after 74 minutes, but the incident exposes a model-routing dependency, GPT-5.6 Luna became degraded across GitHub Copilot products and IDE surfaces because of an unnamed upstream model provider on 1 August. GitHub offered a practical escape route—choose another model or Auto—but published no measure of how many requests failed or what functional trade-off the substitution imposed.Medium confidence
- Editorial contextGitHub's 2015 Great Cannon DDoS Made On-Path Code Injection a Network Accountability Test, The 2015 attack on GitHub showed that network accountability begins with the bytes a user actually receives, not merely the address, certificate, contract or status page associated with a service.Medium confidence
- Editorial contextGitHub's 2018 Memcached Attack Made Anti-Spoofing and Mitigation Handoff an Accountability Test, GitHub's response to a 1.35-terabit-per-second attack showed that DDoS resilience depends on more than buying bandwidth: operators must detect abnormal traffic, move routing authority safely, preserve clean delivery and reduce the spoofing conditions that make reflection possible.Medium confidence
- Editorial contextGitHub’s outage numbers trace six products back to one lost network quarter, GitHub’s July 29 root-cause update turns a broad service incident into a physical capacity story. On July 24, links between one compute cage’s spine switches and an availability zone’s aggregation layer lost connectivity; the surviving paths saturated, one quarter of interconnect capacity disappeared, and failures surfaced differently in Actions, Issues, Copilot, pushes and authentication.Medium confidence
- Editorial contextGitHub resolved a 16-minute GraphQL incident before explaining its scope, GitHub reported degraded API-request performance from 03:53:19 UTC, posted mitigation at 04:09:01 and resolution at 04:09:10—about 16 minutes. The incident title named GraphQL API requests while the update text referred to API Requests more broadly; magnitude and cause were not published.Medium confidence
Related research
- Primary articleGitHub’s Actions postmortem turns a routine deployment into a queue-recovery lessonHigh confidence
- Primary articleGitHub restored Copilot after multi-model request failures exposed a shared work queueHigh confidence
- Primary articleGitHub took 17 minutes to name Fable 5 after upstream model errors beganHigh confidence
- Primary articleGitHub restored GPT-5.6 Luna after 74 minutes, but the incident exposes a model-routing dependencyHigh confidence
- Primary articleGitHub's 2015 Great Cannon DDoS Made On-Path Code Injection a Network Accountability TestHigh confidence
- Primary articleGitHub's 2018 Memcached Attack Made Anti-Spoofing and Mitigation Handoff an Accountability TestHigh confidence
- Primary articleGitHub’s outage numbers trace six products back to one lost network quarterHigh confidence
- Primary articleGitHub resolved a 16-minute GraphQL incident before explaining its scopeHigh confidence
- Primary articleGitHubs Datenbank-Failover von 2012 machte den Clusterzustand zur VerantwortungsgrenzeHigh confidence
- Primary articleDer GitHub-Bericht trennt die Wiederherstellung von Actions von der Aufarbeitung jedes WorkflowsHigh confidence
- Primary articleتقرير GitHub يوضح لماذا لا تنتهي أزمة Actions بمجرد عودة الخدمةHigh confidence
- Primary articleO pós-incidente do GitHub mostra por que recuperar o Actions não encerra a conferência dos workflowsHigh confidence
- Primary articleGitHub Actions障害の事後分析、復旧後にも残るジョブ照合の課題を示すHigh confidence
- Primary articleGitHub Actions 复盘揭示：服务恢复不等于任务已经对账High confidence
- Primary articleEl informe de GitHub separa la recuperación de Actions de la conciliación de cada workflowHigh confidence
- Primary articleLe post-mortem de GitHub relie la saturation d’Actions aux tâches devenues invalidesHigh confidence
- Primary articleGitHub stellte Copilot wieder her, doch der Status ließ angenommene Agentenarbeit offenHigh confidence
- Primary articleاستعادت GitHub خدمة Copilot وبقي أثر الطلبات بين الفشل وإعادة المحاولة بلا قياسHigh confidence
- Primary articleGitHub recuperou o Copilot, mas não mediu o que ficou entre falha e reenvioHigh confidence
- Primary articleGitHubはCopilotを復旧、複数モデル障害の「処理済み」と「再試行」の境界は残ったHigh confidence
- Primary articleGitHub恢复Copilot后，未解释多模型请求为何共同失灵High confidence
- Primary articleLa avería de Copilot cruzó varios modelos y dejó sin medir el coste de cada reintentoHigh confidence
- Primary articleGitHub a rétabli Copilot sans encore donner la mesure de la panne multi-modèleHigh confidence
- Primary articleGitHub brauchte 17 Minuten, um aus Upstream-Fehlern den betroffenen Fable-5-Pfad zu benennenHigh confidence
- Primary articleاحتاجت GitHub إلى 17 دقيقة للانتقال من أخطاء منبع عامة إلى تسمية Fable 5High confidence
- Primary articleGitHub levou 17 minutos para transformar erros upstream em um alerta específico sobre Fable 5High confidence
- Primary articleGitHubは上流エラー検知から17分後にFable 5を特定したHigh confidence
- Primary articleGitHub先看到上游错误，17分钟后才把Fable 5写进事件记录High confidence
- Primary articleEl segundo incidente de modelos de GitHub tardó 17 minutos en señalar a Fable 5High confidence
- Primary articleGitHub a mis dix-sept minutes à passer d’erreurs amont génériques au modèle Fable 5High confidence
- Primary articleBei der GPT-5.6-Luna-Störung wurde die Modellwahl selbst zum Ausweichpfad für CopilotHigh confidence
- Primary articleكشف تعطل GPT-5.6 Luna أن اختيار النموذج أصبح مسار استمرارية داخل CopilotHigh confidence
- Primary articleFalha do GPT-5.6 Luna fez da escolha de modelo uma camada de continuidade do CopilotHigh confidence
- Primary articleGitHubのGPT-5.6 Luna障害、モデル選択そのものがCopilotの迂回路になったHigh confidence
- Primary articleGPT-5.6 Luna恢复前，GitHub把“换模型”变成了Copilot的连续性方案High confidence
- Primary articleLa degradación de GPT-5.6 Luna convirtió la selección de modelo en una ruta de contingenciaHigh confidence
- Primary articleLa panne de GPT-5.6 Luna montre que la continuité de Copilot dépend aussi du routage entre modèlesHigh confidence
- Primary articleGitHubs verlorenes Netzviertel hinterließ fünf verschiedene AufräumarbeitenHigh confidence
- Primary articleخسرت GitHub ربع سعة الربط فتركت خمس مهام تعافٍ مختلفةHigh confidence
- Primary articleA GitHub perdeu 25% da interconexão e devolveu cinco problemas diferentesHigh confidence
- Primary articleGitHub障害は「25％の容量喪失」を五つの復旧作業へ変えたHigh confidence
- Primary articleGitHub 丢掉四分之一互联容量后，五种业务留下五套善后High confidence
- Primary articleGitHub perdió un cuarto de interconexión y cada producto dejó una deuda distintaHigh confidence
- Primary articleChez GitHub, la perte d’un quart du réseau est devenue cinq files d’attenteHigh confidence
- Primary articleGitHub löste den GraphQL-Vorfall nach rund 16 MinutenHigh confidence
- Primary articleحلت GitHub حادث GraphQL في 16 دقيقة وبقي النطاق غامضاًHigh confidence
- Primary articleGitHub resolveu a degradação em 16 minutos, mas não seu custo localHigh confidence
- Primary articleGitHubは約16分で解決したがGraphQLとAPIの範囲表現が残ったHigh confidence
- Primary articleGitHub约16分钟内解决GraphQL事故，但范围用词仍有差异High confidence
- Primary articleGitHub resolvió en unos 16 minutos una degradación titulada GraphQLHigh confidence
- Primary articleGitHub a résolu en 16 minutes un incident GraphQL au périmètre imprécisHigh confidence
- Primary articleGitHubs zweiter Vorfall in zwei Tagen ist kein Beleg für dieselbe UrsacheHigh confidence
- Primary articleأصل عطل GitHub ما زال غير منشور رغم استعادة الخدماتHigh confidence
- Primary articleWebhooks em atraso prolongam a recuperação para fora do GitHubHigh confidence
- Primary articleGitHubの重大インシデントは1時間45分20秒で終わったHigh confidence
- Primary articleGitHub修复延迟源之后，处理积压仍让恢复分阶段发生High confidence
- Primary articleLa demora de Actions convierte el tiempo de CI en una cola sin horizonte claroHigh confidence
- Primary articleUne recherche Issues périmée transforme la latence en risque de décisionHigh confidence
- Primary articleGitHub’s 105-minute incident turned one latency source into four work queuesHigh confidence
- Primary articleGitHubs Drei-Prozent-Verzögerung macht die Warteschlange zur ProduktionsabhängigkeitHigh confidence
- Primary articleتأخر 3% من مشغلات GitHub يكشف أن الطابور جزء من الإنتاجHigh confidence
- Primary articleO atraso de 3% no GitHub mostra que a fila também faz parte da produçãoHigh confidence
- Primary articleGitHubの3％遅延は実行待ち行列も本番依存であることを示したHigh confidence
- Primary articleGitHub托管runner延迟说明：队列本身也是生产依赖High confidence
- Primary articleEl retraso del 3 % en GitHub muestra que la cola también es infraestructuraHigh confidence
- Primary articleChez GitHub, 3 % de files retardées suffisent à bloquer une mise en productionHigh confidence
- Primary articleGitHub's 3% hosted-runner delay reveals the cost of a shared execution queueHigh confidence
- Primary articleGitHubs Deploy-Key-Störung machte einen engen Zugang zum breiten EngpassHigh confidence
- Primary articleعطل deploy key في GitHub حوّل صلاحية ضيقة إلى عنق زجاجة واسعHigh confidence
- Primary articleUma deploy key estreita do GitHub expôs uma dependência ampla de automaçãoHigh confidence
- Primary articleGitHubのdeploy key障害、狭い認証経路が広い自動化を止めたHigh confidence
- Primary articleGitHub一类窄权限部署密钥，暴露出宽范围自动化依赖High confidence
- Primary articleUna deploy key de GitHub falló de forma estrecha y frenó automatizaciones enterasHigh confidence
- Primary articleChez GitHub, une clé de déploiement étroite a bloqué des chaînes plus largesHigh confidence
- Primary articleGitHub's deploy-key failure turned a narrow credential into a delivery bottleneckHigh confidence
- Primary articleGitHub-Actions-Störung griff auf APIs und externe Lieferketten überHigh confidence
- Primary articleعطل GitHub Actions يمتد إلى واجهات البرمجة وسلاسل التسليم الخارجيةHigh confidence
- Primary articleFalha no GitHub Actions avançou sobre APIs e cadeias externas de entregaHigh confidence
- Primary articleGitHub Actions 故障外溢至 API 与下游交付链路High confidence
- Primary articleLa caída de GitHub Actions alcanzó las API y los flujos de entrega externosHigh confidence
- Primary articleLa panne de GitHub Actions a gagné les API et les chaînes de livraison externesHigh confidence
- Primary articleGitHub Actions outage spread to APIs, Pages and downstream workflowsHigh confidence
- Primary articleGitHub made Actions recovery a CI dependency-accountability testHigh confidence
- Primary articleGitHub token exposure made Slack repair a cost-transfer accountability testHigh confidence
- Primary articleGitHub made host-key rotation a contract-versus-control accountability testHigh confidence
- Primary articleGitHub's AI value is measured at the accepted pull requestHigh confidence
- Primary articleThe morning GitHub's correct security response looked exactly like an attackHigh confidence
- Primary articleGitHub's developer seat carries delivery riskHigh confidence