Yesware incident

Service Interruption

Minor Resolved View vendor source →

Yesware experienced a minor incident on October 16, 2017, lasting 40m. The incident has been resolved; the full update timeline is below.

Started
Oct 16, 2017, 02:21 PM UTC
Resolved
Oct 16, 2017, 03:01 PM UTC
Duration
40m
Detected by Pingoru
Oct 16, 2017, 02:21 PM UTC

Update timeline

  1. identified Oct 16, 2017, 02:21 PM UTC

    Yesware is currently experiencing an issue with an upstream database provider and is working with said provider to resolve the issue as quickly as possible. We apologize for the inconvenience.

  2. monitoring Oct 16, 2017, 02:35 PM UTC

    The upstream provider has recovered. Yesware is continuing to monitor performance.

  3. resolved Oct 16, 2017, 03:01 PM UTC

    Yesware performance has returned to normal.