Dashboard -> Logs -> Completions - metadata blocked by CORS

Not specifically to do with the API, but when I attempt to review the logs via the dashboard for the completions endpoint - I am getting

https://api.openai.com/v1/dashboard/chat/completions_metadata’ from origin ‘https://platform.openai.com’ has been blocked by CORS policy

This results in the completions tab showing zero data, even though I have been submitting completions for weeks.
The outage only seemed to start for me 2 or so days ago.

index-B3LRGeqA.js:66 GET https://api.openai.com/v1/dashboard/chat/completions_metadata net::ERR_FAILED

I really need access to the logging capability so I can debug/triage token usage when constructing completions requests. Otherwise all I have to go by is the ‘usage’ dashboard page, which shows a time delayed view of daily usage - this is not as effective as reviewing the actual logs.

Seems this issue has cropped up once or twice in the past - but was intermittent affecting some and not others.

I’ve tried clearing browser cache, cookies, hard refreshes, new incognito windows etc.
Nothing has resolved it on my end.

8 Likes

I’m facing the same issue on https://platform.openai.com/logs?api=chat-completions. Unable to see logs and debug because of this

@baaleos were you able to find a solution?

Same to me.
@baaleos @knolskape Have you recently changed anything in your account settings? e.g. passed verification or smth else

Ironically - I upgraded my chatgpt account - went from a Plus account to Pro.
I am wondering if that is what has caused this - hard to imagine throwing more money at OpenAI would result in loss of service?

I don’t think your account on the platform is linked to your personal account.
I recently verified my business on the Platform, so I wondered if that might be the reason.

For the amount I am spending per month on ChatGPT + API - the support system is crap.

Just tried the following - no luck

Disabled api logging on all projects, organisation etc.
Re-enabled - no change
Started identity verification process for my individual account
Verified that Project → People shows me listed as owner and it has the ‘you’ tag against me.
Created a new project → enabled api logging, getting CORS error on that one too.
Disabled viewing of API logs for project, reenabled → no change

I am running out of ideas - this is literally an OpenAI side thing - even if it is some sort of edge case where my account has some sort of combination of data in the settings, it shouldn’t be triggering a CORS error.

1 Like

Have got a support ticket raised now - will see if they can resolve it.

2 Likes

issue - returning 404
OPTIONS https://api.openai.com/v1/dashboard/chat/completions_metadata

when the GET request is Sec-Fetch-Mode: cors


alt:

from openai import OpenAI
client = OpenAI()

completions = client.chat.completions.list()
print(completions)

Having the same issue since feb 2. Only the completions api log is not accessible. When are they gonna fix this?

I’ve provided screen recording to the support. Once they answer I’ll write here.

If someone from support hears that there’s a 404 server error from an http method, had been provided a URL and request header policy, and then they want you to make a video yourself, they are just wasting your time.

Also provided a screen recording.

1 Like

same issue here :expressionless: I can’t see logs in the page https://platform.openai.com/logs

Engineer now asking for timestamps and request ids - sent him what I have access to.
Interestingly - I did test this from AWS EC2 - A windows instance, and it got exactly the same result - so this is an account level thing and not related to my browser/laptop etc.

…To show how out-of-touch and unknowledgeable they are. That is a “make them spin their wheels until they go away” response.

There’s no request ID when the https GET call is refused because the OPTIONS call is Status 404

There’s no confusion to be had, except by the confused. An API endpoint is down.

Do not engage: ask for immediate escalation to a tier that won’t waste your time and can affect change. And: where they earned their engineering degree if they are calling themselves a professional engineer.

GET https://api.openai.com/v1/dashboard/chat/completions_metadata
Script Referrer Policy: strict-origin-when-cross-origin

Request headers

GET /v1/dashboard/chat/completions_metadata undefined
Host: api.openai.com
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:147.0) Gecko/20100101 Firefox/147.0
Accept: */*
Accept-Language: en-US,en;q=0.9
Accept-Encoding: gzip, deflate, br, zstd
Referer: https://platform.openai.com/
Authorization: Bearer sess-r...
openai-organization: org-...
OpenAI-Project: proj_...
Origin: https://platform.openai.com
Connection: keep-alive
Sec-Fetch-Dest: empty
Sec-Fetch-Mode: cors
Sec-Fetch-Site: same-site

Response: Blocked


Request headers - CORS

OPTIONS /v1/dashboard/chat/completions_metadata HTTP/3
Host: api.openai.com
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:147.0) Gecko/20100101 Firefox/147.0
Accept: */*
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate, br, zstd
Access-Control-Request-Method: GET
Access-Control-Request-Headers: authorization,openai-organization,openai-project
Referer: https://platform.openai.com/
Origin: https://platform.openai.com
Connection: keep-alive
Sec-Fetch-Dest: empty
Sec-Fetch-Mode: cors
Sec-Fetch-Site: same-site
Priority: u=4
Pragma: no-cache
Cache-Control: no-cache
TE: trailers

Server Response: Status 404

  • only transport and generic headers
HTTP/3 404 
date: Wed, 04 Feb 2026 15:58:04 GMT
cf-cache-status: DYNAMIC
priority: u=4,i=?0
set-cookie: __...; path=/; expires=Wed, 04-Feb-26 16:28:04 GMT; domain=.api.openai.com; HttpOnly; Secure; SameSite=None
strict-transport-security: max-age=31536000; includeSubDomains; preload
x-content-type-options: nosniff
set-cookie: _cfuvid=...; path=/; domain=.api.openai.com; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 9c8b5e0b7d6aef1c-XXX
alt-svc: h3=":443"; ma=86400

This endpoint and “logs” platform site UI is of no consequence to me, because I do not store user data with retention intention or expectation.

I appreciate your effort. The issue appears to have been resolved.

Have you recently changed anything in your account settings? e.g. passed verification or smth else

Hey Everyone, We worked with our engineering team and this issue should now be fixed. Please let us know, if its otherwise. Thank yoU!

4 Likes

I can confirm it has been resolved for me.

1 Like