Summary

  • The narrow verified boundary is a young Saint Petersburg company, registered in April 2026 with a 100,000-ruble charter capital, a data-processing and hosting main activity, a RIPE LIR organisation object, ASN AS219516, and a RIPE-registered IPv6 /48 tied to that ASN.
  • The strongest operating signal is not customer traffic; it is preparation for network operation. RIPE records show upstream intent through AS206980 and AS203656 and a route6 object for 2a02:fd40::/48, while RIPEstat showed no globally visible originated prefixes, no announced address space and no observed neighbours at the late-July 2026 snapshot.
  • The economic case therefore remains unproven. IZI could become a revenue-producing operator if it wins niche business access, hosting, protected connectivity or managed continuity work, but the public record does not yet show paying customers, service tariffs, staff depth, telecom licensing, procurement wins, IPv4 capacity, data-centre footprint or a route history that would confirm recurring customer economics.

The operating boundary is real but very narrow

The first discipline with IZI is to keep the verified boundary small. The company is not yet publicly evidenced as a scaled broadband provider, data-centre operator or managed-services platform. The record supports a more modest starting point: Limited Liability Company "IZI" is a Russian legal entity whose public company profiles place it in Saint Petersburg, with OGRN 1267800030915, INN 7840125745 and registration on 23 April 2026. Its registered address in those profiles matches the address that later appears in the RIPE organisation object: ul. Krasnogo Tekstil'shchika, d. 10-12, lit. U, Saint Petersburg, 191124.

That match matters. A shell can be registered without operational consequence, and a network object can be created without traffic. When legal and resource records align on name, country, registration number and address, however, the record supports at least one proposition: the company has moved beyond generic incorporation into a recognisable network-resource posture. RIPE lists the organisation object ORG-LLC73-RIPE for Limited Liability Company "IZI", gives it Russian country code status, records the same OGRN as its registration number, and classifies the organisation type as LIR.

The company also has role, maintainer and abuse-contact objects under the same address and phone details. Those are administrative controls, not revenue, but they are the controls a would-be network operator needs before it can make a credible technical offer.

The timeline is compressed. The company was registered on 23 April 2026. RIPE created the organisation, role and maintainer records on 4 June 2026. AS219516 was created on 8 June 2026. The IPv6 inet6num for 2a02:fd40::/48 and its route6 object were created minutes after the ASN record. The public sequence looks like incorporation first, registry membership or sponsorship shortly after, and then immediate construction of the minimum network identity: organisation, maintainer, contact, ASN, IPv6 assignment and route object. For an operating company, this is preparatory work.

For an investor or counterparty, it is not enough to call the business active in a commercial sense.

The company registry profile also keeps the operating boundary modest. IZI's main OKVED activity is data processing, hosting and related activity. Additional activities surfaced in public profiles include web portals, software, computer and IT services, wired communications, database and information resources, information security and related advisory work. That mix is broad enough to support a hosting, connectivity or managed infrastructure thesis, but it is too broad to prove the thesis by itself.

Russian companies often register multiple adjacent activities early, and the public record does not show which of those activities has produced revenue.

The charter capital also cautions against over-reading the network signal. Public company profiles list 100,000 rubles. That is not the company's full funding capacity; owners can lend money, suppliers can provide credit, and customers can prepay. But as a public anchor, it is small relative to the capital needed for material access-network build-out, data-centre space, professional routing equipment, customer support and regulatory compliance. The right conclusion is not that IZI cannot operate.

It is that a serious economic claim must be proven by other evidence: announced routes, service contracts, invoices, licences, visible customers, staff or durable supplier arrangements.

A registered ASN is an option, not a business

AS219516 is the strongest single network fact. The RIPE aut-num record names the AS as IZI-AS, assigns it to ORG-LLC73-RIPE and records imports from AS206980 and AS203656 with corresponding exports to announce AS219516. In plain business terms, IZI has documented an intention to receive upstream reachability from two networks and to announce its ASN back to them. That is a meaningful operating step because an ASN gives a company routing independence that a normal reseller does not need. It can support multi-homing, provider switching, traffic engineering and a more credible promise of continuity to business customers.

