Time: Oct. 30, 2019, 5:03 p.m.

Status: Resolved

Update: After monitoring our system throughout the day we can confirm that this problem is now resolved.

Time: Oct. 30, 2019, 10:34 a.m.

Status: Monitoring

Update: On Thursday 24th October, we began seeing a higher rate of timeouts in our analytics dashboard. While this was not a consistent problem, several of our customers have been impacted over the following days. We have identified a defect in one of our background data reconciliation processes that we believe caused our data warehouse to become less performant. This in turn had a negative impact on our analytics tools. We have rolled out a fix to the defect and will monitor the outcome.

Time: Aug. 17, 2019, 11:32 a.m.

Status: Resolved

Update: A limited number of our customers will have experienced significantly reduced targeting rates with our JavaScript SDK. This occurred during the period of 03:00 BST on Friday the 16th until 11:30 on Saturday the 17th of August. This issue is fully resolved and targeting rates have returned to normal. Timeline: 1. At 00:30 on Saturday the 17th of August our automated monitoring notified our engineering team that targeting rates had dropped below a predefined threshold for a single customer. Our engineers investigated the issue and confirmed that there was an error being produced for that customer under a limited set of conditions 2. Looking through our logs we realised this issue had started occurring at 03:00 the previous day (Friday the 16th of August). It had originally occurred with minimal impact and had slowly grown over the intervening period until it triggered our alert once it reached predefined threshold. We identified that it had been related to an anomalous traffic pattern we had identified at 18:00 on Friday the 16th 3. Further, at 00:50 we identified a second customer where this issue had started manifesting, but were still below the threshold that would trigger our alerts 4. At 09:20 our engineers identified the root cause of the issue, which occurred when those two customers used a particular type of segmentation query in combination with a recent change we'd made to our Query Language and deployed that week 5. A fix was put in place to our Query Language at 9:52AM London time and rolled out to all effected customers by 11:30am London time on Saturday the 17th of August Most of our customers were unaffected by this issue. If you were affected your Customer Success Manager will reach out to you with further information.

Time: Aug. 17, 2019, 11:32 a.m.

Status: Resolved

Update: A limited number of our customers will have experienced significantly reduced targeting rates with our JavaScript SDK. This occurred during the period of 03:00 BST on Friday the 16th until 11:30 on Saturday the 17th of August. This issue is fully resolved and targeting rates have returned to normal. Timeline: 1. At 00:30 on Saturday the 17th of August our automated monitoring notified our engineering team that targeting rates had dropped below a predefined threshold for a single customer. Our engineers investigated the issue and confirmed that there was an error being produced for that customer under a limited set of conditions 2. Looking through our logs we realised this issue had started occurring at 03:00 the previous day (Friday the 16th of August). It had originally occurred with minimal impact and had slowly grown over the intervening period until it triggered our alert once it reached predefined threshold. We identified that it had been related to an anomalous traffic pattern we had identified at 18:00 on Friday the 16th 3. Further, at 00:50 we identified a second customer where this issue had started manifesting, but were still below the threshold that would trigger our alerts 4. At 09:20 our engineers identified the root cause of the issue, which occurred when those two customers used a particular type of segmentation query in combination with a recent change we'd made to our Query Language and deployed that week 5. A fix was put in place to our Query Language at 9:52AM London time and rolled out to all effected customers by 11:30am London time on Saturday the 17th of August Most of our customers were unaffected by this issue. If you were affected your Customer Success Manager will reach out to you with further information.

Time: July 29, 2019, 3:43 p.m.

Status: Resolved

Update: The issue has been resolved and all services are returning to normal.

Time: July 29, 2019, 3:30 p.m.

Status: Monitoring

Update: The upstream service provider has resolved their issue, so our dashboard is returning to normal functionality. We're currently deploying a fix to prevent this issue reoccurring.

Time: July 29, 2019, 3:27 p.m.

Status: Identified

Update: One of our downstream SaaS service providers is experiencing unexpected down-time, which caused an unexpected fault in our management service which powers our dashboard. We're implementing a fix a which should be effective in the next 10 minutes.

Time: July 29, 2019, 3:18 p.m.

Status: Investigating

Update: We've received reports that our dashboard is returning results slowly and is failing some requests. We're investigating the root cause and we will update as soon as we know more.

Time: July 29, 2019, 3:43 p.m.

Status: Resolved

Update: The issue has been resolved and all services are returning to normal.

Time: July 29, 2019, 3:30 p.m.

Status: Monitoring

Update: The upstream service provider has resolved their issue, so our dashboard is returning to normal functionality. We're currently deploying a fix to prevent this issue reoccurring.

Time: July 29, 2019, 3:27 p.m.

Status: Identified

Update: One of our downstream SaaS service providers is experiencing unexpected down-time, which caused an unexpected fault in our management service which powers our dashboard. We're implementing a fix a which should be effective in the next 10 minutes.

Time: July 29, 2019, 3:18 p.m.

Status: Investigating

Update: We've received reports that our dashboard is returning results slowly and is failing some requests. We're investigating the root cause and we will update as soon as we know more.