Timestamp sorting in a search, is not sorting on milliseconds

Hi

We have a search, which is sorted default by @timestamp. But is it not sorted correctly, on the milliseconds level. Here are the lines from the search.

Jan 29, 2025 @ 16:34:36.040	dokument-lager-service-spring	ERROR	IllegalStateException	No service-name for service-token	77f09979d9d490251d8d60efc53243a3	APM	Access logs
Jan 29, 2025 @ 16:34:36.094	straffe-dirigent-spring	ERROR	WebClientResponseException$InternalServerError	500 Internal Server Error from POST http://dokument-lager-service/dokumenter/e377cf8a-f19c-4eea-b4ff-a82b2bc27f9f/tagEjerskab	77f09979d9d490251d8d60efc53243a3	APM	Access logs
Jan 29, 2025 @ 16:34:36.103	straffe-dirigent-spring	ERROR	WebClientResponseException$InternalServerError	500 Internal Server Error from POST http://dokument-lager-service/dokumenter/e377cf8a-f19c-4eea-b4ff-a82b2bc27f9f/tagEjerskab	77f09979d9d490251d8d60efc53243a3	APM	Access logs
Jan 29, 2025 @ 16:34:36.041	dokument-lager-service-spring	ERROR	IllegalStateException	No service-name for service-token	77f09979d9d490251d8d60efc53243a3	APM	Access logs

Any idea why, or what I can do?

Thanks for reaching out, @Casper_Thrane. What is the current mapping of your @timestamp field? I had something similar happen when I accidentally used a string field.