Check-Host.cc

DNS Test from Latvia

1 node in Riga · LIXP Riga

Latvia — 1 Node

Cities
Riga
ISPs / ASNs
Orion Network Limited AS41564
Datacenters
Fiber Grid INC
Internet Exchanges
LIXP Riga — Latvian Internet Exchange Point, main neutral peering fabric in Riga
TeleHouse Riga — Carrier-neutral colocation and exchange services in Riga

DNS Testing from Latvia

A DNS check from Latvia queries your authoritative nameservers directly from our Riga probe and records the response. This confirms that DNS is resolving correctly from Latvian network infrastructure. Relevant use cases include GeoDNS configurations that route Baltic users to regional servers, and verification that a recent DNS record change has propagated to the authoritative tier as seen from Latvia.

Latvian ISPs run their own recursive resolvers for residential and business customers. Data center traffic typically uses ISP-provided resolvers or public resolvers like Cloudflare (1.1.1.1) and Google (8.8.8.8). Our DNS check bypasses recursive resolver caches entirely and queries the authoritative nameserver directly from the probe node, so you see the current authoritative answer rather than anything a caching resolver might still be returning.

If your GeoDNS policy directs Latvian users to a Baltic-region or Eastern European server, a DNS test from our Riga probe should return that IP. If it returns a Western European or global address, the policy is either not covering Latvian source IP ranges or the authoritative configuration is not working as expected. Compare against Estonian and Lithuanian DNS test results to determine whether the issue is specific to Latvia or affects the entire Baltic region.

Latvia Network Infrastructure

Riga is the central routing hub for Latvia and plays a wider role as a transit point for Baltic internet traffic. LIXP (Latvian Internet Exchange Point) is the country's main neutral peering fabric, connecting Latvian ISPs, transit providers, and content networks. TeleHouse Riga offers carrier-neutral colocation alongside exchange services. Together these give Riga a well-connected peering ecosystem for a city of its size, with paths to both Estonian and Lithuanian networks running directly without needing to transit through Warsaw or Frankfurt.

Our Riga probe node runs on AS41564, operated by Orion Network Limited. The physical data center is operated by Fiber Grid INC, a Latvian colocation provider. Orion Network Limited is an ISP with upstream transit that covers Baltic, Nordic, and Central European destinations. Fiber Grid INC operates as a carrier-neutral facility in Riga, which means multiple ISPs and transit providers colocate there and provide the node with good path diversity compared to a single-carrier data center.

Riga's position at the center of the Baltic states gives it low latency to both Tallinn (around 10 ms) and Vilnius (around 8 ms). Warsaw is reachable in around 22 ms. Stockholm is around 35–40 ms. Frankfurt is typically 45–55 ms from well-peered Riga infrastructure. These figures make Latvia a useful test location for measuring connectivity across the entire Baltic corridor, since Riga can reach all three Baltic capitals and their carrier ecosystems with minimal latency overhead.

Baltic undersea cables connect Latvia to Sweden via the Gulf of Bothnia route and to Germany via cables running through the Baltic Sea. Telia (AS1299), Tele2 (AS1257), and Latvian state-linked provider Lattelecom (AS12578) are among the primary transit carriers for international traffic. The domestic backbone is served by Lattelecom, LMT, and Bite, with several smaller ISPs and hosting providers peering at LIXP to keep local traffic local rather than routing it internationally.

Latvia is an EU member with EU data protection regulations, making it suitable for hosting applications that must stay within EU jurisdictions. The Riga data center market has grown steadily, driven by the Baltic tech sector and by operators who want a lower-cost EU hosting location compared to Amsterdam, Frankfurt, or London. Several international hosting companies maintain Riga nodes specifically to serve Baltic and Eastern European users with lower latency than routing everything through Western European hubs.