OpenTelemetry & AWS SigV4 Timestamp Converter

Q: What is the AWS SigV4 timestamp format?

**`YYYYMMDDTHHMMSSZ`** — basic ISO 8601 UTC, e.g. `20260813T143000Z`. Used in `X-Amz-Date` and the credential scope date.

Q: What timestamp does OpenTelemetry use?

Span times are **Unix nanoseconds** (int64) in OTLP; log records and attributes commonly use **RFC 3339 with nanoseconds** (`2026-08-13T14:30:00.123456789Z`).

Q: What is performance.now() time?

Milliseconds since the **page navigation origin**, not epoch — it resets per page load. The converter shows the epoch-ms equivalent for a wall-clock instant.

Q: What are Chrome network timestamps?

`Network.requestWillBeSent.timestamp` is **µs since the navigation start**, comparable to `performance.timeOrigin` — the converter renders the wall-clock mapping.

Observability and cloud tooling use specific timestamp forms: OpenTelemetry (RFC 3339 nano for OTLP, epoch ns for span times), AWS SigV4 (`20260813T143000Z` in signatures), browser performance (epoch ms since navigation), and Chrome network events (µs since origin).

This converter renders your date-time in each representation for building signed requests, OTLP payloads and performance tooling.

Timezone:

Enter a date-time above to see the conversion results.

OpenTelemetry & AWS SigV4 Timestamp Converter Quick Reference

Format	Pattern / Description	Example 1	Example 2
OpenTelemetry Nanos	Nanoseconds string	1786631400000000000	1767225600000000000
AWS SigV4 Date	YYYYMMDDTHHMMSSZ	20260813T143000Z	20260101T000000Z
Browser Performance	High Res Timestamp	52200000.000	0.000
Chrome Network	DevTools	13431105000000000	13411699200000000

* Examples are rendered in UTC for the fixed sample instants above.

When to Use OpenTelemetry & AWS SigV4 Timestamp

AWS API signing

Generate the `X-Amz-Date` header value (`YYYYMMDDTHHMMSSZ`) for SigV4 requests and debug signature mismatches.

OTLP/OpenTelemetry payloads

Build span start/end times as epoch nanos for OTLP export, and RFC 3339 for resource attributes.

Performance analysis

Convert Chrome DevTools network timestamps (µs) and `performance.now()` values to wall-clock.

Frequently Asked Questions

What is the AWS SigV4 timestamp format?

`YYYYMMDDTHHMMSSZ` — basic ISO 8601 UTC, e.g. `20260813T143000Z`. Used in `X-Amz-Date` and the credential scope date.

What timestamp does OpenTelemetry use?

Span times are Unix nanoseconds (int64) in OTLP; log records and attributes commonly use RFC 3339 with nanoseconds (`2026-08-13T14:30:00.123456789Z`).

What is performance.now() time?

Milliseconds since the page navigation origin, not epoch — it resets per page load. The converter shows the epoch-ms equivalent for a wall-clock instant.

What are Chrome network timestamps?

`Network.requestWillBeSent.timestamp` is µs since the navigation start, comparable to `performance.timeOrigin` — the converter renders the wall-clock mapping.

Related Time Format Converters

UTC Time Converter (Coordinated Universal Time)

Convert any local time to UTC (Coordinated Universal Time) instantly. See the UTC string, Z-suffixed ISO form and GMT equivalent. Free UTC converter.

RFC 3339 Date-Time Converter

Convert any date to RFC 3339 format (2026-08-13T14:30:00Z or +00:00 offset). The timestamp standard for JSON APIs and cloud services. Free converter.

JSON & Protobuf Timestamp Converter

Convert dates to serialization formats: JSON string, Protobuf Timestamp (seconds/nanos since epoch), BSON and XML Schema dateTime. Free converter.

All Format Guides

Unix Timestamp ISO 8601 ISO Week Date ISO Ordinal Date Military Time Decimal Time RFC 2822 RFC 3339 SQL Datetime Julian Date HTTP Date Excel Serial Date GPS Time UTC Time Cron Expression

Browse all 50 format guides →

Need to Convert Between All Formats?

Use the main Time Format Converter for instant conversion across 100+ formats — epoch, ISO 8601, RFC 3339, SQL datetime, military time and more in one click.

Open Time Format Converter