Summary

  • Public records support a narrow but real identity: Pouya Nazm Najafabad Computer Co. is visible as the holder of AS16235, and RIPEStat showed the autonomous system as announced on July 15, 2026 with two IPv4 /24 prefixes in view.
  • The company's own public site describes a Najafabad-based ICT group offering internet service, dedicated bandwidth, network support, VoIP, security, server and storage maintenance, and tower or wireless infrastructure work; those claims are useful evidence, but they remain supplier claims until matched to live contracts and support records.
  • The operating story appears partner-dependent. RIPE Whois for AS16235 shows import, export and default routing through AS206388, Gostaresh Ertebat Azin Kia, while BGP and prefix records also connect the address space to that sponsor or upstream context.
  • The right conclusion is neither dismissal nor blind trust. Pouya Nazm looks like a small regional ICT and connectivity operator with real resource evidence; cloud or enterprise buyers still need active support, route-security, abuse-response, data-locality and service-level proof before relying on the name as assurance.

Pouya Nazm Najafabad Computer Co. is the kind of infrastructure name that can be easy to misread from the outside. A directory entry, an autonomous system number and a Persian-language service website can make the company look operationally concrete. They do not, however, answer the questions that matter to a buyer or analyst: who controls the service surface, what resources are actually routed, which partner stands behind the routes, and who answers when the network or customer environment fails.

The public record is still useful. It gives enough evidence to distinguish Pouya Nazm from a hollow listing. The company appears in internet number-resource records as AS16235, with the holder name "POYANAZM-AS Pouya Nazm Najafabad Computer Co(PJS)" in RIPEStat's AS overview. RIPEStat's announced-prefixes feed showed AS16235 announcing 109.95.63.0/24 and 185.186.241.0/24 across the July 1 to July 15, 2026 observation window. That is concrete network-resource evidence: the company name is attached to a visible routing surface, not just to a marketing page.

The legal and public-identity record points in the same direction, while also requiring care. The company site at poyanazm.com says the Pouya Nazm group began in Mehr 1381, roughly September to October 2002, in Najafabad, working across information technology and communications services: consulting, design, implementation, supervision, support, technical engineering, sales and commerce. It also says the group became an official member of Gostaresh Ertebat Azin Kia in 1395, around 2016-2017, in the fixed communications service field.

Rasmio, a corporate-record aggregator that says it draws from official Iranian company and gazette sources, lists the company as a private joint-stock company in Najafabad, with registration number 1305, a registration date of 1381/07/01, and later official notices including a 1403/05/11 change notice.

Those are identity anchors, not performance guarantees. The company site uses broad service language and local customer examples. It lists internet service, dedicated internet bandwidth, passive network implementation, student Wi-Fi and hotspot work, hardware and network support, fixed urban lines, VoIP, IP PBX, internal network services, server and storage maintenance, user and bandwidth management, security tooling, IP camera work, tower consulting and wireless city Wi-Fi.

The examples are regionally grounded: municipalities, local government offices, universities, schools, trade bodies, industrial companies, private and cooperative businesses, home users and small businesses around Najafabad and nearby areas.

That footprint matters because cloud infrastructure is never only a data-center phrase. For many regional operators, the assurance question lives in support labour, last-mile familiarity and the ability to keep a local customer connected when a remote platform would only show a ticket number. Pouya Nazm's own materials frame the company around support and local service delivery. A related Pouya Nazm training site also presents a Najafabad-based technical and vocational academy, founded in 1382, offering computer, accounting, management, financial-market, computer-specialist and digital-marketing courses.

That does not prove cloud capability, but it does show a wider public presence around local technical labour and skills formation.

The network record is the strongest part of the evidence pack, and it also sets the sharpest boundary. RIPE Whois for AS16235 identifies the aut-num as POYANAZM-AS, status ASSIGNED, created on August 31, 2012 and last modified on April 30, 2024. The same record shows import from AS206388, export to AS206388 and a default route to AS206388. CIDR Report's AS report similarly observed one upstream-adjacent AS for AS16235, AS206388, Gostaresh Ertebat Azin Kia Company PJSC, and listed two announced prefixes: 109.95.63.0/24 and 185.186.241.0/24.

