Regions and data centers
Learn how the Infobip global infrastructure is organized, where data is processed, and how the platform stays available. For private network connectivity to the platform, see Dedicated connections.
How the infrastructure is organized
Infobip infrastructure is built in layers, from the largest to the smallest, and each layer adds redundancy. An infrastructure region is a logical unit of selected locations: two or more interconnected, redundant locations within a geopolitical area. This design provides resilience and backup, improving the reliability and availability of products hosted in that region. Regions are determined by the headquarters or geographical location of customers. This enables a customer-centric organization of infrastructure that aligns with specific needs and data processing requirements.
The EU region also includes the EU locked region, with two locations, EU1 and EU2, in the Infobip data centers in Sweden (SE1) and Germany (FR4). Only EU-based staff have access to these locations, to support compliance with the Schrems II ruling.
Each region is made of locations. A location is a logical construct that combines software components to create products used by customers, and it is made of one or more data centers. Locations are strategically distributed across the globe to optimize customer connectivity and minimize latency. A location is typically created when a data center is deployed, unless that data center extends a location that already exists.
Each location has one or more data centers. A data center is a distinct physical facility, often one or more buildings, designed to house and manage computer systems and digital infrastructure. It has its own power, cooling, and networking infrastructure, with stringent physical security. This dedicated setup lets the data center operate independently, keep its hardware at optimal temperatures, support efficient communication between components, and safeguard against unauthorized access. Together, these ensure reliable and secure digital operations.
Inside a data center, availability zones (AZs) are the building blocks: small, independent units designed to ensure high availability. They are the smallest logical sections inside a data center. Each AZ is made of physical hardware: racks, power systems, servers, storage units, and top-of-the-rack switches. If one zone has a problem or goes offline, the other zones maintain service. Together, the zones support regional services, maintain overall capacity, and keep a high level of availability.
Data center locations
Infobip operates a global network of data centers, accessible through points of presence (data center colocations) around the world. Traffic is processed in your account's location, which helps meet data privacy and regulatory requirements and reduces latency. To find the location of your account, check your Base URL, shown on the homepage of the web interface. It includes the region ID of your account's location: {baseUrl}.api-{regionId}.infobip.com. Reporting data stays local in locations with SaaS (see How data is processed). Internet Exchange centers are also available for establishing private peering with customers.
Each location offers one or both of the following:
- CPaaS: Connectivity and routing infrastructure, so traffic to and from that region is carried and processed locally.
- SaaS: Software products (such as the web interface, Customer Profiles, and reporting) hosted at that location. Locations without SaaS replicate reporting data elsewhere for analytics, as described in How data is processed.
Beyond these locations, Infobip operates more than 30 voice and edge points of presence worldwide. The following table lists the Infobip locations and what each offers:
| Location | CPaaS | SaaS |
|---|---|---|
| United States | ✓ | ✓ |
| Canada | ✓ | |
| Mexico | ✓ | ✓ |
| Brazil | ✓ | |
| United Kingdom | ✓ | ✓ |
| Germany | ✓ | ✓ |
| Sweden | ✓ | ✓ |
| Turkey | ✓ | ✓ |
| Qatar | ✓ | ✓ |
| United Arab Emirates | ✓ | ✓ |
| Saudi Arabia | ✓ | ✓ |
| South Africa | ✓ | |
| Pakistan | ✓ | ✓ |
| India | ✓ | ✓ |
| Hong Kong | ✓ | |
| Singapore | ✓ | |
| Malaysia | ✓ | |
| Indonesia | ✓ | ✓ |
When choosing a location to connect to Infobip services or products, consider proximity, latency, and local regulations. With at least two locations in each core region (USA, EU, India), you can connect locally and have your traffic processed locally. The dual-location setup keeps services accessible even if one location fails, and supports disaster recovery (DR) and business continuity management (BCM).
For the specific data center facilities and the interconnection services available at each, see the connectivity table in Dedicated connections. For the IP addresses to safelist, see IP address safelist.
How data is processed
Where your reporting and analytics data goes depends on whether your location has SaaS products. A location with SaaS keeps reporting data on-site and does not replicate it to Germany, and you use the local Infobip account for analytics. A location without SaaS replicates reporting data to the Germany (Frankfurt) location, and you use the Infobip account in Germany for analytics. There is one exception: if a different location in the same region has SaaS, the data goes to that location, not to Germany.
Data retention [#data-retention-how-data-is-processed]
Infobip retains message and reporting data free of charge for a set period. Retention periods vary by product and data type, and can be customized. To keep data longer, set up a recurring report or export data through Reporting. See the Data retention notice(opens in new tab) for the current periods.
Reliability and failover
Infobip connects its data centers through two kinds of links and a monitoring system that moves traffic between them. Together, they keep traffic flowing when a link, a data center, or a location has a problem.
| Layer | What it is | What it protects against |
|---|---|---|
| Private Layer 2 links | The primary backbone between Infobip data centers: a direct, dedicated channel, exclusive to the Infobip network, for lower latency and faster data transfers | Public internet issues, such as ISP disruptions and rerouting problems, and the risks of shared external traffic |
| Redundant public connections | Failover paths over public networks, distributed across locations for disaster recovery: if a data center has an outage, traffic fails over to another location with minimal downtime | The failure of a Layer 2 link, a hardware failure, or a data center outage |
| Automated rerouting | The Infobip Auto Rerouting system, which monitors the health of all links. When it detects packet loss, it moves traffic to a predefined healthy path automatically, before the issue affects data flow, and keeps in-flight transmissions intact. | Packet loss on any link, Layer 2 or public |
Dedicated connections
Private network connectivity options to the Infobip platform, including cross-connects, MPLS, and internet exchanges.
Platform status and incidents
Check platform status, incident stages, maintenance types, and how to request a root cause analysis.
Network connectivity troubleshooting
Diagnose connection problems between your system and Infobip endpoints.
Was this page helpful?