Telerivet incident

Database Interruption

Notice Resolved View vendor source →

Telerivet experienced a notice incident on March 1, 2015, lasting 52m. The incident has been resolved; the full update timeline is below.

Started
Mar 01, 2015, 02:26 AM UTC
Resolved
Mar 01, 2015, 03:18 AM UTC
Duration
52m
Detected by Pingoru
Mar 01, 2015, 02:26 AM UTC

Update timeline

  1. investigating Mar 01, 2015, 02:26 AM UTC

    Telerivet's primary database server is currently not responding. Telerivet has automatically failed over to a standby database server.

  2. identified Mar 01, 2015, 02:48 AM UTC

    Datacenter personnel have identified a hardware problem with one of Telerivet's database servers, and are working to resolve it. In the meantime, Telerivet is fully operational. The outage lasted about 40 seconds at 02:21 UTC before the automated failover system switched to the standby database.

  3. resolved Mar 01, 2015, 03:18 AM UTC

    The hardware issue has been resolved. All Telerivet services continue to be fully operational.