// AI Platform Drift
Cloudflare AI Gateway log and request IDs changed to UUIDv7 format
Cloudflare developer changelog · published 2026-10-26 18:44 UTC
WHAT CHANGEDEffective 8 October 2026, AI Gateway log IDs and request IDs switched from 26-character ULIDs to lowercase UUIDv7 format (e.g., 019a7b3e-5f2c-7c41-9d3e-2b8f6a1c4e07). For single-step requests, cf-aig-request-id, cf-aig-log-id, and cf-aig-event-id response headers now return the same value. Existing log IDs retain their original format and the logs API accepts both.
WHY IT MATTERSCode that validates log ID format against the 26-character ULID pattern will reject new IDs and break logging, monitoring, or correlation logic. Response header parsing that assumes distinct values across the three ID headers will misinterpret single-step requests.
WHAT TO DOSearch your codebase for ULID format validation (26-character alphanumeric checks) applied to cf-aig-log-id, cf-aig-request-id, or cf-aig-event-id headers or log API responses. Replace format checks with opaque string handling or add UUIDv7 pattern support.
ACT-BY DATE PASSED — this item's act-by date, 2026-10-08, is before this page was generated 2026-11-21 (UTC). Check the primary source before acting on it.
Model-reported confidence 95% (not measured accuracy)
Primary source ↗
written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## AI Gateway - AI Gateway log IDs and request IDs now use UUIDv7 +https://developers.cloudflare.com/changelog/post/2026-10-08-uuidv7-log-ids/ +Thu, 08 Oct 2026 00:00:00 GMT + +New AI Gateway log IDs and request IDs are lowercase UUIDv7, such as 019a7b3e-5f2c-7c41-9d3e-2b8f6a1c4e07. Previously, log IDs were 26-character ULIDs and request IDs were random UUIDs. +For a request that AI Gateway answers in a single step, the cf-aig-request-id, cf-aig-log-id, and cf-aig-event-id response headers now carry the same value. For provider and Universal requests, if you set your own cf-aig-event-id, AI Gateway returns it instead. +Existing log IDs do not change, and the logs API accepts both formats. Treat log IDs as opaque strings, and update any code that checks for the ULID format.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
| triage verdict | MATERIAL at 0.85, needed 0.5 |
|---|---|
| triage reasoning | Log ID format change requires code updates; existing integrations checking ULID format will break. |
| signals | breaking change to log ID format (ULID → UUIDv7) · breaking change to request ID format · explicit instruction to update code that validates format · API contract change (response header values) · future date (2026-10-08) marking effective change |
| suppression | — |
| triage model | anthropic/claude-haiku-4.5 ($0.00000) |
| writer model | anthropic/claude-sonnet-4.5 ($0.00000) |