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 contextA GitHub Ruleset Bypass Actor Is Not a Bypass Event, A repository can deliberately name the people, roles, teams, apps or keys that may bypass a GitHub ruleset. That is an important control decision. It is not a record that any one of them did so on a particular ref, and it is not a substitute for the separate records of review, merge, release or deployment.Medium confidence
- Editorial contextAn Archived GitHub Repository Is Not a Retirement Decision, GitHub’s archive control has a clear and useful job: it changes a repository’s platform state to read-only and signals that its owner no longer presents the project as actively maintained. That visible state can start a dependency review. It cannot decide, for a different organisation, whether a particular package, commit, build output or deployed asset has been retired.Medium confidence
- Editorial contextA CODEOWNERS File Is Not a Review Receipt, A `CODEOWNERS` file can tell GitHub where review responsibility should be routed for a changed path. That is useful machinery. It is not a historical record of who was selected for a particular pull request, whether the eligible person received or completed a review, or whether every other condition for merge was satisfied. Treating a rule file as proof of an event is how configuration quietly acquires authority it never recorded.Medium confidence
- Editorial contextGitHub's Attestation Proves a Build Path, Not a Safe Binary, A valid signature can establish where a binary came from while leaving the deployment decision unresolved. GitHub’s artifact attestation becomes a security control only when the consumer tests the recorded build route against an explicit trust policy.Medium confidence
- Editorial contextThe Cache That Answered 51,000 Times: Memcached and the Bandwidth Nobody Meant to Delegate, A reflector attack begins with a peculiar transfer of authority: one machine lies about who asked, another machine believes the return address, and a third party pays for the answer. In February 2018, public memcached servers made that transfer large enough to move GitHub's routes.Medium confidence
- Editorial contextGitHub says retries prolonged its 7h47 outage, GitHub’s new account of its 17 August disruption says a Central US capacity failure spread through shared authentication gateways, while repeated token requests kept part of the platform under pressure after most services had recovered.Medium 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
Source basis
- RIPE NCC member directory recordGitHub, Inc. appears in the RIPE NCC public member directory and registry-based country United States.High confidence
- RIPE NCC member detail pageThe RIPE NCC detail page provides member address, contact coverage, and areas-serviced context for GitHub, Inc..High confidence
Related research
- Primary articleA GitHub Ruleset Bypass Actor Is Not a Bypass EventHigh confidence
- Primary articleAn Archived GitHub Repository Is Not a Retirement DecisionHigh confidence
- Primary articleA CODEOWNERS File Is Not a Review ReceiptHigh confidence
- Primary articleGitHub's Attestation Proves a Build Path, Not a Safe BinaryHigh confidence
- Primary articleThe Cache That Answered 51,000 Times: Memcached and the Bandwidth Nobody Meant to DelegateHigh confidence
- Primary articleGitHub says retries prolonged its 7h47 outageHigh confidence
- 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 articleThe Return Address Nobody Had Verified: GitHub's 1.35 Tbps Memcached AttackHigh confidence
- Primary articleGitHub says retries prolonged its 7h47 outageHigh confidence
- Primary articleGitHub's 2012 Database Failovers Made Cluster State an Accountability BoundaryHigh 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 articleGitHub’s 105-minute incident turned one latency source into four work queuesHigh confidence
- Primary articleGitHub's 3% hosted-runner delay reveals the cost of a shared execution queueHigh confidence
- Primary articleGitHub's deploy-key failure turned a narrow credential into a delivery bottleneckHigh 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