The incident is resolved
Dec 7, 22:05 PST
We have started our Streaming services and currently monitoring.
We also started processing Impressions Webhook backlog, no data loss is reported.
Dec 7, 18:02 PST
We are observing AWS services started to come back online, we are monitoring at this point and will start enabling the Streaming service gradually
Dec 7, 17:05 PST
We are continuing to work on a fix for this issue.
Dec 7, 17:04 PST
We continue to experience issues with AWS.
- No data loss.
- Streaming is disabled. SDKs will fallback to polling mechanism and will continue to get updates from Split.
- Amplitude, impressions webhook, mParticle, S3 outbound (impressions) are experiencing delays with no data loss.
- Data exports are currently failing. They will be back up once AWS status normalizes.
Dec 7, 12:28 PST
Events service has recovered. Data loss is no longer expected.
Dec 7, 11:42 PST
AWS outage is causing issues for our events service, resulting in intermittent data loss.
We continue to monitor how the AWS incident evolves and will keep this incident updated.
Dec 7, 10:46 PST
As a result of the ongoing AWS incident we are also observing delays for our impressions webhook, as well as our Amplitude and mParticle outgoing integrations. There is no data loss.
Dec 7, 08:47 PST
We have identified issues with AWS US-EAST-1 region which could affect our streaming service. To avoid SDKs missing updates, we have temporarily disabled streaming so all instances will now be getting updates through polling. All running instances will do the switch automatically.
Dec 7, 08:42 PST