But the same record also shows the limit. RIPEstat's late-July 2026 overview for AS219516 reported the ASN as not announced. The announced-prefixes endpoint returned no prefixes over its query window. The routing-status endpoint showed zero IPv4 prefixes, zero IPv6 prefixes, zero announced IPv4 addresses, zero announced IPv6 /48s, no first seen or last seen BGP event and no observed neighbours. The as-routing-consistency view found one RIPE route object, 2a02:fd40::/48, and the two import/export peers in the registry, but marked the prefix and both peer relationships as present in whois rather than in BGP.

The prefix-level RIPEstat checks likewise showed 2a02:fd40::/48 as not announced, with no origins and no related prefixes visible.

This distinction is the core of the thesis. Registry control is a capacity to operate; global routing visibility is evidence that the capacity is being used. IZI has the former and, in the observed snapshot, lacked the latter. That does not mean no private testing occurred, no customer talks existed or no low-visibility routing happened outside RIPE RIS thresholds. It means the public internet record did not yet show a production network with originated space visible to a broad set of collectors.

For a company whose assignment asks whether public records support recurring customer economics, that absence weighs heavily. Recurring connectivity revenue depends on service continuity. A customer buying business internet, hosting, DDoS-protected transit, VPN underlay or managed edge service normally needs an operator that can keep routes live, handle incidents, maintain upstream alternatives and publish credible support processes. An inactive ASN can be an asset in waiting. It cannot be counted as a live customer base.

The IPv6 record narrows the possible starting product. The visible address resource is a /48 named IZI-NET. A /48 can support internal infrastructure, a small number of customer assignments, lab use or a very small hosted-service estate. It is not a broad access-network allocation in the same commercial sense as a large IPv6 allocation with many downstream assignments. RIPE policy allows members to request IPv6 resources, and the existence of a /48 route object confirms a concrete address plan. It does not, by itself, show end-user sites, servers, subscribers or traffic.

The absence of visible IPv4 is also commercially relevant. Russian small and medium customers still need practical IPv4 reachability for many services, even when IPv6 is strategically important. A new operator can buy transit, lease addresses, use upstream-provided IPv4, rely on NAT, or focus on IPv6-capable hosting and internal business services. Each option changes unit economics. Leased or upstream-provided IPv4 weakens independence and can compress margin. NAT can work for residential access but may be unsuitable for business services that need public addressing. A pure IPv6 proposition is technically elegant but commercially narrower.

Without evidence of IPv4 assets or upstream commercial terms, IZI's near-term product set looks constrained.

The upstream names point to supplier dependence

The two upstream ASNs in IZI's aut-num record deserve attention because supplier choice is often where a small network's economics are set. AS206980 is tied in RIPE records to AntiDDoS Solutions LLC, a United States-registered LIR whose aut-num record contains detailed routing-community remarks, including prepend handling, blackhole tagging and DDoS protection actions. AS203656 is tied to Easy Tech Gaming FZ LLC, an Abu Dhabi LIR whose own aut-num record lists several upstream imports and exports. These records do not prove that IZI has bought transit from those networks, and they do not show traffic.

They do show the intended route-control counterparties recorded for AS219516.

Supplier dependence cuts both ways. For a new company, buying upstream connectivity from specialised networks can be a rational shortcut. It reduces the need for immediate backbone build-out, enables a managed protection story and lets the company sell resilience or hosting features before it owns much physical infrastructure. If customers are small businesses that care about uptime more than raw geography, a well-managed upstream relationship can support a viable service.

