3.1 What is Google Cloud Interconnect
Google Cloud Interconnect allows you to create connections between data centers of Google cloud platforms and IT environments. Google Cloud Interconnect provides access directly to Google resources: Google Compute engine, Google cloud storage, Google Bigquery, Google Apps for work.
| Linxdatacenter Moscow | Linxdatacenter Saint Petersburg | |
| Google Belgium | 54 ms, 5 Mbit/s to 10 Gbit/s | 43 мс, от 5 Мбит/с до 10 Гбит/с |
| Google London | 52 мс, от 5 Мбит/с до 10 Гбит/с | 41 мс, от 5 Мбит/с до 10 Гбит/с |
| Google Virginia | 129 мс, от 5 Мбит/с до 10 Гбит/с | 118 мс, от 5 Мбит/с до 10 Гбит/с |
| Google Oregon | 185 мс, от 5 Мбит/с до 10 Гбит/с | 174 мс, от 5 Мбит/с до 10 Гбит/c |
| Google Tokyo | 275 мс, от 5 Мбит/с до 10 Гбит/с | 264 мс, от 5 Мбит/с до 10 Гбит/с |
| Google Singapore | 334 мс, от 5 Мбит/с до 10 Гбит/с | 323 мс, от 5 Мбит/с до 10 Гбит/с |
3.2 Features and Benefits
The Cloud Exchange networking platform allows integration with Google and has the following benefits:
3.3 How it works
The connection consists of a physical network connection from the customer's office or data center to Linxdatacenter's data center locations in Moscow (14, bldg. 1, 8th March street) and St. Petersburg (20a, Repischeva street), where the Cloud Exchange direct access ports are located.
Each Google Cloud Interconnect connection point has a high-speed fiber optic connection and API integration with Cloud Exchange, which simplifies ordering, provisioning and ongoing management.
3.4 Capacity
Bandwidth for the Client is scalable from 5 Mbit/s to 10 Gbit/s in 1 Mbit/s increments.
3.5 Connection options
Different applications and workloads require different network connectivity solutions. Several ways to connect your infrastructure to the Google Cloud Platform are supported.
3.5.1. Dedicated Interconnect
Dedicated Interconnect – это подключение корпоративного уровня к сети виртуального частного облака (VPC) к Google Cloud Platform. Данный вариант подключения рекомендуется для обеспечения высокой пропускной способности и при передаче больших объемов данных.
3.5.2. IPsec VPN
Google Cloud VPN is a secure connection to a VPC network in the Google Cloud through an IPSec VPN connection. Traffic moving between the two networks is encrypted by one VPN gateway and then decrypted by another VPN gateway. The connection is designed to transmit small amounts of data.
3.5.3. Direct Peering
Direct Peering is a direct connection to Google's public services and Google Cloud. It allows you to save on outgoing traffic charges compared to VPN or public access over the Internet. It is necessary to meet Google's requirements for peering (see Appendix 1.4).
3.5.4. Carrier Peering
Carrier Peering is a connection to Google's public infrastructure via a partner. It is used if the Client does not meet Google's requirements for peering.
| CONNECT | TYPE OF ACCESS | VOLUME |
| Dedicated Interconnect Dedicated, direct connection to VPC networks |
Internal IP address in the RFC 1918 address space | 10 Gbps for each connection |
| IPsec VPN tunnel Encrypted tunnel in the VPC network |
Internal IP address in the RFC 1918 address space | Up to 1 Gbps for each tunnel |
| Direct Peering Dedicated, direct connection to the Google network |
Public IP address | 10 Gbps for each connection |
| Carrier Peering Peering through the operator to the Google public network |
Public IP addresses | Variable |
3.6 How to order
3.7 Tariffication
© 2022 Linxdatacenter
BEST, money transfer and payments operator
The customer faced a technical issue with a persistent BGP session flag with Linxdatacenter hardware. We examined the problem and found out that one of customer’s hosts was under a DDoS attack.
Because of the distributed nature of the attack, traffic couldn’t be filtered effectively, and disconnecting the host from the external network wasn’t an option. The attack stopped after changes in the server configuration, but resumed the day after. A 5.5 Gbps attack overloaded the junctions with internet providers, affecting other Linx Cloud users. To mitigate the effects of the attack, we employed a dedicated DDoS protection service.
To ensure the continuous availability of resources hosted in Linx Cloud, we rerouted all the customer’s traffic through StormWall Anti-DDoS system. The attack was stopped within half an hour. To prevent future cyberattacks, we organized all connections to the customer’s resources through the StormWall network.
BEST, money transfer and payments operator
The customer faced a technical issue with a persistent BGP session flag with Linxdatacenter hardware. We examined the problem and found out that one of customer’s hosts was under a DDoS attack.
Because of the distributed nature of the attack, traffic couldn’t be filtered effectively, and disconnecting the host from the external network wasn’t an option. The attack stopped after changes in the server configuration, but resumed the day after. A 5.5 Gbps attack overloaded the junctions with internet providers, affecting other Linx Cloud users. To mitigate the effects of the attack, we employed a dedicated DDoS protection service.
To ensure the continuous availability of resources hosted in Linx Cloud, we rerouted all the customer’s traffic through StormWall Anti-DDoS system. The attack was stopped within half an hour. To prevent future cyberattacks, we organized all connections to the customer’s resources through the StormWall network.
Thank you for your inquiry, we will get back to you shortly!