Riga · Latvia
PeeringDB records five internet exchanges in Riga, Latvia, with 105 networks peering across them. PITER-IX Riga is the busiest by participant count at 68, ahead of SMILE-IXP at 24. Seven colocation facilities hold 64 network presences. An address that geolocates to Riga shows where an operator registered the block, not where a device sits.
Internet exchanges in Riga
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 |
|---|---|---|
PITER-IX Riga | 68 | |
SMILE-IXP Santa Monica Internet Local Exchange | 24 | |
GLV-IX Government of Latvia Internet Exchange | 7 | |
LIX-LV Latvian Internet Exchange | 6 | none in the registry |
MSK-IX Riga | 0 | 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 |
|---|---|---|
| LVRTC TV Tower | 34 | Zakusalas krastmala 1 |
| Perses 2 - Riga | 19 | Perses 2 |
| RETN AD DC | 5 | 73, A. Deglava str. |
| Sigmanet Data Centre | 3 | Raina blvd. 29 |
| Talejas iela 1 | 2 | Talejas iela 1 |
| Balticom Datacenter | 1 | not listed |
| Versija SIA | 0 | Arhitektu iela 1 Perses iela 2 - TB |
What a Riga IP address tells you
Riga's peering concentrates in one exchange. PITER-IX Riga carries 68 participants in PeeringDB, and SMILE-IXP, listed as the Santa Monica Internet Local Exchange, carries 24. The Government of Latvia Internet Exchange, GLV-IX, has 7, LIX-LV has 6, and MSK-IX Riga records none. Colocation holds a second layer of capacity, with 64 network presences spread over seven facilities and the LVRTC TV Tower accounting for 34 of them, ahead of Perses 2 - Riga at 19. Exchange records flag carrier ASNs at PITER-IX Riga, SMILE-IXP and GLV-IX, though the carrier registry names no Latvian mobile operator to match them against.
An address that a database places in Riga need not be a device in Riga. An operator announces a block from whatever location its registry record gives, and a single record can cover the whole country while the addresses inside it are handed out anywhere the operator runs. Mobile traffic compounds this, because handsets across Latvia leave through a small number of gateways, and every session behind one gateway inherits that gateway's address. Geolocation databases read the operator's own published location, so they repeat the registry entry rather than measure the device.
Someone checking a Riga address gets more from the routing data than from the city label. Look at the origin ASN on the specific prefix and the netname on the registry object covering it, then check whether that ASN appears at any of the five Riga exchanges or in the 64 network presences across the seven facilities. An ASN with no Riga presence and a country-wide netname tells you the city name came from a registry field, not from where the traffic entered the network.
Questions
Which internet exchanges are in Riga?
PeeringDB lists five. PITER-IX Riga has 68 participants, SMILE-IXP has 24, GLV-IX has 7, LIX-LV has 6, and MSK-IX Riga has none recorded. Across all of them the registry counts 105 peering networks in the city.
Do Latvia mobile carriers peer in Riga?
The registry is silent on this. Carrier ASNs are flagged at PITER-IX Riga, SMILE-IXP and GLV-IX, but the carrier list for Latvia is empty, so no Latvian mobile operator can be matched to those ASNs from this data alone.
Does an IP that geolocates to Riga mean the device is there?
No. The city label comes from the operator's registry record for the address block, which can cover all of Latvia. Mobile sessions in particular exit through a handful of gateways, so many devices far from Riga share an address that reads as Riga.
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