Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
    • Yandex Cloud Partner program
  • Blog
  • Pricing
  • Documentation
© 2025 Direct Cursus Technology L.L.C.
Yandex Cloud Interconnect
    • Overview
    • Terminology
    • Points of presence
    • Transceivers
    • Trunk
    • Private connection
    • Public connection
    • Routing
    • Monitoring
    • Data size and connection capacity
    • Quotas and limits
  • Pricing policy
  • Release notes
  1. Concepts
  2. Quotas and limits

Quotas and limits in Cloud Interconnect

Written by
Yandex Cloud
Updated at April 28, 2025

Yandex Cloud InterconnectYandex Cloud Interconnect

Yandex Cloud Interconnect has the following limits:

  • Quotas are organizational constraints that our support team can change upon request.
  • Limits are technical constraints of the Yandex Cloud architecture. You cannot change the limits.

If you need more resources, you can increase your quotas in one of the following ways:

  • Make a request to increase your quotas.
  • Contact support, detailing which quotas you want increased and by how much.

To have your request processed, you must have the quota-manager.requestOperator role or higher, e.g.,editor or admin.

You can manage quotas using Cloud Quota Manager.

QuotasQuotas

Type of limit Value
Number of private connections per trunk 2
Number of public connections per trunk 1

LimitsLimits

Type of limit Value
Maximum number of prefixes announced by the customer over BGP per private connection 500

Important

If you go over the limit of prefixes you get, the BGP session will be teared down for 30 minutes.

To prevent such session teardown when the number of prefixes unexpectedly goes up, consider using monitoring to set up notifications for the ipv4_announces_received_by_cloud_num metric and provide thresholds for it to trigger notifications.

Was the article helpful?

Previous
Data size and connection capacity
Next
Overview
© 2025 Direct Cursus Technology L.L.C.