Summary

  • Sogaz is not an internet carrier in any ordinary economic sense. It is a large Russian insurer whose public routing footprint is evidence of internal control over digital continuity, mail, edge services and security operations. The infrastructure matters because the insurer handles high-value industrial clients, regulated claims, medical authorizations and sanctioned counterparty risk.
  • The available evidence supports a limited justification for keeping network control in-house: two small business ASNs, four visible /24 IPv4 blocks, domestic upstreams, mail-host traces, security recruiting and a digital retail surface. That looks more like enterprise resilience than a growth business.
  • The investment only earns its keep if it reduces outage cost, data-loss risk, claims leakage and counterparty friction. It would not be justified as a vanity network, as a substitute for disciplined claims operations, or as a way to avoid measurable service performance.
  • The largest reversal facts would be evidence that the public ASNs carry little production load, that most critical services are already outsourced to more resilient providers, or that Sogaz's own control boundary creates more concentration risk than it removes.

The Premium That Buys Continuity

The clean way to read Sogaz is to start with the premium. A customer pays the insurer because an uncertain loss is more bearable when converted into a known cost. That bargain depends on actuarial judgment, reserves, investment returns, claims discipline and trust. It does not, at first glance, depend on owning address space or running an autonomous system.

Yet the largest insurance companies are not just financial intermediaries. They are information-processing machines. They price industrial hazards, handle medical permissions, receive documents, authorize repairs, pay claims, manage fraud, satisfy regulators and communicate with policyholders at moments when delay feels like breach. A large insurer that loses digital availability at the wrong time does not merely inconvenience customers. It creates payment backlogs, compliance exposure, customer churn, branch overload and reputational cost.

A company with a high share of corporate, medical and regulated lines has more reason than a small retail broker to ask whether a controlled network edge is part of the product.

That is the frame for Insurance Company of Gaz Industry Sogaz, Joint-Stock Company. The public record says the company is a Russian insurer, founded in the Gazprom orbit and now one of the central institutions of the Russian insurance market. Its official disclosure gives the legal name, registration numbers, Bank of Russia insurance-register number 1208, Moscow headquarters and charter capital of 30.1 billion roubles. Its own corporate profile says the group was founded in 1993, offers more than 100 insurance programs, operates more than 1,000 offices or sales units and employs more than 14,000 professionals.

The Bank of Russia register confirms active status and the same identifying data.

The scale is not cosmetic. A Sogaz release citing Bank of Russia data says that in 2024 the company collected more than 260 billion roubles in premiums in insurance other than life and paid clients more than 145 billion roubles. For the first half of 2025 it reported more than 140 billion roubles of premiums and more than 79 billion roubles of payouts. ACRA's May 2026 rating release says Sogaz's group share at the end of 2025 was above 17% in non-life insurance and above 14% in life insurance. Expert RA and NCR both place Sogaz at the top end of their domestic rating scales.

On a national insurance map, this is not a peripheral writer of household policies. It is a systemically relevant balance sheet.

That matters because the fixed cost of infrastructure is easier to justify when the operating base is large. A 512-address corporate network is wasteful for a narrow local underwriter; it may be rational for an insurer that processes hundreds of billions of roubles of premiums and claims and interacts with hospitals, banks, industrial clients, public-sector groups and motorists. The economic question is not whether Sogaz should have information systems. Of course it should.

The question is how far ownership and control should extend before internal infrastructure stops being resilience and becomes another fixed cost protected by institutional inertia.

What Sogaz Sells

Sogaz sells risk transfer across a broad range of Russian insurance lines. Its public pages present consumer products such as OSAGO motor liability insurance, travel insurance, apartment insurance, voluntary medical insurance, telemedicine, student medical insurance and other personal lines. Its corporate pages are more revealing. They include liability insurance for legal entities, hazardous-facility liability, carrier liability, aviation and space risk, nuclear-sector programs and gas-sector insurance. The company repeatedly describes itself as a provider for systemically important Russian corporations and their employees.

