Snapshot 21867
Normalized text
Scripts and page chrome removed; this is what change detection compares.
{
"pages": [
{
"end_time": "2026-09-30T23:59:59Z",
"months": [
{
"incidents": [
{
"code": "jxxlmt598pxf",
"impact": "minor",
"message": "This incident has been resolved.",
"name": "DC01 - Campaigns Dashboard is experiencing intermittent errors",
"timestamp": "Sep \u003cvar data-var='date'\u003e24\u003c/var\u003e, \u003cvar data-var='time'\u003e11:39\u003c/var\u003e - \u003cvar data-var='time'\u003e12:23\u003c/var\u003e UTC"
},
{
"code": "mh2k6y8dzqh4",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] DC 01 | Aux User-Profile Data Migration",
"timestamp": "Sep \u003cvar data-var='date'\u003e3\u003c/var\u003e, \u003cvar data-var='time'\u003e02:30\u003c/var\u003e - \u003cvar data-var='time'\u003e07:00\u003c/var\u003e UTC"
}
],
"name": "September",
"year": 2026
},
{
"incidents": [
{
"code": "m5g1wcztlbmb",
"impact": "major",
"message": "Summary\nBetween 2026-08-17 at 19:55 IST and 2026-08-18 at 12:00 IST, a subset of requests made to the Inform API may not have been delivered successfully. Affected requests received an HTTP 200 OK response, indicating success, but the corresponding messages were never sent.\nThe issue has been fully resolved as of 2026-08-18 at 12:00 IST.\n\nImpact\n\n- Customers using the Inform API routed through DC-03 during the affected window may have been impacted\n- Affected requests appeared successful on the client side but were not processed\n- As a result, messages associated with those requests were not delivered\n- We are unable to automatically retry or replay the affected requests\n\n\nWhat We Did\nWe identified the issue during a routine internal routing update and immediately rolled back the change. Full service was restored at 2026-08-18 at 12:00 IST.\n\nWhat You Should Do\nIf you believe your integration was affected during this window, we recommend:\n\n- Reviewing your logs for requests made between 2026-08-17 19:55 IST and 2026-08-18 12:00 IST\n- Identifying any messages that were not delivered as expected\n- Re-sending those requests manually if delivery is still required\n\n\nWe sincerely apologize for the inconvenience this may have caused. If you have any questions or need assistance identifying affected requests, please reach out to our support team.",
"name": "Dashboard 03 — Inform API: Some Messages Not Delivered During Routing Update",
"timestamp": "Aug \u003cvar data-var='date'\u003e17\u003c/var\u003e, \u003cvar data-var='time'\u003e14:30\u003c/var\u003e - \u003cvar data-var='time'\u003e14:30\u003c/var\u003e UTC"
}
],
"name": "August",
"year": 2026
},
{
"incidents": [
{
"code": "c11zqn2z56p2",
"impact": "major",
"message": "This incident has been resolved.",
"name": "Dashboard 01 - Degraded Performance Across Multiple Services",
"timestamp": "Jul \u003cvar data-var='date'\u003e27\u003c/var\u003e, \u003cvar data-var='time'\u003e10:07\u003c/var\u003e - \u003cvar data-var='time'\u003e14:47\u003c/var\u003e UTC"
},
{
"code": "lqy9s20hk5qm",
"impact": "major",
"message": "This incident has been resolved.",
"name": "DC01 - Degraded performance of Inform, Event Triggered Campaigns, Flows",
"timestamp": "Jul \u003cvar data-var='date'\u003e25\u003c/var\u003e, \u003cvar data-var='time'\u003e09:11\u003c/var\u003e - \u003cvar data-var='time'\u003e12:00\u003c/var\u003e UTC"
}
],
"name": "July",
"year": 2026
}
],
"start_time": "2026-07-01T00:00:00Z",
"time_zone": "UTC"
},
{
"end_time": "2026-06-30T23:59:59Z",
"months": [
{
"incidents": [
{
"code": "fl5qlqcb13s2",
"impact": "major",
"message": "Between 05:00 UTC and 08:35 UTC, the Branded Email Link Click Domain service in the DC-02 region experienced an extended period of performance degradation, followed by a brief period of unavailability.\n\nImpact:\n05:00 UTC – 08:00 UTC:\nThe service operated in a degraded state. Some users may have experienced delayed responses or intermittent timeouts when clicking branded email links for a limited number of affected brands.\n\n08:00 UTC – 08:35 UTC:\nThe service was unavailable while our engineering team performed recovery actions. Normal service was fully restored at 08:35 UTC.\n\nRoot Cause:\nThe degradation was caused by an unexpected and significant spike in request volume. This sudden increase in traffic placed excessive load on the backend database, resulting in slower query processing and degraded service performance.\n\nResolution:\nOur monitoring systems detected the degradation and alerted the engineering team. To restore stability and support the increased traffic volume, the team scaled the underlying database infrastructure and completed recovery procedures.\n\nAfter the infrastructure changes were completed, service availability and performance returned to normal at 08:35 UTC.\n\nCurrent Status\nThe issue has been resolved, and the Branded Email Link Click Domain service is operating normally in the DC-02 region.\n\nWe apologize for the disruption and any inconvenience this may have caused.",
"name": "Dashboard 02 - Degradation in Email Link Branding Service",
"timestamp": "Jun \u003cvar data-var='date'\u003e1\u003c/var\u003e, \u003cvar data-var='time'\u003e05:00\u003c/var\u003e - \u003cvar data-var='time'\u003e05:00\u003c/var\u003e UTC"
},
{
"code": "c106yrd91z68",
"impact": "major",
"message": "On June 1, 2026, we experienced a major incident that affected the processing of email delivery status events in two of our data centers; Dashboard 02 and 04.\n\nDuring this incident, some delivery-related events — including delivered, bounce, and spam status updates — were not processed correctly. As a result, customers may have seen incomplete or under-reported delivery statistics in dashboards and reports for campaigns sent during the affected period.\n\nWe want to emphasize that actual email sending and delivery to recipients were not impacted. The issue was limited to the reporting and processing of delivery status events.\n\nThe incident was triggered by a recent internal system update that changed how delivery events are grouped and processed. In some environments, this caused certain event batches to fail processing. Our monitoring did not alert us as quickly as expected, which delayed detection and response. We sincerely apologize for the impact this had on your visibility into campaign performance and for the delay in identifying the issue.\n\nOur teams have taken corrective action to resolve the issue and are reviewing the affected data. We are also strengthening our monitoring, validation, and release safeguards to help prevent similar incidents in the future.\n\nWe understand how important accurate and timely delivery reporting is to your business, and we regret the disruption this caused. Thank you for your patience and understanding while we worked through this incident.",
"name": "Dashboard 02 and 04 - Email Delivery Reporting Impact",
"timestamp": "Jun \u003cvar data-var='date'\u003e1\u003c/var\u003e, \u003cvar data-var='time'\u003e04:00\u003c/var\u003e - \u003cvar data-var='time'\u003e04:00\u003c/var\u003e UTC"
}
],
"name": "June",
"year": 2026
},
{
"incidents": [
{
"code": "r6mj734q8yq7",
"impact": "minor",
"message": "The lag is cleared and latency is within our SLA threshold. \n\nThe team will take corrective actions as part of the incident post mortem.",
"name": "DC03 | Delay in data ingestion",
"timestamp": "May \u003cvar data-var='date'\u003e14\u003c/var\u003e, \u003cvar data-var='time'\u003e09:55\u003c/var\u003e - \u003cvar data-var='time'\u003e15:01\u003c/var\u003e UTC"
},
{
"code": "kjj4ktgggh4d",
"impact": "minor",
"message": "This incident has been resolved.",
"name": "DC04 | Delay in Data Processing",
"timestamp": "May \u003cvar data-var='date'\u003e13\u003c/var\u003e, \u003cvar data-var='time'\u003e22:02\u003c/var\u003e - May \u003cvar data-var='date'\u003e14\u003c/var\u003e, \u003cvar data-var='time'\u003e03:39\u003c/var\u003e UTC"
}
],
"name": "May",
"year": 2026
},
{
"incidents": [
{
"code": "2s5r074c4zgb",
"impact": "minor",
"message": "This incident has been resolved.",
"name": "[Dashboard-02] Delay in Campaign Sending",
"timestamp": "Apr \u003cvar data-var='date'\u003e24\u003c/var\u003e, \u003cvar data-var='time'\u003e04:35\u003c/var\u003e - \u003cvar data-var='time'\u003e05:27\u003c/var\u003e UTC"
},
{
"code": "strvvhm8sl1q",
"impact": "major",
"message": "This incident has been resolved.",
"name": "Dashboard 01 - Degraded Performance in Data Ingestion",
"timestamp": "Apr \u003cvar data-var='date'\u003e20\u003c/var\u003e, \u003cvar data-var='time'\u003e10:34\u003c/var\u003e - Apr \u003cvar data-var='date'\u003e21\u003c/var\u003e, \u003cvar data-var='time'\u003e01:45\u003c/var\u003e UTC"
},
{
"code": "gqcdpzh981ld",
"impact": "none",
"message": "There was a degradation identified on DC03 Data Ingestion pipeline since 9th Apr, 10:30 AM IST. This was due to an infra/instance type change which was deployed. This change seemed to be unstable and hence has been reverted now. It resulted in degraded data processing throughput resulting in lag.\n\nDuration of the incident: 10:30am IST - 01:45pm IST (~3.15 hours)\n\nImpact:\nThe delay in data processing has impact on availability of user updates and events in segmentation. it also had an impact on Event triggered campaigns and flows due to the delay.\n\nResolution:\nThe lag has been recovered as of 01:45pm IST. There is no data loss. \n\nTeam is currently monitoring the systems and doing a deeper post-mortem to avoid such occurrence in future.",
"name": "DC03 | Lag in data ingestion",
"timestamp": "Apr \u003cvar data-var='date'\u003e9\u003c/var\u003e, \u003cvar data-var='time'\u003e08:39\u003c/var\u003e - \u003cvar data-var='time'\u003e08:39\u003c/var\u003e UTC"
}
],
"name": "April",
"year": 2026
}
],
"start_time": "2026-04-01T00:00:00Z",
"time_zone": "UTC"
},
{
"end_time": "2026-03-31T23:59:59Z",
"months": [
{
"incidents": [
{
"code": "2y7l34v8z3j7",
"impact": "minor",
"message": "This incident has been resolved. The lag was observed from 06:45 UTC (12:15pm IST) to 11:30 UTC (05:00pm IST).",
"name": "Dashboard 03 – Degraded Performance in Trigger-Based Flows",
"timestamp": "Mar \u003cvar data-var='date'\u003e31\u003c/var\u003e, \u003cvar data-var='time'\u003e11:11\u003c/var\u003e - \u003cvar data-var='time'\u003e11:41\u003c/var\u003e UTC"
},
{
"code": "jmjlrj7615jc",
"impact": "minor",
"message": "The issue is resolved as of now and ingestion pipeline latency seems stable. However, the technical team is root causing the issue to deploy a permanent fix. \n\nThis data ingestion delay had an impact on Smart trigger campaigns and Flows, as it consumes the data from the ingestion pipeline and apply trigger/flows conditions. \n\nDelay of around 45 min lasted between 24-March 13:00 UTC to 15:40 UTC.\nThere were delay observed later as well on 24-March 20:30 UTC to 21:30 UTC.",
"name": "[Dashboard-03] Delay in Ingestion Pipeline",
"timestamp": "Mar \u003cvar data-var='date'\u003e24\u003c/var\u003e, \u003cvar data-var='time'\u003e14:47\u003c/var\u003e - \u003cvar data-var='time'\u003e15:54\u003c/var\u003e UTC"
},
{
"code": "5rtvhbnrqq2h",
"impact": "minor",
"message": "This incident has been resolved.",
"name": "Dashboard-03 Service Impact -Smart Trigger and Flow Campaigns",
"timestamp": "Mar \u003cvar data-var='date'\u003e13\u003c/var\u003e, \u003cvar data-var='time'\u003e02:12\u003c/var\u003e - \u003cvar data-var='time'\u003e05:16\u003c/var\u003e UTC"
},
{
"code": "jf0b05554wvt",
"impact": "none",
"message": "This incident has been resolved.",
"name": "Dc03 | Data ingestion lag | Event processing",
"timestamp": "Mar \u003cvar data-var='date'\u003e12\u003c/var\u003e, \u003cvar data-var='time'\u003e17:05\u003c/var\u003e - \u003cvar data-var='time'\u003e19:18\u003c/var\u003e UTC"
},
{
"code": "vkhldqkqfst3",
"impact": "minor",
"message": "The incident has been resolved. The issue lasted for 30 min from 10:35 to 11:05 UTC.",
"name": "[Dashboard-02] All Campaigns Page not loading",
"timestamp": "Mar \u003cvar data-var='date'\u003e6\u003c/var\u003e, \u003cvar data-var='time'\u003e10:56\u003c/var\u003e - \u003cvar data-var='time'\u003e11:06\u003c/var\u003e UTC"
},
{
"code": "4flt87k3d3sj",
"impact": "minor",
"message": "This incident has been resolved.",
"name": "Dashboard 03 - Delay in Stats update",
"timestamp": "Mar \u003cvar data-var='date'\u003e5\u003c/var\u003e, \u003cvar data-var='time'\u003e15:28\u003c/var\u003e - \u003cvar data-var='time'\u003e17:15\u003c/var\u003e UTC"
}
],
"name": "March",
"year": 2026
},
{
"incidents": [
{
"code": "x6y96mr8jycb",
"impact": "major",
"message": "This incident has been resolved.",
"name": "[Dashboard-03] Dashboard not loading",
"timestamp": "Feb \u003cvar data-var='date'\u003e25\u003c/var\u003e, \u003cvar data-var='time'\u003e12:05\u003c/var\u003e - \u003cvar data-var='time'\u003e12:18\u003c/var\u003e UTC"
},
{
"code": "4t2pw41d71d9",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] DC01 - Scheduled Infrastructure Maintenance Notice: Resizing of Data Clusters",
"timestamp": "Feb \u003cvar data-var='date'\u003e19\u003c/var\u003e, \u003cvar data-var='time'\u003e18:22\u003c/var\u003e - \u003cvar data-var='time'\u003e20:30\u003c/var\u003e UTC"
},
{
"code": "pvfw6mvrc991",
"impact": "minor",
"message": "This incident has been resolved.",
"name": "[Dashboard-02] Delay in processing Data Imports \u0026 Exports",
"timestamp": "Feb \u003cvar data-var='date'\u003e11\u003c/var\u003e, \u003cvar data-var='time'\u003e16:12\u003c/var\u003e - \u003cvar data-var='time'\u003e17:50\u003c/var\u003e UTC"
},
{
"code": "n3j8yvwz0bfx",
"impact": "major",
"message": "This incident has been resolved.",
"name": "Service Outage",
"timestamp": "Feb \u003cvar data-var='date'\u003e10\u003c/var\u003e, \u003cvar data-var='time'\u003e22:10\u003c/var\u003e - Feb \u003cvar data-var='date'\u003e11\u003c/var\u003e, \u003cvar data-var='time'\u003e03:31\u003c/var\u003e UTC"
}
],
"name": "February",
"year": 2026
},
{
"incidents": [
{
"code": "yps1jsbwt9yf",
"impact": "minor",
"message": "This incident has been resolved.",
"name": "[DC-04] - Delay in File and Warehouse Processing",
"timestamp": "Jan \u003cvar data-var='date'\u003e14\u003c/var\u003e, \u003cvar data-var='time'\u003e17:45\u003c/var\u003e - \u003cvar data-var='time'\u003e17:53\u003c/var\u003e UTC"
},
{
"code": "3gb0357qy1qc",
"impact": "minor",
"message": "This incident has been resolved.",
"name": "Dashboard 03 - Delay in Stats update",
"timestamp": "Jan \u003cvar data-var='date'\u003e12\u003c/var\u003e, \u003cvar data-var='time'\u003e14:56\u003c/var\u003e - Jan \u003cvar data-var='date'\u003e14\u003c/var\u003e, \u003cvar data-var='time'\u003e01:15\u003c/var\u003e UTC"
}
],
"name": "January",
"year": 2026
}
],
"start_time": "2026-01-01T00:00:00Z",
"time_zone": "UTC"
},
{
"end_time": "2025-12-31T23:59:59Z",
"months": [
{
"incidents": [
{
"code": "fv5t5lvx2zgc",
"impact": "minor",
"message": "This incident has been resolved.",
"name": "Dashboard-03 : Degraded Performance in Stats Processing",
"timestamp": "Dec \u003cvar data-var='date'\u003e23\u003c/var\u003e, \u003cvar data-var='time'\u003e09:44\u003c/var\u003e - \u003cvar data-var='time'\u003e23:56\u003c/var\u003e UTC"
}
],
"name": "December",
"year": 2025
},
{
"incidents": [],
"name": "November",
"year": 2025
},
{
"incidents": [
{
"code": "4l4djy526mtl",
"impact": "major",
"message": "This incident has been resolved.",
"name": "Dashboard 01 - Major Outage due to Cloud Service Provider",
"timestamp": "Oct \u003cvar data-var='date'\u003e20\u003c/var\u003e, \u003cvar data-var='time'\u003e10:15\u003c/var\u003e - Oct \u003cvar data-var='date'\u003e21\u003c/var\u003e, \u003cvar data-var='time'\u003e02:16\u003c/var\u003e UTC"
}
],
"name": "October",
"year": 2025
}
],
"start_time": "2025-10-01T00:00:00Z",
"time_zone": "UTC"
}
]
}