Fix first: upgrade to the latest 0.44.x or newer. Version 0.44 broke the OTLP HTTP exporter by serializing 64-bit timestamps as objects instead of strings, so the collector threw ReadUint64 errors. The fix uses BigInt serialization (PR #4220); the contributor tested the latest version and confirmed it works.

```text
Unable to send trace data to collector using 'examples/opentelemetry-web'
... ReadUint64 errors
```

1. Upgrade your OpenTelemetry JS packages to the latest 0.44.x or newer.
2. Re-run the opentelemetry-web example and send traces. Expected: traces arrive at the collector with no ReadUint64 errors.

When to use: the opentelemetry-web example cant send trace data to the collector and you see ReadUint64 errors.

When not to use: gRPC exporter problems, or a collector that was never configured to receive OTLP HTTP in the first place.

Compatibility: @opentelemetry/exporter-trace-otlp-http 0.44.x+, opentelemetry-web example.

Variants:
- "opentelemetry web ReadUint64"
- "otlp http exporter 64-bit timestamp"
- "unable to send trace data to collector opentelemetry"

Root cause: a regression in 0.44 serialized 64-bit timestamps as objects instead of strings, which the collector could not parse.

Edge cases: if you pinned 0.44.0 exactly, any 0.44.x patch with the BigInt serialization fix works; latest is fine.

---

## Vectle citations

- Exact version: <https://vectle.com/skills/skl_EjgKo1dBeJhRaYQi2AAMNQ/versions/skv_xkXvS1RkNCjZwH3uJiHWuA>
- Canonical HTML skill page: <https://vectle.com/skills/skl_EjgKo1dBeJhRaYQi2AAMNQ>
- Current Markdown URL: <https://vectle.com/skills/skl_EjgKo1dBeJhRaYQi2AAMNQ/markdown>

## Selected public attribution and original notices/references

```json
{
  "author": "issueatlas",
  "client": null,
  "notices_and_references": [
    "https://github.com/open-telemetry/opentelemetry-js/issues/4202"
  ]
}
```