The risk is that the supplier stack may become the business. If IZI's only observable network inputs are registry objects and third-party upstreams, then the customer value must come from something else: local sales, installation, support, compliance handling, Russian-language service continuity, integrated hosting, or a specific protected-connectivity package. Otherwise the company is exposed to a simple question: why would a customer not buy directly from a larger incumbent, a cloud provider, a data-centre operator, or a known anti-DDoS/transit supplier?

The supplier geography also matters in 2026. A Russian company depending on foreign or foreign-registered upstream counterparties faces payment, sanctions, routing-policy and reputational uncertainty even where the service is lawful. The public record does not show that IZI's counterparties are unavailable or unreliable. It simply means the path from Saint Petersburg registration to dependable customer service runs through suppliers outside the local company. That makes contracts, service-level terms and failover evidence more important than they would be for an established domestic network with many visible peers.

The company profile supports infrastructure services more than mass access

IZI's registered activities suggest a company framed around digital infrastructure rather than a classic cable roll-out. The main activity is data processing, hosting and related services. Additional activities include software, IT consultancy, computer-equipment management, databases, web portals, information services, security and wired communications. The wired-communications code keeps a connectivity option open, but the heavier cluster sits around hosting and managed information infrastructure.

That distinction is economically important. A mass-market residential ISP competes on coverage, installation capacity, price, bundled television and customer service at volume. It needs field crews, access to buildings, last-mile infrastructure, municipal and landlord permissions, working capital for customer equipment, and enough subscribers per area to amortise network costs. Nothing in IZI's public record demonstrates that kind of footprint.

A small infrastructure-services provider can start differently. It can rent rack space, buy transit, control an ASN, host servers, provide managed backup or small private cloud, sell protected access to a handful of business customers, and differentiate on response speed. The public company record and RIPE posture are more compatible with that path. A /48, an ASN, LIR status and upstream routing relationships can underpin a small hosting or managed-connectivity offer long before they support a regional last-mile network.

Even that more modest path requires proof that is not yet public. Recurring infrastructure revenue needs customers with monthly invoices, repeat support obligations and a reason to stay. The observable record does not identify clients, tariff pages, a web ordering surface, data-centre locations, IP transit contracts, service staff or support hours. Nor does it show public procurement wins or litigation from commercial disputes. The absence of disputes is not a weakness for a young company; the absence of commercial artefacts is the point.

IZI may be operating privately or preparing launch, but the public footprint does not yet support a conclusion that recurring economics exist.

This is why the title question is not whether IZI is legitimate. The legal and RIPE records are legitimate enough to take the company seriously as a potential operator. The question is whether those records belong to a revenue-producing operating company. At this stage, they show the operating permissions and routing identity a revenue-producing company might need, not the revenue-producing company itself.

Pricing exposes the scale problem

Russian telecom pricing makes the threshold problem sharper. The large incumbent benchmark from Rostelecom shows residential fibre internet ARPU in the hundreds of rubles per month and business/government fibre and VPN-related ARPU in the low thousands of rubles per month. Those figures are not IZI's prices, and they should not be used as IZI estimates. They are useful because they show the economic difference between consumer access and business continuity.

If a new operator tries to win residential broadband customers, very small subscriber numbers cannot cover much fixed cost. A few hundred household customers at low monthly ARPU can demonstrate local demand, but they do not easily pay for routing expertise, customer support, installation labour, upstream capacity, data-centre presence, billing systems and compliance overhead. Scale matters, and scale is hard to infer from a young company with no public routes and no visible customer base.

Business services can change the arithmetic. A small number of SMEs buying managed connectivity, hosting, backup, protected IP access or VPN continuity can produce higher monthly revenue per account than residential broadband. The sales cycle is harder, but the network footprint can be narrower. A Saint Petersburg company with local support and a credible routing setup might serve small enterprises that need a Russian counterparty and practical incident response more than they need a national brand.

The difficulty is customer concentration. In the early stage, a few business accounts can make a company look alive while leaving it fragile. One lost anchor customer can remove a large share of revenue. One supplier price increase can erase margin. One regulatory issue can delay service activation. Public records do not show whether IZI has any such customers, let alone whether revenue is diversified. That is why a recurring-economics judgement cannot rely on incorporation and an ASN alone.

