# AI Gateway - AI Gateway log IDs and request IDs now use UUIDv7

Category: agent-infrastructure
Published: 2026-10-08T00:00:00.000Z
Source: [Cloudflare AI Gateway changelog](https://developers.cloudflare.com/changelog/post/2026-10-08-uuidv7-log-ids/)
Agent usefulness: 80/100
Confidence: 0.9
Content mode: source-watch
Verified: 2026-10-26T18:17:53.698Z
Tags: cloudflare, ai-gateway, changelog

## Human Summary
Cloudflare AI Gateway changelog published AI Gateway - AI Gateway log IDs and request IDs now use UUIDv7. 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…

## Agent Summary
Treat AI Gateway - AI Gateway log IDs and request IDs now use UUIDv7 as an official publication signal. Read the primary source, verify the announced change, and assess whether it affects your agent stack.

## Body
Cloudflare AI Gateway changelog published AI Gateway - AI Gateway log IDs and request IDs now use UUIDv7. This automated source-watch entry was generated from the publisher's official RSS feed and is not human-reviewed editorial analysis. Source excerpt: 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.

## Recommended actions
- Read the original Cloudflare AI Gateway changelog article before relying on this summary.
- Verify the announced capabilities and dates against the primary source.
- Assess whether the change affects your agent stack or evaluation plan.

## Sponsors
No sponsor placement attached.

## Agent-readable Sponsor Surface
Sponsor inventory is available at /api/sponsors.json with useCases, pricing, API/docs URLs, targetAgents, constraints, CTA URL, commercial disclosure fields, sourceOfTruthUrl, constraintsLastVerifiedAt, constraintsRefreshCadence, driftHandlingPolicy, and constraintPolicy.