Chili Piper Status

Postmortem: We discovered this morning that Outlook invites and events were also impacted by the same service failure, extending the scope to both Google and Outlook customers.

We are working on recovering all failed events, but don’t have a specific timeline for this action. Our hope is to get this finalized today.

It’s likely that, while we are waiting on recovery, other meetings may get booked into those open calendar slots. This would result in overbooked meetings once the recovery finalizes, but this is the only way we can accommodate both parties who booked meetings during that time slot. One of the remaining events would ultimately need to be rescheduled manually.

We are investigating our processes that led to the release of this bug and will improve to ensure more thorough testing is performed before release.

Apologies for the inconvenience this has caused.

Resolved: Our team identified that the issue was related to a deployment of our integration services at approximately 15:32 EST (20:32 UTC) for an incident span of approximately 2 hours.

We rolled back the deployment and this resolved the issue, and we saw error rates drop to zero.

It is likely that any meetings booked during this time may have been impacted where no Google calendar event was created in its place.

We strongly recommend manually creating these events if they're identified in the meantime rather than waiting on a replay action (if this is possible from our end) as this will ensure that all parties have the most up-to-date calendar appearance, and ensures prospects receive meeting invites.

Apologies for the disruption this may have caused.

Investigating: Our team has received reports and has found evidence that in many cases the Google calendar service is not creating Events on the calendar. This appears to be a wide-spread issue, but does not appear to impact all meetings booked.

We are investigating the root cause of this issue now and will provide recommendations once we discover more about the circumstances of this issue.

Postmortem: We discovered this morning that Outlook invites and events were also impacted by the same service failure, extending the scope to both Google and Outlook customers.

We are working on recovering all failed events, but don’t have a specific timeline for this action. Our hope is to get this finalized today.

It’s likely that, while we are waiting on recovery, other meetings may get booked into those open calendar slots. This would result in overbooked meetings once the recovery finalizes, but this is the only way we can accommodate both parties who booked meetings during that time slot. One of the remaining events would ultimately need to be rescheduled manually.

We are investigating our processes that led to the release of this bug and will improve to ensure more thorough testing is performed before release.

Apologies for the inconvenience this has caused.

Resolved: Our team identified that the issue was related to a deployment of our integration services at approximately 15:32 EST (20:32 UTC) for an incident span of approximately 2 hours.

We rolled back the deployment and this resolved the issue, and we saw error rates drop to zero.

It is likely that any meetings booked during this time may have been impacted where no Google calendar event was created in its place.

We strongly recommend manually creating these events if they're identified in the meantime rather than waiting on a replay action (if this is possible from our end) as this will ensure that all parties have the most up-to-date calendar appearance, and ensures prospects receive meeting invites.

Apologies for the disruption this may have caused.

Investigating: Our team has received reports and has found evidence that in many cases the Google calendar service is not creating Events on the calendar. This appears to be a wide-spread issue, but does not appear to impact all meetings booked.

We are investigating the root cause of this issue now and will provide recommendations once we discover more about the circumstances of this issue.

Postmortem: We discovered this morning that Outlook invites and events were also impacted by the same service failure, extending the scope to both Google and Outlook customers.

We are working on recovering all failed events, but don’t have a specific timeline for this action. Our hope is to get this finalized today.

It’s likely that, while we are waiting on recovery, other meetings may get booked into those open calendar slots. This would result in overbooked meetings once the recovery finalizes, but this is the only way we can accommodate both parties who booked meetings during that time slot. One of the remaining events would ultimately need to be rescheduled manually.

We are investigating our processes that led to the release of this bug and will improve to ensure more thorough testing is performed before release.

Apologies for the inconvenience this has caused.

Resolved: Our team identified that the issue was related to a deployment of our integration services at approximately 15:32 EST (20:32 UTC) for an incident span of approximately 2 hours.

We rolled back the deployment and this resolved the issue, and we saw error rates drop to zero.

It is likely that any meetings booked during this time may have been impacted where no Google calendar event was created in its place.

We strongly recommend manually creating these events if they're identified in the meantime rather than waiting on a replay action (if this is possible from our end) as this will ensure that all parties have the most up-to-date calendar appearance, and ensures prospects receive meeting invites.

Apologies for the disruption this may have caused.

Investigating: Our team has received reports and has found evidence that in many cases the Google calendar service is not creating Events on the calendar. This appears to be a wide-spread issue, but does not appear to impact all meetings booked.

We are investigating the root cause of this issue now and will provide recommendations once we discover more about the circumstances of this issue.

Postmortem: We discovered this morning that Outlook invites and events were also impacted by the same service failure, extending the scope to both Google and Outlook customers.

We are working on recovering all failed events, but don’t have a specific timeline for this action. Our hope is to get this finalized today.

It’s likely that, while we are waiting on recovery, other meetings may get booked into those open calendar slots. This would result in overbooked meetings once the recovery finalizes, but this is the only way we can accommodate both parties who booked meetings during that time slot. One of the remaining events would ultimately need to be rescheduled manually.

We are investigating our processes that led to the release of this bug and will improve to ensure more thorough testing is performed before release.

Apologies for the inconvenience this has caused.

Resolved: Our team identified that the issue was related to a deployment of our integration services at approximately 15:32 EST (20:32 UTC) for an incident span of approximately 2 hours.

We rolled back the deployment and this resolved the issue, and we saw error rates drop to zero.

It is likely that any meetings booked during this time may have been impacted where no Google calendar event was created in its place.

We strongly recommend manually creating these events if they're identified in the meantime rather than waiting on a replay action (if this is possible from our end) as this will ensure that all parties have the most up-to-date calendar appearance, and ensures prospects receive meeting invites.

Apologies for the disruption this may have caused.

Investigating: Our team has received reports and has found evidence that in many cases the Google calendar service is not creating Events on the calendar. This appears to be a wide-spread issue, but does not appear to impact all meetings booked.

We are investigating the root cause of this issue now and will provide recommendations once we discover more about the circumstances of this issue.