The expires_at value is not in UTC

API Bugs
,
1

We try to create session to use the Realtime API with WebRTC.
We followed the following process to call the API to initialize the session:
https://platform.openai.com/docs/guides/realtime-webrtc#creating-an-ephemeral-token
We noticed that the answer body has a client_secret property such like this:

"client_secret": {
    "value": "ek_abc123", 
    "expires_at": 1234567890
  }

The expires_at property is a timestamp in seconds.
I compared it to a current date in UTC and I noticed that the difference is more than two hours (my timezone is UTC+1). Normally, the toekn expires in one minute. So why is the expires_at delta with UTC in more than two hours ? It the expires_at is not in UTC. The timezone should be given.