# EOS Session Timeouts 

**URL:** <https://forums.unrealengine.com/t/eos-session-timeouts/2858302>\
**Category:** Multiplayer\
**Tags:** epic-online-services, question\
**Created:** [May 16, 2025, 10:24pm UTC](https://forums.unrealengine.com/t/eos-session-timeouts/2858302 "2025-05-16T22:24:42Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![anonymous-edc](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous-edc](https://forums.unrealengine.com/u/anonymous-edc)\
**Post date:** [May 16, 2025, 10:24pm UTC](https://forums.unrealengine.com/t/eos-session-timeouts/2858302/1 "2025-05-16T22:24:42Z")

</div>

Hello,

We are seeing many intermittent timeouts when creating EOS sessions. This seems to have started recently, in the last couple days or so. Here is some log output demonstrating the problem:

```auto
	Line 2703: [2025.05.16-22.05.10:944][479]MWEOSSDK: Warning: [LogHttp] 0000023E073DD670: request has been successfully processed. URL: https://api.epicgames.dev/matchmaking/v1/b442539545c146b9afd73bf479f792da/sessions, HTTP code: 503, content length: 75, actual payload size: 75, elapsed: 4.09s
	Line 2704: [2025.05.16-22.05.10:944][479]MWEOSSDK: Warning: [LogHttp] 0000023E073DD670 Response Header Date: Fri, 16 May 2025 22:05:10 GMT
	Line 2705: [2025.05.16-22.05.10:944][479]MWEOSSDK: Warning: [LogHttp] 0000023E073DD670 Response Header Content-Type: application/json
	Line 2706: [2025.05.16-22.05.10:944][479]MWEOSSDK: Warning: [LogHttp] 0000023E073DD670 Response Header Content-Length: 75
	Line 2707: [2025.05.16-22.05.10:944][479]MWEOSSDK: Warning: [LogHttp] 0000023E073DD670 Response Header Connection: keep-alive
	Line 2708: [2025.05.16-22.05.10:944][479]MWEOSSDK: Warning: [LogHttp] 0000023E073DD670 Response Header X-Epic-Correlation-Id: EOS-wLAmYtxofku9mGvtePFQCg-U3Q9QUhy4EaFYEC1dtwdoA
	Line 2709: [2025.05.16-22.05.10:944][479]MWEOSSDK: Warning: [LogHttp] 0000023E073DD670 Response Header X-Epic-Error-Name: errors.com.epicgames.common.ask_timed_out
	Line 2710: [2025.05.16-22.05.10:945][479]MWEOSSDK: Warning: [LogHttp] 0000023E073DD670 Response Header Server: eos-gateway
	Line 2711: [2025.05.16-22.05.10:945][479]MWEOSSDK: Warning: [LogHttp] Lockout of 2.334666s on https://api.epicgames.dev/matchmaking/v1/b442539545c146b9afd73bf479f792da/sessions
	Line 2728: [2025.05.16-22.05.13:294][622]MWEOSSDK: Warning: [LogHttp] Retry 1 on https://api.epicgames.dev/matchmaking/v1/b442539545c146b9afd73bf479f792da/sessions
	Line 2731: [2025.05.16-22.05.17:398][878]MWEOSSDK: Warning: [LogHttp] 0000023E073DD670: request has been successfully processed. URL: https://api.epicgames.dev/matchmaking/v1/b442539545c146b9afd73bf479f792da/sessions, HTTP code: 503, content length: 75, actual payload size: 75, elapsed: 4.09s
	Line 2732: [2025.05.16-22.05.17:398][878]MWEOSSDK: Warning: [LogHttp] 0000023E073DD670 Response Header Date: Fri, 16 May 2025 22:05:17 GMT
	Line 2733: [2025.05.16-22.05.17:398][878]MWEOSSDK: Warning: [LogHttp] 0000023E073DD670 Response Header Content-Type: application/json
	Line 2734: [2025.05.16-22.05.17:398][878]MWEOSSDK: Warning: [LogHttp] 0000023E073DD670 Response Header Content-Length: 75
	Line 2735: [2025.05.16-22.05.17:399][878]MWEOSSDK: Warning: [LogHttp] 0000023E073DD670 Response Header Connection: keep-alive
	Line 2736: [2025.05.16-22.05.17:399][878]MWEOSSDK: Warning: [LogHttp] 0000023E073DD670 Response Header X-Epic-Correlation-Id: EOS-wLAmYtxofku9mGvtePFQCg-U3Q9QUhy4EaFYEC1dtwdoA
	Line 2737: [2025.05.16-22.05.17:399][878]MWEOSSDK: Warning: [LogHttp] 0000023E073DD670 Response Header X-Epic-Error-Name: errors.com.epicgames.common.ask_timed_out
	Line 2738: [2025.05.16-22.05.17:399][878]MWEOSSDK: Warning: [LogHttp] 0000023E073DD670 Response Header Server: eos-gateway
	Line 2739: [2025.05.16-22.05.17:399][878]MWEOSSDK: Warning: [LogHttp] Lockout of 5.367962s on https://api.epicgames.dev/matchmaking/v1/b442539545c146b9afd73bf479f792da/sessions
	Line 2861: [2025.05.16-22.05.22:773][196]MWEOSSDK: Warning: [LogHttp] Retry 2 on https://api.epicgames.dev/matchmaking/v1/b442539545c146b9afd73bf479f792da/sessions
	Line 2902: [2025.05.16-22.05.27:029][340]MWEOSSDK: Warning: [LogHttp] 0000023E073DD670: request has been successfully processed. URL: https://api.epicgames.dev/matchmaking/v1/b442539545c146b9afd73bf479f792da/sessions, HTTP code: 503, content length: 75, actual payload size: 75, elapsed: 4.08s
	Line 2903: [2025.05.16-22.05.27:029][340]MWEOSSDK: Warning: [LogHttp] 0000023E073DD670 Response Header Date: Fri, 16 May 2025 22:05:26 GMT
	Line 2904: [2025.05.16-22.05.27:029][340]MWEOSSDK: Warning: [LogHttp] 0000023E073DD670 Response Header Content-Type: application/json
	Line 2905: [2025.05.16-22.05.27:029][340]MWEOSSDK: Warning: [LogHttp] 0000023E073DD670 Response Header Content-Length: 75
	Line 2906: [2025.05.16-22.05.27:029][340]MWEOSSDK: Warning: [LogHttp] 0000023E073DD670 Response Header Connection: keep-alive
	Line 2907: [2025.05.16-22.05.27:029][340]MWEOSSDK: Warning: [LogHttp] 0000023E073DD670 Response Header X-Epic-Correlation-Id: EOS-wLAmYtxofku9mGvtePFQCg-U3Q9QUhy4EaFYEC1dtwdoA
	Line 2908: [2025.05.16-22.05.27:029][340]MWEOSSDK: Warning: [LogHttp] 0000023E073DD670 Response Header X-Epic-Error-Name: errors.com.epicgames.common.ask_timed_out
	Line 2909: [2025.05.16-22.05.27:030][340]MWEOSSDK: Warning: [LogHttp] 0000023E073DD670 Response Header Server: eos-gateway
	Line 2910: [2025.05.16-22.05.27:030][340]MWEOSSDK: Warning: [LogHttp] Lockout of 13.110020s on https://api.epicgames.dev/matchmaking/v1/b442539545c146b9afd73bf479f792da/sessions
	Line 3000: [2025.05.16-22.05.40:316][577]MWEOSSDK: Warning: [LogHttp] Retry 3 on https://api.epicgames.dev/matchmaking/v1/b442539545c146b9afd73bf479f792da/sessions
	Line 3001: [2025.05.16-22.05.40:497][578]MWEOSSDK: Warning: [LogHttp] Success on https://api.epicgames.dev/matchmaking/v1/b442539545c146b9afd73bf479f792da/sessions

```

In this case, the request finally succeeds on the 3rd retry, however, many requests are also failing after a 4th retry.

I noticed there was an incident reported on May 12 related to exactly this (503 errors on the matchmaking service) on [https://status.epicgames.com/](https://status.epicgames.com/). However, the status page says this problem has been resolved.

Is there anything we can do to help resolve this problem?

Thank you

---

<div class="post-metadata">

**Author:** ![anonymous-edc](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous-edc](https://forums.unrealengine.com/u/anonymous-edc)\
**Post date:** [May 19, 2025, 4:31pm UTC](https://forums.unrealengine.com/t/eos-session-timeouts/2858302/2 "2025-05-19T16:31:24Z")

</div>

I don’t have an answer, but want to second that we’ve been getting reports from our players with the same issue. When we take a look at their logs, we see similar logs:

```auto
[2025.05.18-03.11.34:838][812]LogRedpointEOS: Warning: [LogHttp] 000001E8E1A05D40: request has been successfully processed. URL: https://api.epicgames.dev/matchmaking/v1/51e195da3fa44b008fdf02e650aebded/sessions, HTTP code: 503, content length: 75, actual payload size: 75, elapsed: 4.06s
[2025.05.18-03.11.34:839][812]LogRedpointEOS: Warning: [LogHttp] 000001E8E1A05D40 Response Header Date: Sun, 18 May 2025 03:11:34 GMT
[2025.05.18-03.11.34:839][812]LogRedpointEOS: Warning: [LogHttp] 000001E8E1A05D40 Response Header Content-Type: application/json
[2025.05.18-03.11.34:839][812]LogRedpointEOS: Warning: [LogHttp] 000001E8E1A05D40 Response Header Content-Length: 75
[2025.05.18-03.11.34:839][812]LogRedpointEOS: Warning: [LogHttp] 000001E8E1A05D40 Response Header Connection: keep-alive
[2025.05.18-03.11.34:839][812]LogRedpointEOS: Warning: [LogHttp] 000001E8E1A05D40 Response Header X-Epic-Correlation-Id: EOS-tv9oC9KhxEq23PntfrOwcA-y1XG1CVk80C4Oew0_HqgPQ
[2025.05.18-03.11.34:839][812]LogRedpointEOS: Warning: [LogHttp] 000001E8E1A05D40 Response Header X-Epic-Error-Name: errors.com.epicgames.common.ask_timed_out
[2025.05.18-03.11.34:839][812]LogRedpointEOS: Warning: [LogHttp] 000001E8E1A05D40 Response Header Server: eos-gateway
[2025.05.18-03.11.34:839][812]LogRedpointEOS: Warning: [LogHttp] Success on https://api.epicgames.dev/matchmaking/v1/51e195da3fa44b008fdf02e650aebded/sessions
[2025.05.18-03.11.34:841][812]LogRedpointEOS: Warning: [LogEOS] Error response received from backend. ServiceName=[Sessions], OperationName=[CreateSession], Url=[<Redacted>], HttpStatus=[503], ErrorCode=[errors.com.epicgames.common.ask_timed_out], NumericErrorCode=[UNSET], ErrorMessage=[], CorrId=[EOS-tv9oC9KhxEq23PntfrOwcA-y1XG1CVk80C4Oew0_HqgPQ]

```

In this case we’re using Redpoint EOS plugin, but the errors seem to be originating from EOS itself.

---

<div class="post-metadata">

**Author:** ![SebBergy2.0](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/sebbergy2.0/32/1214708_2.png) [@SebBergy2.0](https://forums.unrealengine.com/u/SebBergy2.0)\
**Post date:** [May 20, 2025, 7:41pm UTC](https://forums.unrealengine.com/t/eos-session-timeouts/2858302/3 "2025-05-20T19:41:18Z")

</div>

We also had issues from the 16th to the 19th. We’re confirming the times and will update the status page to show the disruption. We’re working on fixing this issue permanently.

---

<div class="post-metadata">

**Author:** ![SebBergy2.0](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/sebbergy2.0/32/1214708_2.png) [@SebBergy2.0](https://forums.unrealengine.com/u/SebBergy2.0)\
**Post date:** [May 21, 2025, 12:15pm UTC](https://forums.unrealengine.com/t/eos-session-timeouts/2858302/4 "2025-05-21T12:15:27Z")

</div>

When the backend gets into this state, the 5xx failure rate is still quite low. Your game could handle the EOS\_TimedOut error returned by CreateSessions, wait a few seconds, and retry. Creating the session should work after a few attempts. This said, our backend team is working on a permanent solution so this doesn’t happen in the future.

---

<div class="post-metadata">

**Author:** ![anonymous-edc](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous-edc](https://forums.unrealengine.com/u/anonymous-edc)\
**Post date:** [May 20, 2025, 11:47pm UTC](https://forums.unrealengine.com/t/eos-session-timeouts/2858302/5 "2025-05-20T23:47:58Z")

</div>

Thank you for the confirmation, I was worried it was a configuration on our end. In the meantime, if this were to happen again do you recommend any actions devs can take to help mitigate?