The article's conservative reading is therefore not pessimistic; it is simply disciplined. IZI's likely attractive route is not mass access at low ARPU. It is a narrower continuity product where the company can charge for reliability, local responsiveness and infrastructure management. But the record must begin to show those things. A published tariff, live route visibility, named facilities, customer references, procurement records, or repeat monthly service evidence would materially improve the case. Without them, pricing remains a scenario rather than a fact.

Cost and capital are front-loaded even for a light operator

RIPE fees are visible enough to frame the minimum administrative cost. The 2026 charging scheme lists an annual service fee per LIR account, a sign-up fee for new members or additional LIR accounts, and smaller charges connected to certain resource assignments. These amounts are modest compared with network build-out, but they are not zero. They are also only the top layer of cost.

The deeper cost stack is physical and operational. A company that originates routes needs routers or virtual routing infrastructure, data-centre space or a hosted edge, upstream capacity, monitoring, abuse handling, customer support and someone who can maintain routing policy under stress. If the product includes hosting, it also needs servers, storage, backup, power and cooling exposure, software licensing or open-source maintenance, security controls and on-call processes.

If the product includes last-mile access, it needs an entirely different cost base: field work, customer premises equipment, local rights of way, building access and service installation.

Russian infrastructure context raises the bar. Market reports through 2025 and 2026 describe strong growth in cloud and infrastructure demand, pressure on data-centre capacity, higher equipment costs, power constraints and uneven regional supply. Those trends can help an infrastructure-services entrant because customers may prefer renting capacity and support rather than buying scarce equipment themselves. They can also hurt the entrant because the same scarcity raises input prices and gives established providers a procurement advantage.

For IZI, the public record does not reveal whether it owns equipment, leases racks, uses a third-party platform or remains pre-launch. The 100,000-ruble charter capital cannot answer that question. Charter capital is not a full balance sheet, but it is a signal that the public incorporation record alone does not show a capital-heavy build. If IZI is capital-light, it likely depends on suppliers for most infrastructure. If it is capital-heavy, the evidence has not yet surfaced.

This is where recurring economics become a proof problem. Monthly revenue is valuable only if gross margin survives supplier costs and operating labour. A small operator can look profitable on paper if founder labour is unpaid, support is informal, and upstream or hosting costs are prepaid by customers. That may be acceptable in a launch phase. It is not a durable business until the company can pay market rates for support, maintain redundancy and still retain customers at sustainable prices.

Regulation is not decorative for internet access

Russia's telecom rules make the difference between hosting, managed IT and communications service commercially important. Federal communications law and Roskomnadzor's licensing framework require licensing for relevant communications services and impose obligations on operators providing internet access, including traffic-handling and network-security requirements. The public sources used here did not reveal an IZI communications licence. Synapse explicitly showed no active or suspended licences in its company profile at the time surfaced, while the official regulatory material explains why the licensing question matters.

This does not mean IZI is violating anything. A company can be preparing service, operating only unlicensed IT activities, reselling under another operator's licence where lawful, or offering hosting and consulting rather than acting as a communications operator to end users. The point is narrower: if the economic thesis depends on IZI becoming a regional ISP or direct internet-access provider, licensing and compliance evidence become central. If the thesis depends on hosting or managed infrastructure, the licence burden may be different, but data protection, security and customer-contract obligations remain relevant.

Personal-data localisation rules also matter for hosting and cloud-like services in Russia. If IZI stores, processes or supports systems containing Russian citizens' personal data, the location and handling of those databases can affect customer trust and legal design. A small provider can turn compliance into a selling point for SMEs that lack internal expertise. It can also be overwhelmed by documentation, audits, incident response and customer due diligence if the company lacks staff.

