City network · Latvia

Riga internet exchanges, data centers and carriers

PeeringDB's 2026-09-07 snapshot records 5 internet exchanges and 7 colocation facilities in Riga, Latvia. The largest exchange is PITER-IX Riga, with 68 participant entries. 2 mobile carriers from our registry peer here.

Exchanges
5
Facilities
7
Snapshot
2026-09-07
Country
Latvia (LV)
Internet exchanges
5
Largest exchange
PITER-IX Riga (68 participants)
Exchange participant entries
105
Colocation facilities
7
Facility network presences
64
Registry carriers peering here
2
Snapshot
2026-09-07

The 2026-09-07 PeeringDB snapshot records 5 exchanges and 7 facilities in Riga, Latvia. Their entries sum to 105 exchange participants and 64 facility network presences; the same network can appear more than once.

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.
Internet exchanges in Riga
ExchangeParticipantsRegistry carriers peering
PITER-IX Riga68Bitė Lietuva AS13194
SMILE-IXPSanta Monica Internet Local Exchange24Tele2 Eesti AS1257Bitė Lietuva AS13194
GLV-IXGovernment of Latvia Internet Exchange7Tele2 Eesti AS1257
LIX-LVLatvian Internet Exchange6none in the registry
MSK-IX Riga0none in the registry

Colocation facilities in Riga

Buildings where networks put equipment. The network count is how many PeeringDB members list a presence there, which records reported presence rather than available capacity.
Colocation facilities in Riga
FacilityNetworks presentAddress
LVRTC TV Tower34Zakusalas krastmala 1
Perses 2 - Riga19Perses 2
RETN AD DC573, A. Deglava str.
Sigmanet Data Centre3Raina blvd. 29
Talejas iela 12Talejas iela 1
Balticom Datacenter1not listed
Versija SIA0Arhitektu iela 1 Perses iela 2 - TB

What these records establish

This page groups the saved exchange and facility records for Riga. A sum of participant or facility counts is not a count of unique networks, traffic volume, available capacity or service coverage.

PeeringDB is user-maintained. Its records describe reported interconnection infrastructure; they do not trace a particular request or locate a subscriber. A missing record in this snapshot is not proof that an operator has no presence or private connection in the area.

An IP geolocation result is a separate estimate. MaxMind documents accuracy limits and explains that its location data cannot identify a specific household, person or street address. This registry does not perform a geolocation lookup or measure where an individual device is located.

Questions

How many exchanges and facilities are recorded in Riga?
5 exchanges and 7 facilities appear in the 2026-09-07 snapshot. The tables show the saved records and link to the publisher for current details.
Are the totals unique networks?
No. Participant entries are summed across exchanges and network presences across facilities. A network listed at several locations contributes to several entries.
Does a Riga IP label prove that a device is there?
No. These infrastructure records do not establish a device location. Consult the geolocation provider’s accuracy information and the specific network record for the claim you are evaluating.

Sources

PeeringDB supplies the exchanges, participant counts, facilities and network presence (snapshot 2026-09-07); MaxMind documents the limits of IP geolocation; the PROXIES.SX carrier registry supplies the operator ASNs used to match peering participants.

  1. [1]https://www.peeringdb.com/
  2. [2]https://support.maxmind.com/knowledge-base/articles/maxmind-geolocation-accuracy
  3. [3]https://www.proxies.sx/carriers

These records describe where networks interconnect. A Riga IP address does not show that a device is in Riga: mobile carriers route traffic from wide areas through shared gateways, and geolocation databases estimate from registration data.