Identified - Since July 17, we started to be impacted by the following Instagram/Facebook issue

As a result, your Instagram account token might be invalid many times for the last 24 hours, even if you renew it correctly on a regular basis.
Your scheduled items might also fail to be published with the following error message: "(#10) Application does not have permission for this action (code 10, subcode null)"

We're monitoring this issue closely and apologize for the inconvenience
Jul 18, 12:50 CEST
Manager ? Operational
Facebook Publishing & Data Processing ? Operational
Twitter Publishing & Data Processing ? Operational
Instagram Publishing & Data Processing ? Partial Outage
Linkedin Publishing & Data Processing Operational
Google Plus Publishing & Data Processing Operational
Youtube Data Processing Operational
Facebook Timeline Contest ? Operational
Facebook Page Barometer ? Operational
Web site ? Operational
Cloud Provider ? Operational
Degraded Performance
Partial Outage
Major Outage
Manager - Response time
Facebook Page Barometer - Response time
Facebook Timeline Contest - Response time
Past Incidents
Jul 22, 2019

No incidents reported today.

Jul 21, 2019

No incidents reported.

Jul 20, 2019

No incidents reported.

Jul 19, 2019

No incidents reported.

Jul 17, 2019

No incidents reported.

Jul 16, 2019

No incidents reported.

Jul 15, 2019

No incidents reported.

Jul 14, 2019

No incidents reported.

Jul 13, 2019

No incidents reported.

Jul 12, 2019
Resolved - This incident has been solved. Thanks again for your patience
Jul 12, 08:59 CEST
Monitoring - As you can read here, the Twitter API should now be fully operational. We're now seeing both scheduled and queued tweets publishing as expected.
We will mark this incident as resolved when Twitter confirm it’s completely fixed.
Jul 11, 22:19 CEST
Identified - We’re currently impacted by a global API Twitter outage, as you can read here

Unfortunately, this means that we cannot synchronize your inbox or publish any tweets.

We apologize as this issue is beyond our control.
Jul 11, 21:35 CEST
Jul 11, 2019
Resolved - We've been able to fine-tune the way we synchronize your Twitter inbox, according to the plan you subscribed to.
Feel free to contact our support team if you have any question (
Jul 11, 21:37 CEST
Identified - Twitter recently announced some important changes to the way they collaborate with third party tools. In that regard and starting today, we have to change how quickly we can sync with Twitter. (

There are two changes to be aware of:
- Inbox: New Mention synchronization will change from the current 5 minutes to be every 60 Minutes
- Calendar: Items you publish from Twitter natively, will now take up to 1 hour to be displayed in your calendar;

Important: Direct message are not impacted. You'll still receive DMs in your Inbox, and we will continue to sync them with the same frequency (near to real time).

We're sorry about such short notice with the changes and we are working hard with Twitter to find the best solutions going forward.
In the short term, we've had to change the sync frequency to retain the ability to synchronize Twitter mentions for everyone.

We will keep you updated once we move forward with options and alternatives. 🙌

If you have any questions, feel free to ask (
Jun 12, 11:21 CEST
Jul 10, 2019

No incidents reported.

Jul 9, 2019
Resolved - We just released a fix: we need you to click on the "reconnect with Linkedin" button and accept the new permissions we're asking to be able to synchronize your account and publish your scheduled items.
If you're trying to renew your token for a company page, please make sure you have an admin role for this page.

We really apologize for the inconvenience
Jul 9, 10:30 CEST
Identified - We identified the reasons that prevented renewing your Linkedin token or publish any LinkedIn items. Our team is currently working on a fix.
Thank you for your patience
Jul 9, 10:03 CEST
Investigating - We're currently facing a Linkedin publishing bug, preventing to publish any item on Linkedin (error code : Not enough permissions to access: POST /shares)
We're investigating and we will update this incident as soon as we identified the problem.
We really apologize for the inconvenience
Jul 8, 23:10 CEST