Belgrade · Serbia
PeeringDB records no internet exchange under Belgrade's city entry and seven colocation facilities holding 49 networks between them. Cetin Data Center reports 26, more than any other building in the city. No mobile ASN appears in the Serbian carrier data behind this page, so a Belgrade address reflects an operator's registration rather than a device in the city.
Internet exchanges in Belgrade
An exchange is a shared switch where networks hand traffic to each other directly. Participant counts come from PeeringDB, where each network maintains its own record.
| Exchange | Participants | Registry carriers peering |
|---|---|---|
SOX Serbia Serbian Open eXchange | 43 | none in the registry |
Exchange records: PeeringDB.
Colocation facilities
Buildings where networks put equipment. The network count is how many PeeringDB members list a presence there, which shows where capacity in the city sits.
| Facility | Networks present | Address |
|---|---|---|
| Cetin Data Center | 26 | 90 Omladinskih brigada |
| Telekom Srbija data centar | 9 | Katiceva St. 14-18 V floor |
| BeotelNet Data Center | 5 | 37 Bulevar vojvode Mišića |
| Serbia BroadBand | 4 | Kumodraska 241 |
| Orion Telekom Data Center | 3 | Naselje Zemun Polje Mala Pruga 8 Beograd |
| Absolut Solutions | 2 | Nehruova 82a |
| PhoenixNAP BELGRADE | 0 | Omladinskih brigada 1 |
What a Belgrade IP address tells you
Belgrade's recorded capacity sits in colocation rather than at an exchange. PeeringDB files seven facilities in the city and 49 networks across them. Cetin Data Center holds 26 of those, over half the total, with Telekom Srbija data centar next at nine and BeotelNet Data Center at five. Serbia BroadBand has four and Orion Telekom Data Center three, with Absolut Solutions on two. PhoenixNAP BELGRADE is on record with none. No exchange participant count exists for this entry, and the carrier data behind this page attaches no Serbian mobile ASN to any of these buildings.
An address that a database places in Belgrade need not be a device in Belgrade. Operators announce blocks from a registry record that carries a single address for a whole allocation, and mobile traffic leaves a network through a small number of gateways that can sit far from the subscriber. Geolocation providers read the operator's own published location and copy it, so a connection from anywhere in Serbia can resolve to Belgrade in a lookup while the handset never came near any of the seven facilities on record.
Someone checking an address learns more from the origin ASN and the netname on the specific prefix than from the city field. The ASN names the network that announced the block, and the netname says how that network chose to describe the range, including whether it is set aside for mobile subscribers. Neither says the traffic passed through Cetin Data Center or any other building on the list. The 49 facility networks describe where colocation is documented in Belgrade, not where a given address sits.
Questions
Which internet exchanges are in Belgrade?
PeeringDB lists none under the Belgrade city entry used for this page. What it records instead is seven colocation facilities holding 49 networks. Networks in Belgrade may still interconnect privately inside those buildings, and private interconnection is not counted in any exchange figure.
Do Serbian mobile carriers peer in Belgrade?
The carrier data behind this page holds no Serbian mobile operator, and no carrier ASN is attached to the facilities recorded in the city. That is silence in the registry rather than evidence that mobile networks exchange no traffic in Belgrade.
Does an IP that geolocates to Belgrade mean the device is there?
No. The city label comes from the address block's registration and the operator's published location, not from the device. A subscriber elsewhere in Serbia can leave through a gateway whose addresses are registered in Belgrade and will appear in Belgrade in any database copying that record.
Sources
- PeeringDB - exchanges, participant counts, facilities and network presence, snapshot 2026-09-07
- PROXIES.SX carrier and ASN registry - operator ASNs used to match peering participants