This mixture is crucial. A pure retail motor insurer can buy cloud services, rely on aggregators and compete on price, claim speed and marketing. A corporate industrial insurer has a different operating burden. It must underwrite complicated assets, interpret engineering documentation, manage high-severity low-frequency claims, arrange reinsurance, keep privileged customer data secure and remain reachable during physical disruption. When the client base includes gas infrastructure, rail, nuclear, defense-linked or other strategic sectors, service continuity is part of the promise even if it is not printed as a line item on the invoice.

The market data reinforce that Sogaz's center of gravity is not ordinary retail. Interfax, citing Bank of Russia statistics, reported that Sogaz led the 2024 market for mandatory liability insurance of hazardous-facility owners with 853.4 million roubles of premium and a 29.3% share. Sogaz's own sector materials emphasize gas, nuclear, aviation and other industrial risks. A 2026 legal publication records a Gazprom property insurance contract with Sogaz connected to gas-transmission property.

That does not mean every rouble of Sogaz revenue comes from heavy industry, but it confirms the kind of risk book in which downtime, documentation, communications integrity and claim coordination have strategic value.

The retail book still matters because it produces visible service stress. OSAGO is regulated, high-volume and complaint-sensitive. Voluntary medical insurance requires authorization workflows and policyholder data. Household and mortgage policies create small claims where customer tolerance for friction is low. The Bank of Russia published an OSAGO complaint ranking for 2024 based on confirmed complaints per 10,000 contracts. A Rossiyskaya Gazeta summary of that release put Sogaz at the top of the large-insurer group by the consumer-risk indicator.

Review platforms add a rougher but useful signal: Banki.ru shows many negative OSAGO comments; Otzovik carries complaints about electronic OSAGO; Medadvisor has complaints about voluntary medical insurance permissions; TBank reviews show a more positive aggregate score but still include digital-service frustrations.

Unofficial reviews are not audited performance data. They are biased toward complaint and gratitude, not a representative sample. But they tell us what kind of operating failure customers notice: inability to edit a policy, slow callbacks, claim delays, unclear application status, weak guarantees for medical service, and trouble completing online insurance. Those are not solved by address space alone. They are solved by product design, staffing, claims governance and provider networks. But the existence of those complaints raises the cost of digital unreliability.

When retail service is already under pressure, outage and identity-control failures compound a known weakness.

Why A Private Network Can Be Rational

The public routing evidence is compact. AS51748, named SOGAZ-AS in routing sources, is registered to JSC Insurance Company of Gaz Industry Sogaz. IPinfo reports it as a business ASN in Russia, allocated in 2010, with 512 IPv4 addresses, no IPv6 addresses and two visible /24 ranges: 193.178.131.0/24 and 185.173.80.0/24. AS44102, named sogaz-e-os in Cloudflare and CIDR-style reports, is also associated with Insurance Company of Gaz Industry Sogaz, Joint-Stock Company. IPinfo reports that ASN as allocated in 2016, again with 512 IPv4 addresses, no IPv6 addresses and two more /24 ranges: 185.173.81.0/24 and 185.173.83.0/24.

That is not a carrier network. It is not a mass broadband access base, a hosting platform or a transit business. Four /24 IPv4 blocks and two business ASNs are small by telecom standards. The evidence points toward a controlled enterprise perimeter. The 193.178.131.0/24 range shows reverse-DNS traces such as mail.sogaz.ru and mail2.sogaz.ru. IPinfo marks 193.178.131.1 as a Sogaz-address-space host with mailserver, router and webserver signals. CIDR Report shows AS51748 with upstream adjacency to AS44102 and Rostelecom, while AS44102 appears with Storm Networks upstream and AS51748 downstream.

IPinfo's AS51748 view adds Rostelecom, MegaFon, Storm Networks and AS44102 among peers or upstreams. The exact relationship labels vary by observer, but the broad picture is consistent: Sogaz controls a small public routing perimeter and depends on domestic Russian network providers.

