All Systems Operational

About This Site

We have a full-time team dedicated to keeping CoSchedule running at full speed, but if things get weird we'll update this page to keep you in the loop. Subscribe above for instant alerts.

Web App   ? Operational
WordPress Plugin   Operational
Social Publishing   Operational
Email Notifications   Operational
Chrome Extension   Operational
Convert to Wordpress   Operational
WordPress Syncing   Operational
Heroku   Operational
Top Content Page   Operational
Degraded Performance
Partial Outage
Major Outage
Past Incidents
Nov 19, 2017

No incidents reported today.

Nov 18, 2017

No incidents reported.

Nov 17, 2017

No incidents reported.

Nov 16, 2017
Postmortem - Read details
Nov 17, 09:41 CST
Resolved - This incident has been resolved.
Nov 16, 17:04 CST
Update - As you may be aware, CoSchedule was down for an extended period of time earlier today. I want to let you know that we have identified the source of the problem, and have applied a permanent fix. CoSchedule is back online. That said, unfortunately today’s incident did result in some data loss that you need to be aware of.

What You Need to Know:

Due to the nature of the incident, we were required to restore our system from a restore point of 2:00 am CST on November 16.

While we have reason to believe that we can recover some of the data that was lost over the next 24 hours, you need to be aware that significant data from your calendar may be missing, and may never be restored.

You should assume:
* Any NEW social messages, content, projects or tasks you may have created after 2:00 am CST on November 16 will be missing from your calendar and will need to be recreated.
* Any messages or content that were created before that 2:00 am CST on November 16 will still be on your calendar. If you are missing a WordPress post in CoSchedule, please open that post in WordPress and it will sync back to your calendar.
* Any social messages that were scheduled to publish between 2:00 pm and 4:00 pm CST on November 16 will need to be rescheduled.

We understand that this is extremely frustrating. We take your data, security, and trust in us very seriously, and while we know that companies always say that, please understand that we care deeply about our product, and the customers we serve. You rely on CoSchedule for your work and livelihood, and we do not take that for granted. We are already looking into ways to prevent this type of incident in the future.

What Happened:

I want to emphasise that today’s issue was related to a database failure, and was not the result of a security breach of any kind.

At approximately 2:00 pm CST we learned that significant amounts of data had become corrupted on our primary database. To prevent further damage, we immediately took CoSchedule offline.

For many years we have maintained a redundant (backup) database. This backup generally allows us to restore corrupted data instantly with minimal data loss. In this instance, however, we learned that data loss had happened there as well, rendering it useless.

With a few minutes, we were able to begin the restore process from our third layer of protection. This restore was provided by our overnight backup system which had a restore point of 2:00 am CST on November 16. This means that while we were able to restore the vast majority of data, we did experience an irreversible loss of some customer data.

We want to leave no doubt: This was our fault, and it should have never happened. I promise you, we will make sure that it doesn’t happen again.

We appreciate your help and patience while our team worked on a fix, and apologize for the downtime and resulting data loss. We take the responsibility for the data you trust us with very seriously and we are assessing the incident and are making changes to make sure something like this does not happen again.

For now, we are confident that we have mitigated the issue. We have no reason to believe that a recurrence of this issue is possible, however our engineering team will be monitoring things closely over the next few days.

If you have further questions or concerns, please feel free to reach out to our support team.
Nov 16, 17:04 CST
Update - The system has been restored and we are still monitoring the situation. We will publish a full report as soon as we finalize the details.
Nov 16, 16:04 CST
Update - We are continuing to implement a fix and will have another update in a few minutes.
Nov 16, 14:53 CST
Update - We are continuing to monitor the build for the fix. More details when the fix is live.
Nov 16, 14:52 CST
Monitoring - We are continuing to monitor the situation. More details to follow.
Nov 16, 14:28 CST
Identified - Some users are reporting not being able to load their calendars. We have identified the issue and are working on a fix.
Nov 16, 14:11 CST
Nov 15, 2017

No incidents reported.

Nov 14, 2017

No incidents reported.

Nov 13, 2017

No incidents reported.

Nov 12, 2017

No incidents reported.

Nov 11, 2017

No incidents reported.

Nov 10, 2017

No incidents reported.

Nov 9, 2017

No incidents reported.

Nov 8, 2017

No incidents reported.

Nov 7, 2017

No incidents reported.

Nov 6, 2017

No incidents reported.

Nov 5, 2017

No incidents reported.