All Systems Operational
Manager ? Operational
Facebook Publishing & Data Processing ? Operational
Twitter Publishing & Data Processing ? Operational
Instagram Publishing & Data Processing ? Operational
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
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Manager - Response time
Fetching
Facebook Page Barometer - Response time
Fetching
Facebook Timeline Contest - Response time
Fetching
Past Incidents
Apr 18, 2019
Resolved - Facebook confirmed the bug was fixed: the option is now back on Agorapulse, you can add a location to your next scheduled or queued items.
All previously scheduled/queued Instagram posts that have not been published yet will resume posting as originally created with tagged locations if applicable.

Thanks
Apr 18, 20:27 CEST
Update - As there is still no update from Facebook, we disabled the location feature and removed tagged locations from all scheduled and queued Instagram items with our weekly release.

Once the bug is resolved by Facebook, the option will be back on Agorapulse
Apr 17, 13:07 CEST
Identified - Instagram API is currently experiencing an issue that is impacting all third party apps that prevents direct posting where location tagging is used.
The error message you will receive is the following: Facebook error: Fatal (code -1, subcode 2207001) errorUserTitle=Instagram Platform API Error

Facebook received information about this bug report and assigned it to their team: https://developers.facebook.com/support/bugs/307064806625308/

The next steps on Agorapulse will be: with our next release planned on April 17, we will disable this feature and remove tagged locations from all scheduled and queued items.
In the meantime, our recommendation is to publish the Instagram post without using the location feature.

Once the bug is resolved by Facebook, the option will be back on Agorapulse
Apr 16, 16:05 CEST
Apr 16, 2019
Completed - The scheduled maintenance has been completed.
Apr 16, 07:54 CEST
Verifying - Verification is currently underway for the maintenance items.
Apr 16, 07:34 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 16, 06:31 CEST
Scheduled - We're going to perform a maintenance operation on our infrastructure on Tuesday, April 16, around 7am Paris time (1pm in Singapore, 1am in New York and 10pm on April 15 in Los Angeles). This maintenance should last no more than one hour.

This maintenance operation will upgrade our app structure.

You won’t be able to use Agorapulse during this period and you might face the following issues:

- items scheduled during this timeframe won’t be published on time. However, upon the completion of this maintenance, these items will be published immediately. Please anticipate this delay.
- inbox items received during this time will be retrieved after the downtime (you won't lose any data)

Rest assured that we will do our best to make this experience as smooth as possible.
Apr 10, 16:05 CEST
Apr 15, 2019

No incidents reported.

Apr 14, 2019

No incidents reported.

Apr 13, 2019

No incidents reported.

Apr 12, 2019

No incidents reported.

Apr 11, 2019

No incidents reported.

Apr 10, 2019

No incidents reported.

Apr 9, 2019

No incidents reported.

Apr 8, 2019

No incidents reported.

Apr 7, 2019

No incidents reported.

Apr 6, 2019

No incidents reported.

Apr 5, 2019
Resolved - This incident has been resolved. Thanks for your patience
Apr 5, 09:34 CEST
Monitoring - We released a new version to fix this issue and for now, there is no loading delay anymore.
We keep monitoring this and will update this incident very soon to confirm the resolution.
Thanks!
Apr 4, 23:58 CEST
Investigating - We are currently experiencing loading and syncing delays with our desktop app, mobile app, and Chrome Extension. Our tech team is working hard to resolve this issue as quickly as possible.
Apr 4, 18:43 CEST