Regional Invocations
How to execute an Edge Function in a particular region.
Edge Functions are executed in the region closest to the user making the request. This helps to reduce network latency and provide faster responses to the user.
However, if your Function performs lots of database or storage operations, invoking the Function in the same region as your database may provide better performance. Some situations where this might be helpful include:
- Bulk adding and editing records in your database
- Uploading files
Supabase provides an option to specify the region when invoking the Function.
Using the x-region
header
Use the x-region
HTTP header when calling an Edge Function to determine where the Function should be executed:
You can verify the execution region by looking at the x-sb-edge-region
HTTP header in the response. You can also find it as metadata in Edge Function Logs.
Available regions
These are the currently supported region values you can provide for x-region
header.
ap-northeast-1
ap-northeast-2
ap-south-1
ap-southeast-1
ap-southeast-2
ca-central-1
eu-central-1
eu-west-1
eu-west-2
eu-west-3
sa-east-1
us-east-1
us-west-1
us-west-2
Using the client library
You can also specify the region when invoking a Function using the Supabase client library:
_10const { createClient, FunctionRegion } = require('@supabase/supabase-js')_10const { data: ret, error } = await supabase.functions.invoke('my-function-name', {_10 headers: { 'Content-Type': 'application/json' },_10 method: 'GET',_10 body: {},_10 region: FunctionRegion.UsEast1,_10})
Handling regional outages
If you explicitly specify the region via x-region
header, requests will NOT be automatically re-routed to another region and you should consider temporarily changing regions during the outage.