Oakland, CA, United States of America

Ivan Kanevski

This inventor holds 1 USPTO granted patent. Top assignee: Mango Technologies, Inc.. Active years: 2026.

IDiyas Innovation Intelligence. (2026). Inventor Profile: Ivan Kanevski. Retrieved from https://idiyas.com/inventor/ivan-kanevski-c4aih7ur

Data source: USPTO (United States Patent and Trademark Office) public patent records. Weekly synchronization. How IDiyas builds this profile

Calculating rank

Average Co-Inventor Count = 1.0


Company Filing History:


Years Active: 2026

Loading Chart...
1 patent (USPTO):Explore Patents

Title: Ivan Kanevski: Patent Inventor in Oakland

Introduction

Ivan Kanevski is an inventor associated with Oakland, California, and Mango Technologies, Inc. His patent work addresses how online systems manage requests for data held by third-party services.

Latest Patents

Kanevski is credited with 1 patent: “Regulating Data Request Transmission to One or More Third Party Systems Across Clusters of Servers in an Online System.” The invention describes scheduling requests to third-party systems to account for limits on request volume or frequency. It also describes increasing the wait time between retransmission attempts when a third-party system indicates that a request violates its regulations.

Career Highlights

Kanevski’s patent reflects work on coordinating data access across online systems and third-party services. The approach is designed to help manage service-imposed request limits while enabling users to access data through an online system.

Collaborations

Kanevski’s listed coworkers include Dmitry Koterov and Taras Zubyk. His company affiliation is Mango Technologies, Inc.

Conclusion

Ivan Kanevski’s patent focuses on scheduling and retry strategies for third-party data requests, highlighting a practical approach to managing access across online systems.

Profile summary based on public USPTO records.
Data Sources: USPTO Patent Grant XML, Patent Center, EPO & CIPO • Normalized by IDiyas Innovation Graph. Methodology & provenance architecturePlease report any incorrect information to [email protected]
Loading…