A router has a rather unglamorous job: it must decide where to send a packet next. Alex Zinin spent years explaining that decision, improving it and helping other engineers understand what could go wrong. Then he founded a company around a different question. If mobile operators carried so much of the internet's activity, why were they having such a hard time participating in the businesses built on top of it?
The distance between those questions looks larger than it is. Both concern the connections inside a system: who passes something to whom, under what conditions, and with what consequences. Zinin's career has taken him from Kazan to Moscow, into American networking companies and across Asia. Along the way, the object being routed changed from packets to commercial opportunity. The habit of examining the machinery remained.
Cinarra, which he co-founded in 2012 and led as its founding CEO, offered mobile operators a way into the advertising economy. SoftBank led a $20 million funding round in 2015. The company became a wholly owned SoftBank subsidiary in 2020. Those are useful milestones. To understand the person behind them, however, it helps to begin with the less photogenic business of teaching a network to behave.
Before the pitch, the packet
Zinin's early work included consulting and instruction at AMT Group in Russia. He supported major internet service providers and trained hundreds of professionals. At Cisco, he worked as a routing protocol escalation engineer, close to the developers responsible for the protocols themselves. Later, at Nexsi Systems, he became a senior routing software architect.
It is an education in practical consequences. A diagram may look elegant; an operator still has to make it run. Teaching introduces another test: can you explain the mechanism clearly enough for somebody else to use it? Zinin's professional record includes both tasks, the technical work and the effort to make that work intelligible.
His book, Cisco IP Routing: Packet Forwarding and Intra-domain Routing Protocols, appeared in October 2001. It explored four routing protocols, including OSPF and EIGRP, and walked readers through the processes inside routers. The contents move from addressing and forwarding to dynamic routing and the ways engineers can influence routing behavior. There are configurations, diagrams and worked examples. A router, mercifully, does not require a motivational speech.
The book's premise was that understanding the internals gives an engineer more control. That is a useful lens for the career that followed. Zinin had already spent time helping people operate networks; now he was putting an explanation of their inner workings into a form other engineers could return to.
The internet's committee room
His work also extended into the Internet Engineering Task Force. Zinin served as a Routing Area co-director from 2002, and his IETF record lists fourteen RFCs. These documents cover subjects such as OSPF signaling, area border routers and fast rerouting. The titles have little interest in charming a general audience. Their job is to help independent implementations agree on behavior.
One example is RFC 5286, which Zinin co-edited with Alia Atlas. Published in September 2008, it describes loop-free alternate paths for IP fast reroute. When a link fails, a router can use a previously calculated backup route while the network works out its new arrangement. The purpose is to reduce lost packets during that interval. Whether a suitable backup exists depends on the network's topology.
Another, RFC 6987, describes how an OSPF router can signal that traffic should avoid passing through it, or treat routes through it as less desirable. Published in 2013, it lists Zinin at Cinarra. Even after he had started a business, his name was still appearing on the detailed rules that help networks accommodate change.
The parallel with his later work is an interpretation of the record, rather than a claim about his private motives. His public projects repeatedly ask what happens at a boundary: between routers, between industries, and eventually between organizations and the people permitted to operate their systems.
A familiar network, an unfamiliar business
At Alcatel and Alcatel-Lucent, Zinin's responsibilities broadened into technology and business leadership. His career included work in Singapore and responsibility for IP solutions in Asia Pacific. He received Alcatel Fellow and Bell Labs Fellow honors. In September 2010, he became Cisco's chief technology officer for its service provider business in Asia Pacific and Japan.
That position covered a wide territory of technology, including next generation IP networks, video, mobility, data centers and cloud computing. It also put the business problems of service providers within his remit. His eventual startup would address one of those problems: how operators could use their existing capabilities to earn revenue beyond selling connectivity.
Cinarra brought Zinin back together with Alexander Nikolaev, with whom he had previously built Center Group in Kazan. Nikolaev organized the Russian development operation; Zinin handled international business. Their first investment was about $200,000 of their own money. The startup required a working product and operator integrations before the commercial idea could become convincing.
There was even a small geographical joke in the name. Nikolaev explained that the Sinara River ran near where he was born. The founders wanted a distinctive name that someone could hear over the telephone and write down. In an industry fond of initials, that was a refreshingly practical naming brief.
Japan already knew his name
In October 2013, Cinarra announced a $4.5 million Series A led by Almaz Capital, with participation from Cisco and individual investors. Geoffrey Baehr joined the board. The financing supported team expansion, development and bringing products to market. The company was presenting itself as a mediator between operators and internet application platforms.
Japan was an early commercial destination, helped by relationships Zinin had developed during his previous work. In his account of that period, prospective partners wanted to be the first to work with the new venture. Discussions began in 2013, before the public funding milestone that drew attention two years later.
He described Japanese partnerships as demanding close involvement, attention to quality and a quick response when something went wrong. The attraction came with obligations. A founder could not simply deliver a product and expect the relationship to take care of itself. Partners wanted to understand the work and its progress.
SoftBank's 2015 investment therefore combined financing with an operating relationship. The companies had begun joint business in Japan, and SoftBank had introduced the service into its network. Almaz Capital and Siguler Guff also participated in the round. Money and a place to deploy the product arrived together.
“Our relationship with SoftBank signifies a fundamentally new phase for Cinarra.”Alex Zinin, July 2015
The next year brought a joint media development project with Hakuhodo DY Digital and Hakuhodo DY Media Partners. It used anonymized behavioral data to help distinguish audiences more or less likely to be reached by television advertising. In July 2017, Cinarra Japan announced a beta platform through which customers could manage advertising and data analysis themselves. The bridge between industries was acquiring specific uses.
A smaller audience can reveal too much
The advertising proposition carried a difficult engineering question: how to extract useful patterns without exposing individuals. In November 2017, Zinin wrote about location privacy after researchers demonstrated how advertising tools could be used to track people. His response examined the mechanics of targeting and reporting together.
A group can appear anonymous until filters whittle it down. Detailed reports can expose what a broader campaign audience seems to conceal. Zinin argued for minimum group sizes in both targeting and reporting, alongside limits on the simultaneous precision of location, time and user information. He presented these as design choices that advertising systems needed to make.
That position deserves attention because he was building a business that depended on the usefulness of location data. The essay made the tradeoff explicit. Advertisers could learn about patterns without being given every available detail. He said Cinarra had applied the principles he described. The claim belongs to his account of the platform; the larger argument is that privacy requires decisions inside the machinery.
The founder outside the org chart
When Zinin introduced his personal blog in August 2017, he began with roles that a corporate biography generally leaves out. He was a father of three, a son, a brother, an uncle and a friend. He also described himself as a founder, a technology and business enthusiast, and someone trying to develop intellectually.
He had considered blogging for years before deciding he had experience worth sharing. His opening was candid about the limits of that invitation: “I don't pretend to know everything”. The point was to offer his views, without expecting readers to adopt them. It was a modest entrance for somebody whose professional life already included a textbook and internet standards.
Still asking who controls the system
His subsequent career included PR3VISION consulting and cloud infrastructure leadership at Acronis. In February 2023, Acronis identified him as its chief cloud infrastructure officer while announcing recognition on CRN's Data Center 50 list. By 2026, his published role at Commvault was vice president and general manager for managed service providers.
His recent writing concerns digital sovereignty. In May 2026, he examined who can access an environment, including vendors and support personnel, and how telemetry can cross organizational or jurisdictional boundaries. Another essay addressed recovery: controls have to hold when data is restored as well as when it is stored. These are operational questions with technical consequences.
In August, he discussed sovereignty with Max Mortillaro on Commvault's STRIVE series. His accompanying article treated continued operation under changing assumptions as a business problem involving technical, legal and operational decisions. The subject had widened again. The questions still required looking beneath the label attached to a system.
The career offers an unusually concrete progression: explain a router, help define its behavior, lead technology across a region, build a company between two industries, examine the boundaries around data. Each stage adds people and institutions to the diagram. Somewhere inside it remains the original engineer's question: when this system has to work, what actually happens next?