Unsupported_country_region_territory" Error in Production Environment

API
1

Hello,

I have been encountering the following error, which is preventing proper operation in my production environment:

{
“error”: {
“code”: “unsupported_country_region_territory”,
“message”: “Country, region, or territory not supported”,
“param”: null,
“type”: “request_forbidden”
}
}

This issue does not occur in my local environment, where everything works fine. However, in the production environment, the above error is causing my service to be non-operational.
I am using a VPN service from a Japanese provider called “Sakura Internet,” and my server is located in Hokkaido, Japan. Since Japan should be a supported country, I believe this location should not be subject to any regional blocking by OpenAI.
Additionally, I tried creating a new account to test, but the same error occurred.

This error is seriously impacting my ongoing services, and I am in urgent need of assistance.
I would greatly appreciate it if you could check into this matter as soon as possible and provide guidance on how to resolve this issue.

Thank you very much in advance for your support.

2

Welcome to the dev forum.

Do they have other datacenters, maybe? I’d check the DNS for the IP or ask your host.

Are you using CloudFlare?

3

Hello, I’m also having the same issue in Taiwan (also supposedly supported).

Error: 403 Country, region, or territory not supported
    at (node_modules/.pnpm/openai@4.57.1_zod@3.23.8/node_modules/openai/error.mjs:47:0)
    at (node_modules/.pnpm/openai@4.57.1_zod@3.23.8/node_modules/openai/core.mjs:268:23)
    at (node_modules/.pnpm/openai@4.57.1_zod@3.23.8/node_modules/openai/core.mjs:311:0)
    at (app/api/v6/analyze/route.ts:75:24)
    at (app/api/v6/analyze/route.ts:31:11)
    at (node_modules/.pnpm/next@15.0.0-rc.0_@opentelemetry+api@1.9.0_react-dom@19.0.0-rc-d025ddd3-20240722_react@19.0.0-_fkoshl6xyu3n4afphgdvrcv7zm/node_modules/next/dist/esm/server/future/route-modules/app-route/module.js:214:0)
    at (node_modules/.pnpm/next@15.0.0-rc.0_@opentelemetry+api@1.9.0_react-dom@19.0.0-rc-d025ddd3-20240722_react@19.0.0-_fkoshl6xyu3n4afphgdvrcv7zm/node_modules/next/dist/esm/server/future/route-modules/app-route/module.js:129:0)
    at (node_modules/.pnpm/next@15.0.0-rc.0_@opentelemetry+api@1.9.0_react-dom@19.0.0-rc-d025ddd3-20240722_react@19.0.0-_fkoshl6xyu3n4afphgdvrcv7zm/node_modules/next/dist/esm/server/future/route-modules/app-route/module.js:279:0)
    at (node_modules/.pnpm/next@15.0.0-rc.0_@opentelemetry+api@1.9.0_react-dom@19.0.0-rc-d025ddd3-20240722_react@19.0.0-_fkoshl6xyu3n4afphgdvrcv7zm/node_modules/next/dist/esm/server/web/edge-route-module-wrapper.js:90:0)
    at (node_modules/.pnpm/next@15.0.0-rc.0_@opentelemetry+api@1.9.0_react-dom@19.0.0-rc-d025ddd3-20240722_react@19.0.0-_fkoshl6xyu3n4afphgdvrcv7zm/node_modules/next/dist/esm/server/web/adapter.js:157:0)
4

Do they have other datacenters, maybe? I’d check the DNS for the IP or ask your host.

Are you using CloudFlare?

5

Hi, I’m using Vercel and Next.js - with help from Vercel support I managed to fix it by disallowing Hong Kong as a location for Edge Functions.

1 Like
6

Hello, my name is Dai.
I also have the same problem as shogo1. I also use a VPN service from a Japanese provider called SakuraInternet.
I checked the IP with DNS. (Located in Japan)
I contacted my provider and they said it was their problem.
I don’t use CloudFlare.
Do you have any hints on how to deal with this?