The business case for that perimeter is not revenue. Sogaz is not collecting broadband fees from households. The business case is control. Own address space can improve continuity planning, mail routing, VPN endpoint control, segmentation of external-facing systems, independence from a single hosting provider, and flexibility when vendors or counterparties are disrupted. A Bank of Russia-regulated insurer handling medical, motor, industrial and sanctions-sensitive data can plausibly value that control more than a smaller insurer would.

But control is not free. A private network means engineering labor, monitoring, security tooling, equipment refresh, abuse handling, vendor contracts, configuration risk, incident response and governance. It may also mean lower economies of scale than a bank-grade data-center provider or telecom operator can achieve. If Sogaz merely duplicates commodity hosting badly, the network is a tax on policyholders and shareholders. If it keeps critical communications and claims workflows alive during carrier, vendor or sanctions disruptions, it is closer to a form of operational reinsurance.

The right analogy is not a telecom side business. It is a deductible. Sogaz spends a certain amount of capital and operating cost to lower the probability or severity of a digital-loss event. That loss event could be a claims outage, a medical authorization jam, a data breach, a failed mail flow, a regulator-facing reporting interruption, a blocked overseas vendor path or a corporate-client continuity failure. The return is not visible in revenue. It appears as avoided cost, fewer emergency manual processes, lower reputational damage and better bargaining power with suppliers.

The Capital Cycle Inside The Insurer

Insurance is a balance-sheet business before it is a technology business. The rating evidence shows why Sogaz can afford infrastructure but also why the spending must be disciplined. Expert RA confirmed Sogaz at ruAAA in February 2026, citing large size, market position, asset quality, balance-sheet comfort and management quality. In March 2026 it raised the company's international-scale financial reliability rating to A- with stable outlook.

That release cited high-quality investment assets, a capital-to-obligation ratio of 1.95 at September 30, 2025 and a reinsurance book where 96.0% of ceded premium over the measured period went to counterparties at a conditional BBB- class or higher. ACRA's November 2025 international-scale release cited capital above 200% of the national requirement and current liquidity above 135% as of June 30, 2025. NCR's May 2026 action said Sogaz retained leadership, profitability and capitalization in 2025.

Those figures do two things. They show capacity. They also raise the bar. A company with high ratings and strong capital cannot excuse sloppy infrastructure as a survival compromise. It has the resources to buy competent connectivity, security operations and vendor redundancy. If internal control is chosen, it should be because it is superior for this risk profile, not because the organization has inherited a technical estate and learned to live with it.

The spending question should be expressed in insurance terms. First, what is the expected loss from a digital outage or data compromise? Second, how much of that expected loss is reduced by owning and routing Sogaz-controlled address space rather than buying managed service? Third, how does the residual risk compare with the cost of people, tools and suppliers needed to run the environment? Fourth, what concentration risk is introduced by the chosen upstreams and security vendors? Fifth, how often does the infrastructure support high-value corporate-client or medical workflows rather than low-value static web traffic?

Sogaz's capital cycle is more sensitive to claims and investment performance than to a few /24s. But that is precisely why infrastructure can become invisible. A small network budget can hide inside a large insurer. It can grow without the same scrutiny as reserves, reinsurance, loss ratios or investment assets. The danger is not that Sogaz owns a modest network. The danger is that no one prices it like an insurance risk. An internal routing perimeter should have a loss-prevention thesis, a target service level, a failure history, a supplier-concentration map and a decommissioning test for services that no longer require ownership.

My judgment is that Sogaz's current public footprint is small enough to be defensible. It is not obviously excessive. The signals look like an enterprise continuity perimeter rather than infrastructure empire-building. But the justification depends on governance that the public record cannot fully show. If the ASNs support mail, secure access, corporate-client portals, claims data exchange, medical authorization and sanctions-resilient communications, the cost is likely modest against the claim book.

If they mostly support legacy services that could be moved to stronger managed platforms without losing control, then the case weakens quickly.

Pricing Power And The Claims Machine

Sogaz's revenue logic is not complicated in the abstract: price risk, collect premium, invest float, pay claims, retain underwriting margin and use scale to reduce expense ratio. In practice, each line has a different economic texture. Industrial property and hazardous-facility liability reward engineering knowledge, client familiarity and reinsurance access. Voluntary medical insurance rewards provider-network discipline, authorization speed and employer relationships. OSAGO is more regulated, price-constrained and customer-service exposed. Corporate group products benefit from bundling and employee access.