The report is explicit that its upstream and downstream terms describe the view from its BGP collection point, not a complete commercial relationship. Even with that caveat, the direction of the evidence is clear: AS16235 should be evaluated together with the Azin Kia routing and sponsorship context.

The prefix evidence reinforces that dependency. BGP.he's record for 185.186.241.0/24 shows the prefix announced by AS16235, names Pouya Nazm as the origin registrant, marks the route as IRR valid and RPKI valid, and names Gostaresh Ertebat Azin Kia Company PJSC as the prefix registrant for the matching delegation. IPinfo's page for AS206388 also lists AS16235 among Gostaresh Ertebat Azin Kia's downstreams and shows AS49100 Pishgaman Toseeh Ertebatat as AS206388's upstream. That is not a weakness by itself. Smaller regional providers often sit behind larger licensed or backbone partners. But it changes the diligence question.

Assurance has to cover the sponsor path, the routing dependency and the customer-facing support chain, not just the AS holder name.

For an enterprise buyer, this produces a practical reading. Pouya Nazm can be described as a real regional ICT and connectivity operator with live number-resource evidence and a service narrative centered on local support. It should not be described, from the public record alone, as a globally assured cloud provider, a data-sovereignty platform, or a resilient enterprise infrastructure vendor.

The public materials reviewed for this piece do not show audited uptime statistics, public incident history, data-center certification, information-security certification, an IPv6 deployment, a documented abuse desk process, a public service-level agreement, or a transparent network operations escalation model. Absence from the public record does not prove absence in the business. It means those claims still need direct evidence.

The data-locality question is similar. Pouya Nazm's public story is local: Najafabad, Isfahan province, Iranian institutions, schools, municipalities, trade bodies, industrial zones and fixed communications service membership. That can be valuable for customers who care about local presence, in-person installation, Persian-language support and domestic connectivity. It can also raise concentration risk.

If a buyer depends on Pouya Nazm for hosted systems, fixed connectivity or managed network support, the buyer should ask where data is stored, which facilities are used, whether backups leave the locality, which subcontractors can access systems, and how the Azin Kia relationship affects operational control.

The route-security evidence is promising but incomplete. The BGP.he page's IRR and RPKI-valid labels for 185.186.241.0/24 are positive signals for that route, and RIPEStat's July 2026 visibility shows the AS was not dormant. But route validity on one visible prefix is not the same as end-to-end operational maturity. A customer would still want current ROA evidence for every routed prefix, a route-object and maintainer review, a contactable abuse and NOC path, confirmation of upstream diversity or acceptance of single-upstream risk, and a statement on what happens when the sponsor relationship changes.

Support accountability is where the public company narrative and the routing data meet. The official site emphasizes customer satisfaction and support across internet, network, hardware and software services. Its customer examples, if current, imply practical field capability: school networks, university Wi-Fi, local government connectivity, trade-body connections and business services are all operationally demanding in ways that a static website cannot fake for long. Still, the buyer's question is not whether support is advertised. It is whether support is measurable.

The responsible test is to ask for named escalation channels, support hours, maintenance windows, fault-response targets, customer references in the same service category, and evidence that the people responsible for field support can coordinate with the people responsible for routing.

The balanced verdict is therefore specific. Pouya Nazm Najafabad Computer Co. should be treated as a plausible regional infrastructure and ICT services operator with evidence in three layers: public corporate continuity, self-described local service delivery, and live internet number-resource visibility. The company should not be granted assurance merely because its name appears in a directory or on an ASN record. For cloud infrastructure, the assurance threshold is higher: route security, upstream dependency, data locality, incident response, support labour and service accountability all need to be tested.

That is not a criticism of the company. It is the correct standard for any small or regional operator whose public evidence is stronger on local service and routing presence than on audited cloud controls. Pouya Nazm's records give analysts a useful starting point. They show where to look, what to ask, and which risks are probably real. They do not replace the work of proving that the operating surface behind the name can carry the customer's risk.