March 25, 2026
Advanced Integrated Visibility Timestamp Standardization
Advanced Integrated Visibility (AIV) webhook events that don't include a time component now use a standardized timestamp of 00:00:00+00:00 (UTC). Previously, these events defaulted to 23:59:59 with a non-UTC offset.
No downtime is expected. All AIV webhook services remain fully available and operational throughout the release.
Overview
This release standardizes how timestamps are populated when the time component is missing in AIV webhook event payloads.
What to Expect
- For a subset of webhook events without a time component, timestamps now return as 00:00:00+00:00.
- Events that previously resulted in future timestamps due to offset handling will be corrected.
- No additional webhook events will be generated.
- Event sequencing and counts remain unchanged.
- Only the time component of affected timestamps is modified.
Updated Fields
The following fields are updated only when the incoming payload does not include a time component (applies to all lifecycle timestamp types):
- scanEvent.eventCreateTime
- scanEvent.previousEvents[].eventCreateTime
- dateAndTimes[].dateTime.dateTimeRange
Timestamp Behavior
Event Create Time (Message / Scan Events)
Previous: 23:59:59 with non-UTC offset (e.g., +07:00)
Updated: 00:00:00+00:00 (UTC)
Examples
Delivered Event (DL)
Previous: "eventCreateTime": "2026-03-17T23:59:59+07:00"
Updated: "eventCreateTime": "2026-03-17T00:00:00+00:00"
Previous Events Array
Previous:
"previousEvents": [
{
"eventCreateTime": "2026-03-17T23:59:59+07:00"
}
]
Updated:
"previousEvents": [
{
"eventCreateTime": "2026-03-17T00:00:00+00:00"
}
]
dateAndTimes Array
Previous:
"dateAndTimes": [
{
"dateAndTime": {
"dateTimeRange": {
"begins": "2026-03-17T23:59:59+07:00"
}
}
}
]
Updated:
"dateAndTimes": [
{
"dateAndTime": {
"dateTimeRange": {
"begins": "2026-03-17T00:00:00+00:00"
}
}
}
]
