¶ Connectivity
This page describes the access options for the technology infrastructure of Base Exchange and Base Clearing. The architecture provides multiple connectivity models, allowing each participant to select the one that best fits their operational, latency, and availability requirements.
¶ Table of Contents
¶ Version History
| Version | Compatible with previous version |
Change Description | Date |
|---|---|---|---|
| 1.0 | - | Original version | 27/08/2024 |
¶ Summary
Base Exchange and Base Clearing offer different connectivity options to their technology infrastructure. Each option is designed to meet specific requirements, whether for ultra-low latency, stability, rapid deployment, or ease of implementation. Participants can choose the connectivity model that best fits their operational needs. The final setup is defined jointly with the Base team during the onboarding process.
The infrastructure is distributed across multiple sites in the São Paulo region, covering trading, post-trading, and disaster recovery environments, as well as cloud-based resources to ensure business continuity and fault tolerance.
¶ High-Level Topology
EQUINIX SP6: Primary data center for the trading systems, providing access to the connectivity edge infrastructure for both Production and Certification environments.
Location: Av. Cid Vieira da Souza, 460-484, Colinas da Anhanguera, Santana de Parnaíba, SP, 06544, Brazil.
ASCENTY VINHEDO 2: Secondary data center for the trading and post-trading systems, providing access to the disaster recovery (DR) connectivity edge infrastructure.
Location: Avenida João Batista Nunes, 50, Distrito Industrial Benedito Storani, Vinhedo, SP, 13288-162, Brazil.
Cloud - AWS: Primary hosting environment for the post-trading systems, deployed in the AWS São Paulo Region (Brazil). Resources are distributed across the three Availability Zones (sa-east-1a, sa-east-1b, and sa-east-1c) to ensure business continuity, high availability, and fault tolerance.
¶ Connectivity Options
¶ Cross Connect
The Cross Connect access model provides the lowest possible latency when connecting to Base's technology infrastructure, as the participant's equipment is physically hosted within the same data center facility.
To ensure resilience and traffic segregation, each participant must establish four redundant single-mode fiber cross connects (LC/LC), with complete separation between Unicast and Multicast traffic:
- 2 × Unicast cross connects (primary and secondary)
- 2 × Multicast cross connects (primary and secondary)
BGP sessions are established over point-to-point links using /30 IP addressing provided by BASE. For unicast Order Entry traffic, participants must use a /26 subnet, also assigned by BASE, as the LAN address space for the origination and destination of trading messages.
The Cross Connect provides exclusive access to BASE's trading environment, with no routing to other services or network segments. Access to additional services requires the provisioning of dedicated cross connects for each specific purpose.
To use this access model, the participant must meet the following requirements:
- Support for the BGP (Border Gateway Protocol) routing protocol;
- Support for the PIM-SM (Protocol Independent Multicast - Sparse Mode) multicast routing protocol;
- Support for FHRP (First Hop Redundancy Protocol), such as HSRP or VRRP;
- Support for NAT (Network Address Translation), where applicable.
¶ Leased Lines
The leased lines access model provides direct connectivity to BASE's trading and post-trading systems through private network links contracted from telecommunications providers approved and accredited by BASE.
To use this access model, the participant must meet the following requirements:
- Support for the BGP (Border Gateway Protocol) routing protocol;
- Support for the PIM-SM (Protocol Independent Multicast - Sparse Mode) multicast routing protocol;
- Support for FHRP (First Hop Redundancy Protocol), such as HSRP or VRRP;
- Support for tracking features for automated failover and route monitoring;
- Support for QoS (Quality of Service);
- Support for NAT (Network Address Translation), where applicable.
BASE's infrastructure operates with complete network segmentation. Each environment requires dedicated and independent connectivity links, with no routing permitted between network segments.
¶ Fabric (Equinix / Ascenty)
The Fabric access model is an interconnection service that enables participants to establish private, on-demand circuits to BASE's technology infrastructure. It provides rapid provisioning, predictable latency, and secure traffic transport outside of the public internet.
To use this access model, the participant must meet the following requirements:
- Access the connectivity portal of the selected data center provider (Equinix or Ascenty);
- Order a physical Fabric connection port;
- Establish the virtual connections to the BASE-published services;
- Support for the BGP (Border Gateway Protocol) routing protocol;
- Support for the PIM-SM (Protocol Independent Multicast - Sparse Mode) multicast routing protocol;
- Support for FHRP (First Hop Redundancy Protocol), such as HSRP or VRRP;
- Support for tracking features for automated failover and route monitoring;
- Support for QoS (Quality of Service);
- Support for NAT (Network Address Translation), where applicable.
BASE's infrastructure operates with complete network segmentation. Each environment requires dedicated and independent private circuits, with no routing permitted between network segments.
¶ VPN SITE-TO-SITE
The VPN over the Internet access model secures communications through encrypted tunnels established between Participants and BASE's technology infrastructure.
To establish this connectivity, the Participant's environment must meet the following minimum requirements:
- Support for the BGP (Border Gateway Protocol) routing protocol;
- Support for the PIM-SM (Protocol Independent Multicast - Sparse Mode) multicast routing protocol;
- Compatibility with IPSec VPN technology;
- Support for the encryption and authentication algorithms defined by the BASE Network Operations Team (to be provided during the onboarding process);
- Support for GRE tunnels, required for the delivery of multicast traffic (Market Data);
- Support for NAT (Network Address Translation), where applicable.
BASE's infrastructure operates with complete network segmentation. Each environment requires dedicated and independent VPN tunnels, with no routing permitted between network segments.
¶ Connectivity Matrix
| Environment | Cross Connect | Leased Line (ISP) | Fabric | RTM | VPN | Internet |
|---|---|---|---|---|---|---|
| Trading | X | X | X | |||
| Market Data | X | X | X | |||
| Market Data Cloud - kafka | X | |||||
| Drop Copy | X | X | X | X | ||
| Post-Trade | X | X | X | X | X | |
| Testing and Certification | X | X | X | X |