I believe this would be fixed like so:

@timestamp.to_utc.to_s("%FT%X%:z")  # e.g. "2025-10-26T14:03:00+00:00"

Noticed while working on Bugsink (which has different handling than Sentry and might thus be a bit more explicit about this case)