Yesware incident

Services Unavailable

Major Resolved View vendor source →

Yesware experienced a major incident on October 31, 2017, lasting 2h 38m. The incident has been resolved; the full update timeline is below.

Started
Oct 31, 2017, 01:01 PM UTC
Resolved
Oct 31, 2017, 03:40 PM UTC
Duration
2h 38m
Detected by Pingoru
Oct 31, 2017, 01:01 PM UTC

Update timeline

  1. identified Oct 31, 2017, 01:01 PM UTC

    Due to a widespread problem with an upstream service provider, some features (including open and link tracking) may be unavailable at the moment. Updates to follow.

  2. investigating Oct 31, 2017, 01:18 PM UTC

    Due to a widespread issue with a service provider, all Yesware features and services may be inaccessible at the moment. The underlying issue has yet to be resolved with our provider. Updates to follow as they are made available.

  3. monitoring Oct 31, 2017, 02:25 PM UTC

    Recovery is now underway. Access to Yesware services and features should be restored shortly. We will continue to monitor our systems to ensure all services and features are working properly.

  4. resolved Oct 31, 2017, 03:40 PM UTC

    All services have recovered.