The regulatory burden therefore cuts against a simplistic shell story and against a simplistic operating story. A shell may hold a company registration and even network resources without facing the full cost of live service. A real operator must absorb compliance work that does not scale down cleanly. The public evidence so far shows readiness to hold resources, not readiness to carry a regulated customer base.

Competition leaves little room for an undifferentiated offer

Russia's communications and infrastructure markets are not empty spaces waiting for a new small operator. National operators, regional ISPs, cloud providers, hosting companies and data-centre groups already compete for customers. TMT Consulting's 2025 telecom market summary describes a large market with growth in fixed broadband, leased channels and data-services consumption. Rostelecom's disclosures show the scale and capital intensity of the incumbent base. Other public market sources point to continued cloud growth, data-centre capacity constraints and high infrastructure investment needs.

For a new entrant, this context creates both opportunity and pressure. The opportunity is that demand for data, cloud, secure hosting, backup and continuity is rising. Equipment is expensive, and many smaller companies may prefer service contracts to owning infrastructure. If IZI can serve a narrow segment with local responsiveness, it may not need national scale.

The pressure is that the obvious generic services are already available from larger firms. A simple "internet access" or "hosting" offer has weak differentiation unless the company has a local access advantage, a cheaper supplier base, stronger support, a specialised security package or a customer niche that larger providers neglect. The public record does not identify such a niche. The OKVED mix permits one, but permission is not positioning.

Competition also affects supplier bargaining. A small operator with no visible traffic has limited leverage with upstream providers and data-centre landlords. If capacity is scarce, larger customers get better terms. If routing depends on two named upstreams and neither is visibly carrying IZI traffic, then the company has not yet demonstrated route diversity in practice. A prospective customer would reasonably ask for service-level terms, outage processes and proof of live failover before placing critical connectivity with IZI.

The most plausible early wedge is SME service continuity rather than broad ISP substitution. SMEs often need someone to solve practical problems: keep a site reachable, host a line-of-business server, provide remote access, manage DNS and certificates, arrange backup connectivity, and answer the phone when a service fails. A young company can compete there if the founders have technical credibility and local relationships. Public records do not show those relationships, so the thesis stays conditional.

Market signals should be treated as signals, not telemetry

The public market signals are mixed. On the positive side, IZI's creation sequence is coherent: company registration, RIPE organisation, ASN, IPv6 assignment and route object all appeared in a short period. The registered activities fit digital infrastructure. The RIPE contacts and maintainer are not orphaned objects. The upstream references are specific rather than generic. That combination is consistent with a company preparing to operate.

On the negative side, the public internet did not show route origination in the RIPEstat snapshot. Company profiles did not show financial accounts, taxes, court cases, procurement wins, active licences or visible workforce depth. The company is too new for many annual disclosures, so absence should be interpreted carefully. Still, recurring customer economics leave traces. Live routes, tariffs, customer mentions, public support pages, job postings, procurement notices, data-centre presence, payment terms or disputes often appear before a company reaches scale. The current record is thin across those dimensions.

There is also a name-noise problem. "IZI" is a common short brand element across unrelated logistics, travel, commerce and software references. Public searches return many irrelevant entities. That makes exact identifiers important. The useful records are those tied to OGRN 1267800030915, INN 7840125745, ORG-LLC73-RIPE, AS219516, the address in Saint Petersburg and the IPv6 /48. Anything outside those identifiers should not be imported into the economic judgement.

The market-signal reading is therefore: preparation is credible, operation is unproven, and revenue is not visible. That is a harsher standard than a directory listing, but it is the right standard for a company-research article about customer economics. The question is not whether IZI has the right to try. It is whether the public footprint shows that the attempt has become a recurring business.

Customer economics require a service surface

Recurring economics begin when a customer understands what is being bought, why the supplier is accountable and how continuity will be restored when something fails. That service surface is not yet visible for IZI. The company has identifiers, registry controls and potential upstream paths, but the public record gathered here does not show a product catalogue, tariff schedule, support terms, uptime commitment, facility description, customer onboarding process or named service boundary. This absence is not unusual for a company only months old.

