11pm UTC 10/19/16
We have resolved all connection issues and confirmed customers are receiving data back in from the delay. We are investigating root cause with Microsoft currently and will report back with more details as they are available. Our apologies for the disruption but please contact our support team with any continued issues, if you are not seeing data expected, or any other questions we can help with.
10pm UTC 10/18/16
We have begun receiving reports of connection errors from clients using our US datacenter. This is impacting email sends, data writing back, and even leveraging some of our editors. The connection error received will state a variant of 'Metadata contains a reference that cannot be resolved' and 'The remote name could not be resolved'. Our operations team is investigating with urgency and we will post here with updates as we have them available.