TigerConnect incident

Service degradation

Minor Resolved View vendor source →

TigerConnect experienced a minor incident on September 28, 2016, lasting 5h 42m. The incident has been resolved; the full update timeline is below.

Started
Sep 28, 2016, 05:04 PM UTC
Resolved
Sep 28, 2016, 10:47 PM UTC
Duration
5h 42m
Detected by Pingoru
Sep 28, 2016, 05:04 PM UTC

Update timeline

  1. investigating Sep 28, 2016, 05:04 PM UTC

    TigerText is investigating a sporadic degradation in service that may affect login, sending, and receiving messages. Another update will be provided in one hour.

  2. investigating Sep 28, 2016, 06:04 PM UTC

    TigerText continues to investigate sporadic degradation in service that may affect slowness with login, sending and receiving messages. Another update will be provided in one hour. Thank you for your patience. If you have any questions feel free to contact us at [email protected].

  3. investigating Sep 28, 2016, 06:59 PM UTC

    TigerText continues to investigate sporadic degradation in service affecting push notifications to iOS devices and login, sending and receiving messages with web, Desktop App, and mobile. Users on iOS devices will receive messages despite the push notification not received. Another update will be provided in 30 minutes.

  4. investigating Sep 28, 2016, 07:36 PM UTC

    Users on iOS devices should start receiving push notifications as normal. Users may receive multiple push notifications for messages already Read as our queue catches up. TigerText will continue to investigate sporadic degradation in service that may affect login, sending and receiving messages. Another update will be provided in one hour.

  5. investigating Sep 28, 2016, 08:25 PM UTC

    TigerText continues to investigate sporadic degradation in service that may result in slowness with login, sending and receiving messages. Another update will be provided in four hours. Thank you for your patience. If you have any questions feel free to contact us at [email protected].

  6. resolved Sep 28, 2016, 10:47 PM UTC

    The degradation in service has been corrected and services are slowly coming back to normal. Thank you for your patience. Please contact us at [email protected] if you have any questions.