It is nevertheless decisive for the economic judgement because the evidence must support revenue, not only readiness.

The distinction is practical. A business-access customer wants to know whether IZI sells an internet circuit, a protected transit path, a hosted server, a managed router, a VPN service, backup connectivity, remote-access support or all of those things together. Each product has different gross margin and different operational stress. A hosted service can be launched with rented infrastructure and a small technical team, but customer trust depends on backup, patching, security and response. A direct access service may create steadier monthly revenue, but it requires physical installation, licence clarity and local network depth.

A protected-connectivity service can charge a premium, but only if the supplier stack and mitigation policy are credible under attack.

The public records do not identify IZI's choice among those paths. That means the revenue model cannot be safely inferred from the OKVED list. A broad set of registered activities is an option set, not a price list. It allows the company to do data processing, hosting, wired communications, software, consulting and information-security work. It does not tell an analyst whether the first customer is a local office needing backup internet, a software team renting virtual infrastructure, an overseas network needing a Russian registration point, or no customer at all.

The service-surface gap also affects labour economics. If IZI sells continuity, the company needs support labour. If it sells hosting, it needs systems labour. If it sells access, it needs field or partner labour. If it sells protected transit, it needs routing and security labour. The registry record names an IZI team role, but that is a contact object, not staffing evidence. A small company can cover early operations with founder labour, but founder labour is not free in a durable business. The cost eventually appears as salary, contractor fees, burnout, slower response or weaker customer retention.

The more favourable interpretation is that IZI is still in the launch interval between resource setup and public commercial offer. Under that reading, the lack of a tariff page or public customers is not fatal; it simply means the article should not move ahead of the facts. The less favourable interpretation is that resource control is the whole activity: the company holds an ASN and IPv6 records but does not yet have a product capable of converting those controls into monthly revenue. Both interpretations fit the available evidence.

The deciding facts will be public product definition, route stability, licence clarity where required and customer artefacts that repeat over time.

Dormancy is a realistic alternative, not an accusation

A serious assessment must keep dormancy on the table without turning it into a charge. Many young companies register broad activities, create technical records, test suppliers and then pause. The pause can happen because customers take longer than expected, supplier terms are unattractive, licensing takes time, founders pivot, or the original idea proves too small. Nothing in the record proves that IZI is dormant. But the absence of visible route origination, licences, customers, accounts and staff signals means dormancy is a plausible alternative to operating revenue.

That alternative changes how the company should be monitored. If IZI is dormant, the most important events are renewal or abandonment signals: RIPE objects staying current, route objects being removed or updated, a new prefix appearing, a website or tariff surface going live, a licence being granted, or the company showing tax, employment, procurement or court records as time passes. If IZI is active privately, the public record should eventually leak some evidence through routing, contracts, support pages, filings or market references. A completely silent footprint over a longer period would make the dormant interpretation stronger.

Dormancy also has an economic cost even when visible operating expenses are low. RIPE membership or sponsorship arrangements, domain and hosting costs, accounting, legal compliance and basic administration continue. More importantly, opportunity cost accumulates. A young operator that waits too long to launch may lose local customer relationships to incumbents, cloud providers or managed-service firms that already have contracts in place. In infrastructure services, trust compounds slowly. Delayed public operation can make customer acquisition more expensive later.

The counterpoint is that careful staging can be rational. A company may create network objects before announcing routes because it is negotiating upstreams, testing configurations, arranging licences, building a product, or waiting for first customers. In that case, not being visible in BGP is a timing fact rather than a weakness. But the burden of proof remains with later evidence. The public record on 30 July 2026 supports a prepared technical identity. It does not yet support a mature operating company.

