LACNIC Network Infrastructure Profile

What to know first

IdentityLACNIC, RegistryHigh confidence
Registry relationship1 registry recordMedium confidence
Commercial servicesRegistry and RIR services · IndiaHigh confidence

Basic information

Display nameLACNICHigh confidence
Legal nameLACNICHigh confidence
Legal typeRegistryHigh confidence
Registration jurisdictionIndiaHigh confidence
HQ countryIndiaHigh confidence
Directory categoryRegistryHigh confidence
Last updatedJul 10, 2026High confidence

Locations

Geography scopeIndiaHigh confidence
Registry and RIR servicesIndiaMedium confidence

What it does

Registry and RIR servicesIndia, Unavailable, LACNIC is linked to Registry and RIR services records in India.High confidence

Other network resources

Registry recordLACNIC India registry/RIR service · IndiaHigh confidence

People and contacts

ContactsPolicyMedium confidence
Available contact typesPolicyMedium confidence

Source basis

Source basisPublic source recordHigh confidence
Source basisRIR · Public network recordHigh confidence

Related research

Primary articleLACNIC's legitimacy claim in regional registry governanceHigh confidence
Primary articleLACNIC 46 Shows Two Numbers. It Does Not Explain the GapHigh confidence
Primary articleThe Gateway That Points Back: A DHCP Draft Adds a Legacy-Client Escape HatchHigh confidence
Primary articleAn Internet address is not an Internet connectionHigh confidence
Primary articleThe Link Is Not the Block: Testing LACNIC’s Sub-Assignment RuleHigh confidence
Primary articleDigitel’s IPv6 Transition Had a Second Clock in Its RecordsHigh confidence
Primary articleLACNIC links an operator’s ASN to the freedom to change providersHigh confidence
Primary articleDíaz’s provider switch narrows the symptom, not the blockerHigh confidence
Primary articleLACNIC’s Caribbean satellite fallback depends on an unstated triggerHigh confidence
Primary articleFRIDA’s 2026 Call Cut Its Menu in Half. The Application Data Cannot Explain the ShiftHigh confidence
Primary articleDigitel says IPv6 reaches five million devices; DNS headroom remains unmeasuredHigh confidence
Primary articleLACNIC’s Board Ties Comisión Fiscal Access to Possible Financial Impact, but Does Not Define the TestHigh confidence
Primary articleThe LACNIC Board ballot is set for November. Its English call says October.High confidence
Primary articleWhy the IXP Ranking Counts São Paulo, Rio and Fortaleza SeparatelyHigh confidence
Primary articleCEDIA’s FIRST Talk Leaves Critical CSIRT Decisions With PeopleHigh confidence
Primary articleLACNIC’s Legacy Policy Page Leaves Its No-Consensus Timeline UnclearHigh confidence
Primary articleLACNIC’s Canary Guide Puts Grafana’s Detection Clock in FocusHigh confidence
Primary articleLACNIC’s Routing Lab Needs an Operational ReceiptHigh confidence
Primary articleLACNIC 46’s Hybrid Mix Includes 192 Remote RegistrationsHigh confidence
Primary articleLACNIC’s second-place IANA reviewer starts first—and the dates do not line upHigh confidence
Primary articleA Loop Is a Path Claim. An ASN Is an Inference.High confidence
Primary articleFive root-server letters, six listed instances: what Panama’s count can tell usHigh confidence
Primary articleLACNIC Adds ASPA Publishing to MiLACNIC; Uptake Is Still UncountedHigh confidence
Primary articleLACNIC’s Loop Study Moves 59 Cases into Intra-AS Under a Private-Hop RuleHigh confidence
Primary articleLACNIC 46 Registrations More Than Doubled. That Is Not AttendanceHigh confidence
Primary articleThe Legacy Host Went Quiet. Its IPv4 Lease Did Not.High confidence
Primary articleLACNIC’s 47-University Security Metric Leaves Its Denominator UnclearHigh confidence
Primary articleLACNIC Warned About Attendee-Database Emails. That Is Not Yet a Breach Notice.High confidence
Primary articleLACNIC's PDP Draft Asks Which Version Receives ConsensusHigh confidence
Primary articleLACNIC's ASN-Only Label Is Not a Test of Network UseHigh confidence
Primary articleLACNIC’s New Legacy Draft Makes Four Facts Share One TriggerHigh confidence
Primary articleLACNIC’s WHOIS Shows the Origin ASNs but Not Their Authorization BoundaryHigh confidence
Primary articleLACNIC’s New Transfer Draft Is a Policy Map, Not a CheckboxHigh confidence
Primary articleLACNIC Approved the Security Framework Before Measuring the Baseline. The Next Control Is a Versioned Maturity ReceiptHigh confidence
Primary articleRapport Counts Outcomes Only After a Requested Test Path ExistsHigh confidence
Primary articleLACNIC’s Election Upload Test Reads Bytes, Not Excel or PDFHigh confidence
Primary articleLACNIC’s Hackathon Repo Sends Agents to an Unpinned Sibling HarnessHigh confidence
Primary articleRapport’s Forbidden-AKI Test Starts at Barry, Not at the ValidatorHigh confidence
Primary articleThe RIR Draft Counts 1,000 Members, Not 1,000 VotesHigh confidence
Primary articleLACNIC’s Migration Script Reuses a Volume at a Different PathHigh confidence
Primary articleFORT’s Provider Cap Checks the Sum Before the UnionHigh confidence
Primary articleFORT’s Snapshot Patch Changes the Rebuild, Not the Meaning of a Good HashHigh confidence
Primary articleTwo Minutes Can Become Many in LACNIC’s Permission CacheHigh confidence
Primary articleLACNIC 46 Says Blocking Is Now Reactive. Its Public Agenda Does Not Show the Coding RuleHigh confidence
Primary articleLACNIC's Election Recovery Defaults to ALL. One Email Search Reaches Vote, Nomination and Support LinksHigh confidence
Primary articleLACNIC's 12,609-Organisation Electoral Roll Has No Revision ClockHigh confidence
Primary articleLACNIC’s AI Client Resolves a Model, Then Chats Without a Resolution IDHigh confidence
Primary articleLACNIC Asked for a Technical-Committee Charter. Its First Committee Ran the Registry.High confidence
Primary articleLACNIC Counts 2.223 Billion BGP Messages. Its Family Table Totals 853 Million UpdatesHigh confidence
Primary articleLACNIC Signs 150 Reverse-DNS Files. The Batch Has No Manifest.High confidence
Primary articleLACNIC’s BGP Case Counts 368 Route Peers. The Vendor Could Not Produce a Definitive Installation List.High confidence
Primary articleLACNIC's Open-Source Election Lookup Puts the Email Address in the Request PathHigh confidence
Primary articleLACNIC’s IPv6 Clock Subtracts 210 `/32`s Without Showing Which Fragments CountHigh confidence
Primary articleLACNIC’s Highest Risks Have Two Clocks and No Public Start PointHigh confidence
Primary articleRapport Tests Cache Survival. Its Missing-Manifest Warning Is Still Commented OutHigh confidence
Primary articleLACNIC Listed 32 Resources for December Revocation. That Is Not 32 Cases.High confidence
Primary articleLACNIC Budgets a $390,000 Operating Gap. Financial Results Close All but $87,000 on PaperHigh confidence
Primary articleLACNIC’s ASPA Explainer Cites a Moving Percentage Without a SnapshotHigh confidence
Primary articleLACNIC 46's Attendee List Has Consent. It Still Needs a Retention ClockHigh confidence
Primary articleLACNIC’s Autonomous-Network Ladder Needs a Scenario Ledger, Not a Company BadgeHigh confidence
Primary articleLACNIC’s Abuse-Contact Lockout Sits Outside the Policy ManualHigh confidence
Primary articleA LACNIC Telecom Essay Moves Voice to IP. It Leaves Backup Power Unassigned.High confidence
Primary articleLACNIC's RDAP delegationSigned Records Parent DS Presence, Not DNSSEC ValidationHigh confidence
Primary articleLACNIC Deferred Its $2,100 IPv6-Only Fee to 2029. The 2020 Notice Still Ends the Waiver in 2026High confidence
Primary articleLACNIC Says to Email the Bulk WHOIS Form. The Same Page Says Email Is Not AcceptedHigh confidence
Primary articleLACNIC Whois created Dates the Registry Record, Not the Network's LaunchHigh confidence
Primary articleLACNIC Made Merger Transfer Fees Equal. It Did Not Make the Payment Rules EqualHigh confidence
Primary articleLACNIC Whois routing-c Can Register Routing Policy, Not Prove Who Operates BGPHigh confidence
Primary articleBarry’s README Uses the IPv6 Prefix Its Lexer RejectsHigh confidence
Primary articleLACNIC’s PAI Client Documents Java 8. Its Latest JAR Requires Java 17High confidence
Primary articleLACNIC Whois owner-c Marks Administrative Authority, Not Network OperationHigh confidence
Primary articleA Splice Is Not a Recovery. Venezuela’s Atlas Study Needs the Events in OrderHigh confidence
Primary articleLACNIC WHOIS nslastaa Records the Last Successful Check, Not Current DNS HealthHigh confidence
Primary articleLACNIC’s IRR turns route filters into a derived registry viewHigh confidence
Primary articleLACNIC Geofeeds makes IP location a maintained claim, not a registry factHigh confidence
Primary articleLACNIC’s RDAP shift turns registry data into an automation contractHigh confidence
Primary articleThe root KSK rollover makes resolver readiness the real continuity testHigh confidence
Primary articleLACNIC’s reverse-DNS anycast turns registry continuity into a distributed controlHigh confidence
Primary articleLACNIC’s measurement commons turns regional latency into operating evidenceHigh confidence
Primary articleLACNIC’s RPKI controls make route origin authority operableHigh confidence
Primary articleLACNIC’s IPv6 allocation rules make scale plannableHigh confidence
Primary articleLACNIC’s 2025 Path Study Does Not Date Its MeasurementsHigh confidence
Primary articleLACNIC 46's Machine Records Still Say LACNIC 39 and LACNIC 45High confidence
Primary articleLACNIC’s RDAP Name Is a Registration Label, Not a Legal or Routing IdentityHigh confidence
Primary articleLACNIC’s RDAP Self Link Locates the Record, Not the Network’s Serving InfrastructureHigh confidence
Primary articleLACNIC’s RDAP Conformance List Identifies Response Specifications, Not Network AuthorityHigh confidence
Primary articleLACNIC’s IPv4 transfer market and the price of scarcityHigh confidence
Primary articleOne Prefix, Two Countries in LACNIC’s GeofeedHigh confidence
Primary articleLACNIC’s Voice Primer and the Bandwidth Beyond the CodecHigh confidence
Primary articleThe Refill Behind LACNIC’s Falling ASN ForecastHigh confidence
Primary articleLACNIC’s fee schedule and the price of a durable registryHigh confidence
Primary articleLACNIC Ratified the Sub-Assignment Rule. An Operating Log Still Needs Its Own Receipt.High confidence
Primary articleLACNIC and the economics of rough consensusHigh confidence
Primary articleLACNIC and the economics of transition architecture beyond RIRsHigh confidence
Primary articleLACNIC’s Bogon Guide Has Three Different Data Clocks.High confidence
Primary articleLACNIC's Board Is Nine Members. Its Public Description Still Says SevenHigh confidence
Primary articleLACNIC’s FORT Guide Skips the Signature Published Beside Its TarballHigh confidence
Primary articleLACNIC Calls Postman Its Current API. The Website Still Says ROAs Change by Serial NumberHigh confidence
Primary articleLACNIC Published a 98% Outreach Score. The Response Count Is MissingHigh confidence
Primary articleLACNIC Reported 99.5% Completion. An Earlier 98% Minute Also Recorded 6% Cancelled ActionsHigh confidence
Primary articleLACNIC’s TAL Page Shows Two URLs and Links to Two OthersHigh confidence
Primary articleLACNIC's Delegation File Declares 49,894 Records. It Contains 48,214High confidence
Primary articleLACNIC’s Revocation List Shows a /23 in 2023 and a Nested /24 in 2026High confidence
Primary articleLACNIC's Four-Vendor BGP Claim Needs the Configuration ColumnHigh confidence
Primary articleOne LACNIC Office Has Three Public Calendar StatesHigh confidence
Primary articleLACNIC’s 70% Pass Mark Is Not a Candidacy ReceiptHigh confidence
Primary articleLACNIC and the economics of legitimacy after scandalHigh confidence
Primary articleLACNIC's FORT Can Validate ASPA. Its Router Feed Defaults to Version 0High confidence
Primary articleLACNIC and the economics of IANA recognition and franchise riskHigh confidence
Primary articleLACNIC and the economics of NRO coordination incentivesHigh confidence
Primary articleOne Meeting, Two Public States: The Transition Record LACNIC 46 RequiresHigh confidence
Primary articleLACNIC and the economics of ICP-2 reformHigh confidence
Primary articleA Private Registry Still Needs Public LimitsHigh confidence
Primary articleA Court Order Is Not a Registry RunbookHigh confidence
Primary articleLACNIC’s 11 IXP Collectors Need a Vantage-Point ReceiptHigh confidence
Primary articleThe Estate Cannot Route ItselfHigh confidence
Primary articleLACNIC Cut Its Recovery Window to Three Months in 2015. One Procedure Page Still Says SixHigh confidence
Primary articleSix Minutes Are Published. LACNIC’s Summary Column Says NothingHigh confidence
Primary articleBetween Listening and the Map: LACNIC’s Missing Input TraceHigh confidence
Primary articleLACNIC’s RDAP Last Changed Event Dates the Registry Record, Not the Network HandoverHigh confidence
Primary articleThe Seller’s Last Login: Why a LACNIC Deal Can Close Before Its Addresses MoveHigh confidence
Primary articleThe Prefix in the Credit File: What a LACNIC Lender Can Actually RecoverHigh confidence
Primary articleThree LACNIC Numbers an IPv4 Accounting Memo Must Not CollapseHigh confidence
Primary articleLACNIC Turns IPv4 Value Into a Chain of ProofHigh confidence
Primary articleAt LACNIC, the Most Valuable IPv4 Option Is WaitingHigh confidence
Primary articleAt LACNIC, a New ISP Must Prove Need Before It Can Pay $8,000 for IPv4High confidence
Primary articleLACNIC’s Last Waitlist Applicant Faces 12 Years for at Most 1,024 AddressesHigh confidence
Primary articleLACNIC’s Election Commission Can Assign a Candidate to a Country They Are Not a Citizen OfHigh confidence
Primary articleTrusted channels, no command: who can speak for FIRST in a cyber crisis?High confidence
Primary articleLACNIC's ASO AC Result Became Official Without a Closure ReceiptHigh confidence
Primary articleLACNIC's Anti-Fake-IXP Log Has No Event ColumnHigh confidence
Primary articleThree National Registers Expose the Gap Behind LACNIC's No-Consensus ResultHigh confidence
Primary articleLACNIC's Legacy Deadline Is Running Ahead of Its PolicyHigh confidence
Primary articleLACNIC's 80% ROA Draft Ties New Addresses to Old Route RecordsHigh confidence
Primary articleThe missing disposition in LACNIC’s 2026 Review Committee voteHigh confidence
Primary articleLACNIC Counted 978 Organisations and 2,145 Weighted Votes. One Denominator Is Still Missing.High confidence
Primary articleLACNOG’s workshops put routing-security practice in the roomHigh confidence
Primary articleFrom Custody to Capacity: What LACNOG’s Incorporation Actually ChangedHigh confidence
Primary articleLACNIC utilisation audits in the acquisition data roomHigh confidence
Primary articleCloud NAT control and credible exit for LACNIC-region workloadsHigh confidence
Primary articleShared IPv4 identity under LACNIC scarcity when CGNAT failures become evidence disputesHigh confidence
Primary articleWho ultimately carries dual-stack costs under LACNIC IPv4 scarcity?High confidence
Primary articleWhy IPv6 deployment does not end LACNIC's IPv4 dependency problemHigh confidence
Primary articleEmerging-market growth when LACNIC-recognised identity lags demandHigh confidence
Primary articleEqual LACNIC charges and unequal burdens in low-income marketsHigh confidence
Primary articleIsland network redundancy and the LACNIC record that must survive restorationHigh confidence
Primary articleRural connectivity under LACNIC scarcity when few lines carry fixed obligationsHigh confidence
Primary articleSmall ISP entry in the LACNIC region before the first invoiceHigh confidence
Primary articleHow LACNIC registry decisions travel into customer continuity riskHigh confidence
Primary articleReverse DNS delegation and LACNIC's leverage over exit and transferHigh confidence
Primary articleLACNIC ROA revocation as an immediate continuity shockHigh confidence
Primary articleFragmented IRR evidence and the transaction burden on LACNIC IPv4 marketsHigh confidence
Primary articleWhat LACNIC route objects decide in transfers, leases and upstream changesHigh confidence
Primary articleRouting-security evidence as LACNIC infrastructure for accepted IPv4 useHigh confidence
Primary articleLACNIC fraud checks and the risk of discretionary holder controlHigh confidence
Primary articleWhen LACNIC registry cleanliness cannot erase IPv4 reputation memoryHigh confidence
Primary articleSuballocation visibility at LACNIC between privacy and operational proofHigh confidence
Primary articleIPv4 leasing contracts beyond the reach of LACNIC's thin ledgerHigh confidence
Primary articleDelay, reversibility and the LACNIC discount on usable IPv4High confidence
Primary articleWhy the title-insurance analogy matters for LACNIC address recordsHigh confidence
Primary articleCan a thin LACNIC ledger improve IPv4 price evidence?High confidence
Primary articleEscrow, finality and LACNIC transfer records at the closing deskHigh confidence
Primary articleIPv4 brokers and the line LACNIC must hold as ledger keeperHigh confidence
Primary articleLACNIC university legacy space between campus memory and future option valueHigh confidence
Primary articlePublic-sector reachability and the quiet force of LACNIC registry continuityHigh confidence
Primary articleEnterprise legacy holders and the LACNIC evidence value of old IPv4 blocksHigh confidence
Primary articleCarrier-grade NAT in LACNIC mobile broadband and the support burden it hidesHigh confidence
Primary articleWhat data-centre IPv4 demand asks of LACNIC registry recordsHigh confidence
Primary articleCloud address inventory as bargaining leverage in the LACNIC regionHigh confidence
Primary articleLACNIC address identity after a submarine cable failureHigh confidence
Primary articleWhen LACNIC address records shape interconnection bargainingHigh confidence
Primary articleLACNIC cross-border transfers and the proof burdens on liquidityHigh confidence
Primary articleLACNIC portability under pressure from geopolitical fragmentationHigh confidence
Primary articleLACNIC sanctions screening without turning evidence checks into continuity shocksHigh confidence
Primary articleWhen LACNIC's regional ledger meets domestic capital claimsHigh confidence
Primary articleLACNIC NIR relationships and the bargain of layered registry accessHigh confidence
Primary articleLACNIC language barriers where policy meaning affects address rightsHigh confidence
Primary articleDo LACNIC hybrid meetings change influence or just attendance?High confidence
Primary articleLACNIC representation after the costs of showing upHigh confidence
Primary articleWhy silence is unstable evidence of consent at LACNICHigh confidence
Primary articleWho frames the problem in LACNIC scarce-address policy?High confidence
Primary articleLACNIC chair discretion and the value moved by procedural callsHigh confidence
Primary articleThe participation tax inside LACNIC policy proposalsHigh confidence
Primary articleWhen LACNIC expertise becomes leverage over the ledgerHigh confidence
Primary articleLACNIC corruption controls for value that moves quietlyHigh confidence
Primary articleLACNIC receivership and the continuity test for emergency controlHigh confidence
Primary articleLACNIC address disputes before the final answer arrivesHigh confidence
Primary articleLACNIC appeals as part of pricing administrative riskHigh confidence
Primary articleLACNIC identity checks and the authority to speak for a holderHigh confidence
Primary articleWhen LACNIC transfer proof starts to resemble capital controlHigh confidence
Primary articleLACNIC abuse contacts between notice and overreachHigh confidence
Primary articleWhat LACNIC RDAP and Whois records should make visibleHigh confidence
Primary articleLACNIC reverse DNS continuity and the value of weak evidenceHigh confidence
Primary articleLACNIC RPKI governance when certification affects market accessHigh confidence
Primary articleThe LACNIC database record that counterparties can rely onHigh confidence
Primary articleLACNIC RPKI Governance Risk: Routing Trust Needs Administrative RestraintHigh confidence
Primary articleLACNIC Database Accuracy As Market Infrastructure: The Quiet Ledger Behind IPv4 LiquidityHigh confidence
Primary articleLACNIC's Enforcement BoundaryHigh confidence
Primary articleWhen Legal Capacity Becomes Governance CapitalHigh confidence
Primary articleLACNIC's reserve policy discipline problemHigh confidence
Primary articleWhere LACNIC ledger maintenance stops becoming enforcement leverageHigh confidence
Primary articleWhat LACNIC's legal budget changes in registry bargainingHigh confidence
Primary articleLACNIC reserve policy and the insulation of registry capitalHigh confidence
Primary articleLACNIC's continuing legitimacy after the exhaustion pointHigh confidence
Primary articleWhat recovery asks of LACNIC after governance failureHigh confidence
Primary articleLACNIC's fee and reserve structure as an incentive bargainHigh confidence
Primary articleWhen consensus at LACNIC becomes a capture riskHigh confidence
Primary articleWhat LACNIC transparency requires from the audit recordHigh confidence
Primary articleSmall operator dependency in LACNIC's registry compactHigh confidence
Primary articleLACNIC inter-RIR transfers and the politics of external accessHigh confidence
Primary articleLACNIC's conservation rhetoric and the limits of allocation authorityHigh confidence
Primary articleLACNIC's legacy allocation title problemHigh confidence
Primary articleWhat court process can unsettle in LACNIC continuity planningHigh confidence
Primary articleLACNIC board elections and the credibility of consentHigh confidence
Primary articleWho participates through LACNIC's policy mailing-list process?High confidence
Primary articleCapital-control logic inside LACNIC's registry rule setHigh confidence
Primary articleWhen mandate claims stretch LACNIC's registry remitHigh confidence
Primary articleLACNIC registry compliance under sanctions pressureHigh confidence
Primary articleIPv4 leasing at LACNIC and the allocation work done off-ledgerHigh confidence
Primary articleThe rule architecture behind LACNIC's transfer marketHigh confidence
Primary articleScarce IPv4 addresses and LACNIC's allocation discretionHigh confidence
Primary articleWhen LACNIC's registry ledger carries gatekeeping forceHigh confidence
Related articleWhat determines IPv4 leasing costs: beyond the per-IP rateMedium confidence
Related articleIPv4 Scarcity and the RIR Poverty PenaltyMedium confidence

LACNIC

What to know first

Basic information

Locations

What it does

Other network resources

People and contacts

Registry and related records

Source basis

Related research