Telerivet incident

Scheduled datacenter migration

Minor Resolved View vendor source →

Telerivet experienced a minor incident on January 2, 2016, lasting 5h 39m. The incident has been resolved; the full update timeline is below.

Started
Jan 02, 2016, 05:17 PM UTC
Resolved
Jan 02, 2016, 10:56 PM UTC
Duration
5h 39m
Detected by Pingoru
Jan 02, 2016, 05:17 PM UTC

Update timeline

  1. scheduled Jan 02, 2016, 05:17 PM UTC

    In order to avoid the continuing DDoS attacks against Linode, Telerivet will be moving to a secondary data center (AWS) in approximately 3 hours. No downtime is expected, although some errors or performance issues may occur. Search and dynamic groups will be unavailable for approximately 1 hour while the index is rebuilt. SMPP connections will continue to be routed via Linode's data center in order to maintain connectivity for users with connections fixed to a Linode IP address.

  2. in progress Jan 02, 2016, 10:01 PM UTC

    Telerivet's servers migrated to an AWS data center 1 hour ago and appear to be operating smoothly. The search index is currently being rebuilt, and is anticipated to be ready about 1 hour from now.

  3. completed Jan 02, 2016, 10:56 PM UTC

    The migration to AWS is complete, and all Telerivet services are currently operational.