For IZI, the difference between dormant and early-stage is not philosophical. It is the difference between a balance sheet supported by recurring invoices and a balance sheet supported by owner patience. A company can survive for a while on patience, especially if costs are modest. It cannot justify an operating-company conclusion on patience alone. The article therefore treats dormancy as an unresolved economic scenario, not as misconduct.

Why a narrow niche could still work

The upside case should also be stated clearly. IZI does not need to defeat national operators to become a real company. A small infrastructure provider can earn durable revenue if it owns a narrow customer problem. Saint Petersburg has enough business density for specialist support, and Russian SMEs have continuing needs for connectivity, backup, hosting, data handling and security-aware operations. A provider that can combine local accountability with competent upstream management may win customers who are too small for bespoke attention from incumbents and too practical to manage infrastructure themselves.

The likely wedge is continuity. A customer may not care who announces an ASN in abstract terms, but it cares whether its office link, hosted application or remote-access service works on Monday morning. If IZI can translate AS219516, the IPv6 /48 and supplier relationships into a continuity promise that customers understand, the public-resource base becomes commercially meaningful. The resource base lets the company say it is not merely a web-design shop or casual reseller; it has a network identity and can control parts of routing policy. That can matter to customers who need more than commodity hosting.

The wedge has limits. Continuity promises are costly to keep. They require monitoring, escalation, abuse handling, spare capacity, documented changes and a willingness to answer incidents outside ordinary hours. The company must avoid selling the impression of carrier-grade resilience before its real supplier and labour base can support it. A small operator can be excellent by being honest about scope: a small set of well-supported services, clear escalation boundaries, and pricing that pays for the required human response.

That is why the most bullish reading is still conditional. The same facts that make IZI interesting also define the next proof points. A coherent RIPE identity, a route object and two named upstreams are useful ingredients. They are not the meal. The company must now show stable routing, a product, paying customers and the operational muscle to keep promises. If those arrive, the July 2026 record will look like the setup phase of a focused operator. If they do not, the record will look like a technically literate registration exercise.

What would change the judgement

Several facts would materially improve the case. The first is routing visibility. If AS219516 begins originating 2a02:fd40::/48, obtains or leases IPv4 space, appears with observed neighbours, and maintains stable visibility over time, the network record would move from prepared to active. If it shows more than one active upstream, the continuity claim improves.

The second is commercial evidence. A public tariff page, customer contracts, procurement wins, named references, billing terms, or repeated service announcements would show that customers are being asked to pay for a defined product. For IZI, a narrow product would be more persuasive than a broad one. A specific business-continuity or managed-hosting offer with transparent support terms would fit the current record better than a claim of broad regional access coverage.

The third is compliance evidence. A communications licence would matter if IZI offers direct access or data-transmission services to subscribers. Published data-protection and abuse-handling practices would matter if it hosts customer workloads. Facility and supplier disclosures would matter if customers depend on physical continuity. The RIPE abuse mailbox is a start; it is not a full operating discipline.

The fourth is labour evidence. Network operation is a human service. Someone must design routing policy, respond to abuse, maintain customer premises or hosted systems, handle billing and answer incidents. Public evidence of technical staff, support hiring, contractor relationships or founder operating history would reduce the risk that the company is merely holding resources.

Until those facts appear, the fairest conclusion is restrained. IZI is not just a blank legal shell because it has a coherent RIPE identity and resource plan. But it has not yet proven, through public records, that the identity belongs to a revenue-producing operating company. The base case is a new infrastructure-services entrant at the preparation or very early operating stage. The upside case is a small Saint Petersburg provider focused on managed continuity, hosting or protected connectivity for SMEs. The downside case is dormant or lightly used resource holding, where the ASN and IPv6 objects never become a commercial network.

That is the economic test IZI now faces. The company does not need to become a national operator to be real. It does need to show that its resource control solves a customer problem often enough, and at a price high enough, to cover upstreams, support, compliance and capital renewal. Until the public footprint shows that conversion, the evidence supports readiness more strongly than revenue.

Sources