Life and savings-linked insurance, through group structure, depend on distribution partners and investment returns.

The network-control question enters through the expense and claims machine. Digital reliability does not let Sogaz charge a visible "private ASN premium." Customers buy insurance, not routing. But service continuity can protect pricing power indirectly. Large corporate clients do not want their insurer's portals, claim-reporting channels, medical approvals or risk documentation flows to fail during a loss event. Retail customers are more price-sensitive, but digital failure creates complaints and regulator attention.

A network boundary that reduces downtime, supports secure remote access for branches and stabilizes mail can lower friction across both customer sets.

There is a plausible unit-economics paragraph here, even without internal cost data. Four /24 ranges and two ASNs imply a narrow public routing perimeter. The annual cost of maintaining such a perimeter should be low relative to more than 260 billion roubles of 2024 non-life premium. The expensive items are not the numbers themselves; they are engineers, security monitoring, hardware, contracts, audits and incident response. If that spend prevents even a small number of material claim delays, data incidents or corporate-client service failures, it can pay for itself. If it merely reproduces commodity hosting, it cannot.

Sogaz's digital surface is wider than a static corporate website. The official home page points to a user account, policy activation, offices, mobile application and insurance calculators. The OSAGO page presents online purchase and renewal. The health pages involve voluntary medical insurance, telemedicine and special groups. Each of these depends on identity, availability and secure data flows. Network control is not the only way to support those flows, but it is one layer in the stack.

The key limitation is that network control does not fix bad processes. Review-platform complaints about slow payment, unclear callback loops or medical authorization denial are process, governance and product-design issues. A private ASN can keep the door open; it cannot make the claims department walk through it. If Sogaz uses infrastructure control as an excuse to focus on hardware while customers suffer from workflow failures, it is solving the wrong problem. The strongest case for the network is as part of an operating system that also measures claim cycle time, complaint ratios, call-center follow-through and provider response.

Suppliers And The Cost Of Being Domestic

The routing evidence shows dependency, not independence. AS51748 and AS44102 may belong to Sogaz's control surface, but they still rely on upstream and adjacent networks. Public datasets name Rostelecom, MegaFon, Storm Networks and legacy Comstar/MTS-related records around the relevant ASNs. The AS51748 RIPE-style record visible through IPGeolocation includes imports from AS8359 and AS12389, and the AS44102 report lists multiple Russian ASNs in its import lines. The effect is a domestic supplier map.

That map is rational under sanctions pressure. Sogaz appears on U.S. OFAC records, Canadian Russia regulations, UK Companies House sanction-disqualification records, OpenSanctions aggregations and Ukrainian sanctions mapping. The legal effects differ by jurisdiction, but the direction is unmistakable: Sogaz faces substantial external counterparty friction. A sanctioned Russian insurer cannot assume normal access to Western cloud, reinsurance, software, payment or professional-service relationships. Even where a service is legally possible, banks, vendors and compliance departments may choose not to touch the risk.

Domestic control therefore becomes more valuable. If cross-border service options narrow, the ability to run critical edge infrastructure with Russian carriers and Russian security teams is not simply preference. It is continuity planning. The trade-off is concentration. Domestic upstreams may share legal, geopolitical, power, software and equipment risks. Sanctions that push Sogaz away from global providers also reduce diversification. The company may control its ASNs, but it does not control the Russian internet, the equipment supply chain, security-software evolution, or the reliability of upstream carriers.

Reinsurance is the parallel case. Expert RA's international-scale release emphasizes high reinsurance-protection quality, including a high share of ceded premium going to stronger counterparties by its rating classification. That is good for Sogaz's risk transfer. But sanctions and geopolitical isolation can narrow reinsurance choice, change collateral demands and make settlement paths more difficult. The same logic applies to IT vendors. The insurer can lower dependency on one class of supplier by increasing dependency on another. Good governance means mapping the dependency shift, not congratulating itself for "control."

