Monitoring - The engineers are making upgrades to our caching layer infrastructure and adding more capacity to eliminate message caching delays. We will provide another update as soon as the updates are complete.
Aug 18, 10:57 CDT
Identified - The 2.0 Syncs are falling behind which is causing a delay on 2.0 webhooks. We have a identified an issue causing our MSI syncs to run slow. The engineers are now working on an infrastructure upgrade to ensure proper performance.
Aug 17, 09:49 CDT
2.0 API ? Operational
2.0 Syncs Degraded Performance
2.0 Webhooks ? Degraded Performance
Lite API ? Operational
Lite WebHooks ? Operational
Developer Console ? Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Aug 23, 2017

No incidents reported today.

Aug 22, 2017

No incidents reported.

Aug 21, 2017

No incidents reported.

Aug 20, 2017

No incidents reported.

Aug 19, 2017

No incidents reported.

Aug 16, 2017
Resolved - The sync queue has cleared and all syncs are operating normally again.
Aug 16, 23:30 CDT
Investigating - We're investigating an issue causing delays to 2.0 syncs and webhooks. We'll update as soon as we identify the cause.
Aug 16, 15:19 CDT
Aug 15, 2017
Resolved - The DNS settings are propagating and APIs are back up.
Aug 15, 14:35 CDT
Identified - A DNS related issue is preventing API calls from resolving properly. We have identified the issue and are working to get it fixed immediately.
Aug 15, 14:18 CDT
Aug 14, 2017

No incidents reported.

Aug 13, 2017

No incidents reported.

Aug 12, 2017
We've identified an issue affecting message endpoints for a small percentage of accounts, causing slow responses and timeouts. We've implemented a fix that will gradually improve response times throughout the day for these affected accounts.
Aug 12, 12:28 CDT
Resolved - The syncs cleared overnight and are back to operating normally.
Aug 12, 09:20 CDT
Identified - We've temporarily disabled the message counts (`nb_messages`) for the `2.0/accounts` endpoints to help with response times. We'll enable those again once the sync queue is cleared.
Aug 11, 19:23 CDT
Monitoring - The backlog of messages continues to drain at an increasing pace. We estimate the queue will be flushed this evening. We'll resolve this incident as soon as the syncs have caught up completely.
Aug 11, 16:33 CDT
Update - The backlog of syncs is putting a higher load than usual on our systems, which is causing some requests to 2.0 to time out. This should start to improve as the sync backlog clears.
Aug 11, 13:02 CDT
Identified - We have identified the cause of the sync queue and have deployed a fix. The backlog of syncs is now going down.
Aug 11, 12:32 CDT
Update - The engineers are working to isolate the root cause of the sync delays. We will provide an ETA for the resolution once we have full confirmation on the cause and identify the best solution.
Aug 11, 11:27 CDT
Investigating - We're investigating a spike in our 2.0 sync queue which is also affecting the performance of 2.0 webhooks.
Aug 11, 08:47 CDT
Aug 10, 2017

No incidents reported.

Aug 9, 2017

No incidents reported.