We will close the issue as resolved, as we have seen improved performance in the early morning hours of CET the last 9 days since the root cause was identified and fixes applied last week. We have additional actions to reduce load on specific API calls in the future, in order to prevent similar bottlenecks to appear. We will also be announcing a larger database maintenance event soon, which will be performed over a weekend to help improve performance further. Thanks for your patience.
Mar 22, 09:56 EDT
We are continuing to monitor however Podio has been stable since 10.15 EST. We have seen better performance in the morning of CET and is now investigating what caused the issues today in the morning of EST (US time). Thanks for your patience. We will keep this incident open until both issues have been fully confirmed resolved.
Mar 18, 17:25 EDT
We are monitoring performance as things have been stable the last 30 minutes.
Mar 18, 10:37 EDT
We are looking into reports of Podio being unavailable at the moment.
Mar 18, 10:10 EDT
We are investigating errors on Podio at the moment.
Mar 18, 09:37 EDT
Podio is still fully operational however we are keeping the incident open until we confirm the spikes in early morning CET has been resolved on Mondays and Tuesdays as well, this is our peak time for load on Podio. We will close the incident when resolution has been confirmed this week.
Mar 17, 20:51 EDT
Podio has been operational the last 2 days and we believe to have identified cause of the early spikes in performance in mornings CET. We will have follow up actions to prevent similar case to occur in the future. We are still monitoring results and will have additional actions the following weeks to improve further.
Mar 14, 10:52 EDT
We have seen good initial results from the cause analysis and changes done from yesterday, however we are still monitoring results and will keep the incident open for another few days to confirm full resolution on a daily basis. Podio is still fully operational and have seen good performance today so far.
Mar 13, 08:05 EDT
Update: We are still investigating different routes of cause for the spike in latency in the morning hours of CET. We had issues today from around 8.30 CET to 9.10 CET and have seen similar symptoms in the morning hours of CET over the last 2 weeks. We are doing everything we can to find cause and longterm solution. We will share additional updates in the morning CET. We will keep this incident open until we have root cause defined and action plan in place.
Mar 12, 11:30 EDT
We are getting closer to understanding the root cause and will update as we have more confirmation. Performance has been stable the last 2 hours.
Mar 12, 06:50 EDT
Performance is improving, we continue to investigate the issue.
Mar 12, 04:20 EDT
We are currently investigating the issue
Mar 12, 04:10 EDT