The sourcing question should be dynamic. In a calmer market, Sogaz might minimize internal network ownership and rely more heavily on scaled external providers. In a sanctions-constrained market, it may accept higher internal operating cost to reduce counterparty fragility. That does not mean every internal service is strategic. It means the hurdle rate changes. A commodity website still belongs on resilient commodity infrastructure. A claims, medical or corporate-risk communications channel might justify stronger internal control.

Customer Concentration And Trust

The public record around Sogaz's customer base has always had a Gazprom shadow. The company name itself points to the gas industry. Gazprom's investor page shows that the Russian state and state-controlled entities held 50.23% of Gazprom as of the end of 2024. S&P's 2014 rating note, historical but still instructive, said Gazprom and subsidiaries owned 24% of Sogaz and that Gazprom had effective control through board representation and largest-client status. Vedomosti reported in 2013 that Gazprom group risks accounted for 29% of Sogaz's 2012 premium, down from 32%.

A Sogaz-hosted historical article described major customers including Gazprom, RZD, Rosatom, Rosneft and others. A 2026 court record involving Gazprom gas-transmission property insurance with Sogaz confirms that the Gazprom relationship did not vanish into history.

Those figures should not be mistaken for current shareholder or premium concentration. The current ownership detail is less transparent in the easily accessible public record, and a 2012 premium mix is not a 2026 metric. But the pattern matters. Sogaz's franchise is built on trust from large strategic customers, not only on open retail competition. That trust has operational consequences. An insurer serving industrial systems is expected to understand continuity, confidentiality and administrative reliability.

Its internal network may be part of the comfort package for those clients, especially when claims documentation and risk engineering move through sensitive channels.

Customer concentration can support infrastructure investment because a few large relationships can justify tailored reliability. It can also dull competitive pressure. If Sogaz retains clients because of institutional ties, group procurement or sector habit, it may face less immediate penalty for inefficient technology. Retail complaints are visible, but corporate-client dissatisfaction is usually private. The company therefore needs internal discipline to avoid mistaking captive trust for operational excellence.

Switching costs differ by line. A household motor-policy buyer can compare price and service on platforms. A large gas, nuclear or transport customer changes insurer only after considering reinsurance, risk engineering, claims history, political comfort and procurement rules. Voluntary medical contracts for employees have their own provider-network and authorization complexity. That is why Sogaz can have a large retail complaint signal and still maintain a powerful corporate franchise. The infrastructure case rests more on the latter than the former.

The test is whether network control improves the customer experience that customers actually value. For a corporate industrial client, that may mean secure document exchange, reliable claims coordination and continuity during a physical incident. For an OSAGO customer, it means a policy can be bought, changed and claimed without digital dead ends. For a DMS customer, it means the medical authorization path is quick enough that the insurer is not experienced as a denial machine. If Sogaz's infrastructure cannot be tied to those outcomes, it is invisible capital consumption.

Regulation, Sanctions And The Narrowing Of Alternatives

Sogaz's regulator is the Bank of Russia. That means licensing, solvency, reporting, consumer-rights handling, financial-ombudsman procedures and scrutiny of market conduct. The Bank of Russia's 2024 market review gives the macro picture: insurance premiums reached 3.7 trillion roubles, payouts reached 2.1 trillion roubles, contracts numbered 299 million and sector capital was 1.2 trillion roubles. In that market, Sogaz is large enough to be part of the system's operating fabric. Its failure to process claims or maintain compliance flows would not be a purely private inconvenience.

Sanctions create the second regulatory environment. OFAC lists Gas Industry Insurance Company Sogaz with the LEI, Russian registration number and tax ID also seen in company and LEI records. Canada lists Gas Industry Insurance Company Sogaz in its Russia sanctions regulations. UK public records show a director-disqualification sanctions entry tied to Sogaz. OpenSanctions aggregates further listings across jurisdictions, and the Ukrainian sanctions portal maps a wide sanctions footprint. The reasons and legal consequences differ, but the practical message is clear: Sogaz is a restricted counterparty for many international purposes.

