Stream incident

Failure on main PG database

Major Resolved View vendor source →

Stream experienced a major incident on December 26, 2017, lasting 44m. The incident has been resolved; the full update timeline is below.

Started
Dec 26, 2017, 09:45 PM UTC
Resolved
Dec 26, 2017, 10:30 PM UTC
Duration
44m
Detected by Pingoru
Dec 26, 2017, 09:45 PM UTC

Update timeline

  1. identified Dec 26, 2017, 09:45 PM UTC

    Our main PG database (that holds the configs) is seeing high CPU. This is causing a percentage of API requests to fail. We're investigating this issue and will keep you posted.

  2. resolved Dec 26, 2017, 10:30 PM UTC

    The issue was mitigated and we are now working on a permanent solution.