GPT‑5.x Responses API returns 400 BadRequest in East US/East US 2 (works in Sweden)

Question

GPT‑5.x Responses API returns 400 BadRequest in East US/East US 2 (works in Sweden)

Sroba, Roman 20

Hi, we’ve started seeing an issue with the Responses API in the East US and East US 2 regions when using GPT‑5.x models.

We consistently receive a 400 BadRequestError: {'error': {'message': 'There was an issue with your request. Please check your inputs and try again', 'type': 'invalid_request_error', 'param': None, 'code': None}}

If we switch the same request to the Sweden region, it works as expected. Is there a known service issue, limitation, or configuration difference affecting GPT‑5.x in East US/East US 2?

Vishant M 25 Reputation points

2026-03-10T10:05:28.1133333+00:00

Same! 5.4 seems to work but TPS is too low for our use case
Ayush Singh 5 Reputation points

2026-03-10T10:29:59.7933333+00:00

I am also facing the exact same issue from India. Using gpt-5.2 model:
openai.BadRequestError: Error code: 400 - {'error': {'message': 'There was an issue with your request. Please check your inputs and try again', 'type': 'invalid_request_error', 'param': None, 'code': None}}

Same code used to work since last one month without any changes ever since I created the gpt-5.2 deployment. Also tried upgrading the python openai client but it didn't work.
Harsh Pathak 5 Reputation points

2026-03-10T10:35:30.4+00:00

ERROR:

openai.BadRequestError: Error code: 400 - {'error': {'message': 'There was an issue with your request. Please check your inputs and try again', 'type': 'invalid_request_error', 'param': None, 'code': None}}

I have been facing this same error. The same code was working untill this morning and suddenly I keep getting this error.
Chris Battarbee 15 Reputation points

2026-03-10T10:49:10.32+00:00

Pretty sure there's an unreported outage happening right now. We're seeing the same thing.
Yuval Gabay 0 Reputation points

2026-03-10T12:08:41.3366667+00:00

yes we have issues with 5.2 on EastUs2 Region as well right now
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Hegedus, Paul 0 Reputation points

2026-03-10T13:27:10.3666667+00:00

I am also receiving this exact error with GPT 5.x models in East US 2 region this morning
SRILAKSHMI C 19,735 Reputation points Microsoft External Staff Moderator

2026-03-18T11:39:42.6+00:00

Hi Sroba, Roman,

The issue has been mitigated by the product group. Please check from your end and let me know if it is resolved or if you are still experiencing the issue.

Thank you!
Pooja Vijayakumar 15 Reputation points

2026-07-30T08:54:19.7433333+00:00

Hi @SRILAKSHMI C ,

I am still experiencing this issue for global standard deployment. I am using the gpt 5.6 sol model and consistently receive the 400 BadRequestError: {'error': {'message': 'There was an issue with your request. Please check your inputs and try again', 'type': 'invalid_request_error', 'param': None, 'code': None}}

Your answer

Vishant M 25 Reputation points

2026-03-10T10:05:28.1133333+00:00

Same! 5.4 seems to work but TPS is too low for our use case
Ayush Singh 5 Reputation points

2026-03-10T10:29:59.7933333+00:00

I am also facing the exact same issue from India. Using gpt-5.2 model:
openai.BadRequestError: Error code: 400 - {'error': {'message': 'There was an issue with your request. Please check your inputs and try again', 'type': 'invalid_request_error', 'param': None, 'code': None}}

Same code used to work since last one month without any changes ever since I created the gpt-5.2 deployment. Also tried upgrading the python openai client but it didn't work.
Harsh Pathak 5 Reputation points

2026-03-10T10:35:30.4+00:00

ERROR:

openai.BadRequestError: Error code: 400 - {'error': {'message': 'There was an issue with your request. Please check your inputs and try again', 'type': 'invalid_request_error', 'param': None, 'code': None}}

I have been facing this same error. The same code was working untill this morning and suddenly I keep getting this error.
Chris Battarbee 15 Reputation points

2026-03-10T10:49:10.32+00:00

Pretty sure there's an unreported outage happening right now. We're seeing the same thing.
Yuval Gabay 0 Reputation points

2026-03-10T12:08:41.3366667+00:00

yes we have issues with 5.2 on EastUs2 Region as well right now
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Hegedus, Paul 0 Reputation points

2026-03-10T13:27:10.3666667+00:00

I am also receiving this exact error with GPT 5.x models in East US 2 region this morning
SRILAKSHMI C 19,735 Reputation points Microsoft External Staff Moderator

2026-03-18T11:39:42.6+00:00

Hi Sroba, Roman,

The issue has been mitigated by the product group. Please check from your end and let me know if it is resolved or if you are still experiencing the issue.

Thank you!
Pooja Vijayakumar 15 Reputation points

2026-07-30T08:54:19.7433333+00:00

Hi @SRILAKSHMI C ,

I am still experiencing this issue for global standard deployment. I am using the gpt 5.6 sol model and consistently receive the 400 BadRequestError: {'error': {'message': 'There was an issue with your request. Please check your inputs and try again', 'type': 'invalid_request_error', 'param': None, 'code': None}}