That changes the infrastructure math. A non-sanctioned insurer can buy more external redundancy from global providers, access more reinsurance markets, use international software support more freely and settle across borders with less friction. Sogaz has to assume more breaks in those channels. That makes domestic operational control more appealing. It also makes external validation harder. A high-quality global vendor ecosystem is a form of discipline; when it recedes, internal teams must replace not just technology but also process maturity.

There is a geopolitical irony here. Sanctions may increase Sogaz's need for internal resilience while also increasing the risk that its internal resilience is less diversified. Russian domestic providers can keep the company operating inside Russia, but their own dependence on constrained technology supply, domestic regulation and geopolitical events becomes Sogaz's indirect risk. Owning an ASN does not magic away the supply chain.

For policyholders, the question is narrower: will the insurer pay and communicate when needed? For corporate clients, the question is whether the insurer can support complex risk transfer despite sanctions. For regulators, the question is whether Sogaz remains solvent, fair and operationally stable. For outside counterparties, the question is often whether they can transact at all. Network control helps only with the middle part: the company's ability to keep its own channels working. It cannot remove legal restrictions.

The Unofficial Signals

Unofficial signals are useful when they are kept in their lane. Review sites do not establish loss ratios or breach incidents. Recruiting posts do not prove a security architecture. Routing pages do not reveal all production systems. But together they show where pressure is felt.

Banki.ru OSAGO reviews point to frustration with claim handling, communication and digital interaction. Otzovik's electronic OSAGO page carries complaints about purchase friction and settlement dissatisfaction. Medadvisor's DMS reviews complain about authorization and application usability. TBank's review page is much more positive overall, with many comments praising speed and branch staff, but it still includes online-policy issues. The mixed picture is believable.

A company with more than 1,000 sales units and a large Russian footprint can deliver good branch experiences in some places and poor digital or claims experiences in others.

The recruiting traces point in the opposite direction: Sogaz and Sogaz-Med appear to be hiring for system administration, active network-equipment support, 1C administration, SIEM, incident-response orchestration, DLP, firewalls, vulnerability scanners and personal-data protection methodology. Some of these listings are from aggregators or public channels, not formal company disclosure. Still, they fit the operating needs of a regulated insurer with medical data, branches, online policies and a visible network edge.

The signal is not that Sogaz has a uniquely sophisticated cyber program. The signal is that the company is spending on the categories one would expect if the network control surface is real: endpoint and branch support, security monitoring, data-loss prevention, compliance documents, regulator correspondence and technical controls. That supports the view that the ASNs are not orphaned curiosities. They sit inside a broader enterprise-technology footprint.

But the customer signals also warn against over-crediting technology spend. If customers cannot get a callback, cannot receive a guarantee letter, cannot edit a policy or cannot understand claim status, the insurer's private network has not delivered the service outcome. In insurance, operational excellence is not measured at the router. It is measured at the claim desk, the hospital reception, the repair shop and the regulator's complaint statistics.

Alternatives

Sogaz has several alternatives to internal network control. It could outsource more services to domestic telecoms or managed hosting providers. It could place non-sensitive public web functions on larger distributed platforms inside Russia. It could use bank or partner infrastructure for some retail distribution. It could separate high-sensitivity corporate and medical systems from low-sensitivity marketing and calculator surfaces. It could keep its own address space for mail, secure access and critical claims workflows while moving commodity traffic elsewhere.

The best answer is almost certainly hybrid. The public footprint is already small enough that the company does not appear to be trying to become a telecom operator. The task is to decide which systems truly require Sogaz-controlled routing and which merely inherited it. Critical mail, regulator communication, secure remote access, certain corporate-client channels and claims continuity may justify internal control. Public marketing pages, low-risk calculators and generic content may not.

The comparison is not internal versus external in the abstract. It is internal with domestic upstream concentration versus external with vendor concentration and sanctions risk. Outsourcing to a Russian managed provider may improve scale and resilience but reduce direct control. Keeping everything inside may improve authority but increase internal error risk. A mature insurer would classify workloads by legal sensitivity, downtime tolerance, customer impact, supplier restrictions and reversibility.

