# Supabase — Data API Routes to Nearest Read Replica

- Company: Supabase (supabase.com)
- Announced: 2025-04-04
- Category: capability-change
- Coverage: not counted
- Announcement: yes
- Group: announcements
- Source: https://supabase.com/blog/data-api-nearest-read-replica
- Record: https://forck.live/items/21362-data-api-routes-to-nearest-read-replica
- Subject: Supabase

Supabase released geo-routing for Data API requests, automatically directing read-only PostgREST requests to the geographically closest read replica to reduce latency. The feature is available by default when using the API load balancer endpoint and requires no configuration changes beyond updating the project URL.

## Evidence

Verbatim from https://supabase.com/blog/data-api-nearest-read-replica:

> Geo-routing automatically directs your Data API requests to the geographically closest read replica of your database, reducing latency and improving response times for your users around the world.

---

Record: https://forck.live/items/21362-data-api-routes-to-nearest-read-replica
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md