We're experiencing a sudden, widespread auth failu...
# ory-network
t
We're experiencing a sudden, widespread auth failure across all environments (prod and dev) that started around 2026-02-13T15:43 UTC. The issue is affecting all users, including fresh sessions from incognito windows. Symptom: All calls to the
ToSession
(
GET /sessions/whoami
) endpoint via the Go SDK (
github.com/ory/client-go
) are failing with
"undefined response type"
. This error originates from the SDK's response decoder, which expects a
Content-Type
matching
application/json
or
application/xml
. When the Content-Type doesn't match, the SDK can't parse the response and throws this error. What we believe is happening: Something changed on the Ory Network side that altered the
Content-Type
header (or other response characteristics) returned by the
/sessions/whoami
endpoint. This is breaking the SDK's response parsing for both success (200) and error (401) responses. What we've ruled out: Not an expired session issue — happens on brand new sessions in incognito • Not an SDK version issue — happening on both
v1.22.16
and
v1.22.23
simultaneously • Not a code change on our side — prod (unchanged code) and dev broke at the same time We're deploying additional debug logging to capture the full response details (status code, headers, body, Content-Type) and can share those shortly. In the meantime, can you check if there were any infrastructure or API changes around that time that could have affected response headers on the
/sessions/whoami
endpoint?
Seems to be intermittent. We've observed it working, failing, working, failing and now working again - across 2 envs with separate Ory projects.
b
Hi, can you DM me the details (slug or project ID) here or (preferably) create a support ticket on console.ory.sh/support? Thank you!
b
Happening to us too
FYI @thankful-shoe-14315 https://status.ory.com/
🙌 1
@thankful-shoe-14315 Turning off the Cloudflare DNS proxy resolved it for me (temporarily)
t
I turned off too, but tough to know if that was the issue yet. Even with it enabled, calls to
/sessions/whoami
have been succeeding.
b
Not on me end unfortunately
l
I just went through this issue and am using Cloudflare too. My working theory is that this is related to routing in Ory and caching in Cloudflare with respect to pagination. Near as I can tell, if your request includes pagination, the request takes one route. Without pagination it takes another. The only change I made was adding pagination, and all session queries that had worked broke. I removed pagination, and all queries for general users worked again. I have not tested admins except through the Ory console, but I suspect that that the admin API now requires pagination for security.
b
@lemon-painter-27431, thanks for the description. We're still investigating, but overall the issue mentioned in this thread seems to be limited to the
/sessions/whoami
endpoint and is caused by some internal routing issues. There should be no pagination involved here, so from your description this issue seems like something else. Could you raise this issue via console.ory.sh/support?
l
@Jonas, will do.