The absence of IPv6 in the public IPinfo summaries is a small warning flag. It may not matter for all Russian customer use today, but it suggests that the public footprint is conservative and possibly legacy-weighted. A disciplined internal network strategy should not only preserve old services. It should modernize where modernization lowers risk. Lack of visible IPv6 is not a fatal weakness; it is a question for technical governance.

What Would Change The Judgment

The bullish case is that Sogaz's infrastructure is a modest, necessary control layer for a very large insurer operating under sanctions, serving industrial clients and handling sensitive medical and claims data. In that case the costs are likely small against the avoided-loss potential. The company does not need to prove carrier economics because it is not selling carrier service.

The bearish case is that the visible network is a legacy perimeter whose costs are hidden in a large organization, while actual customer pain sits in claims workflows, medical approvals and retail communication. In that case the network may be technically valid but economically overrated. It could even distract management from higher-return operational fixes.

Several facts would change my view. If Sogaz disclosed that the ASNs support core claims, medical authorization, corporate-risk documentation and regulator reporting with measured uptime and incident data, the case for internal control would strengthen. If independent routing history showed stable, redundant announcements with low outage incidence, the case would strengthen. If customer complaints fell materially after digital-service improvements tied to infrastructure modernization, the case would strengthen.

The case would weaken if most customer-facing systems are already outsourced and the ASNs mainly host old mail and administrative remnants. It would weaken if network concentration around a small number of domestic upstreams created repeated outages. It would weaken if security incidents, mail disruption or claim delays traced to internal configuration failures. It would also weaken if Sogaz's corporate clients did not value direct infrastructure control and would accept managed-provider service with clearer service-level guarantees.

The central judgment remains narrow. Sogaz does not need infrastructure because it is an insurer with a website. It needs some infrastructure control because it is a large Russian insurer whose product is continuity, whose customers include strategic corporate groups, whose retail services are complaint-sensitive, and whose sanctions environment narrows external alternatives. That is enough to justify a controlled edge. It is not enough to justify complacency.

Evidence Register

The core identity facts come from the Bank of Russia financial-organization register, Sogaz's official information page, Prime disclosure, Interfax disclosure and the LEI record. They align on the same legal name, registration numbers, tax identifier, Moscow address and insurer registration.

The business-model facts come from Sogaz's own corporate, product and sector pages, then are checked against Bank of Russia market material, Interfax reporting on hazardous-facility liability, Expert RA ranking material, ACRA rating releases, NCR rating releases and Expert RA rating releases.

The capital and solvency discussion relies on the current rating-agency record: Expert RA's ruAAA and A- releases, ACRA's AAA(RU) and A- releases, NCR's AAA.ru profile and release, plus Bank of Russia market statistics. Historical AM Best and S&P records are used only to explain continuity in Sogaz's corporate-property and Gazprom-linked profile, not to state current ownership.

The infrastructure findings come from IPinfo, IPGeolocation, Cloudflare Radar, CIDR Report and Hurricane Electric BGP pages for AS51748, AS44102 and 193.178.131.0/24. These show the network resources, routing names, address ranges, adjacent networks and mail-host traces. They are evidence about Sogaz's operating surface, not independent businesses.

The customer-concentration discussion uses Sogaz historical company material, Vedomosti's management quote about 2012 Gazprom group premium share, S&P's 2014 rating commentary, Gazprom's current shareholder-structure page and a 2026 legal database item describing a Gazprom property insurance contract with Sogaz.

The sanctions discussion uses OFAC, the Government of Canada, UK Companies House, OpenSanctions and the Ukrainian sanctions portal. These sources map legal and practical constraints around Sogaz's international counterparties.

The unofficial market-signal discussion uses Banki.ru, TBank, Otzovik and Medadvisor customer-review pages and several recruitment postings for system administration, security monitoring, data-loss prevention and personal-data protection. Those sources are interpreted as signals of operating pressure and spend, not as audited performance facts.

Sources