AWS Outage

Incident Report for Plivo

Resolved

We have now restored all recordings not uploaded to S3 during the AWS outage.
The issue is now fully resolved.

Posted Mar 01, 2017 - 01:35 UTC

Update

All services are now fully operational. We will close the incident and mark it as resolved once we're done reinserting all the recordings that failed to upload during the outage.

Posted Feb 28, 2017 - 23:05 UTC

Update

The recordings are now being uploaded successfully. We are now in the process of re-uploading the recordings that happened during the AWS outage. We will add another update once the recording backfill is done.

Posted Feb 28, 2017 - 22:48 UTC

Update

The WebSDK is now available again on its usual URL (https://s3.amazonaws.com/plivosdk/web/plivo.min.js) and the Account Interface is also back online (https://manage.plivo.com/dashboard/) - We're working on bringing the Website and the Blog back online as soon as possible.

Posted Feb 28, 2017 - 20:58 UTC

Update

We're still closely monitoring the situation - We will upload the call recordings to S3 once the incident is resolved

Posted Feb 28, 2017 - 20:31 UTC

Update

As a temporary fix, you can use this URL to use the WebSDK : https://44331acfb583d0aaf00d-5ca3180738c02128ce523651411c8aef.ssl.cf2.rackcdn.com/plivo.min.js - The main URL for the WebSDK will be usable once again when the outage is resolved.

Posted Feb 28, 2017 - 19:23 UTC

Monitoring

We're actively monitoring our upstream provider's (AWS) status and working on mitigating the issue.

Posted Feb 28, 2017 - 18:52 UTC

Identified

Our main provider, AWS, is having global issues with it's CDN and File Hosting services (CloudFront and S3). We're working with them to resolve the issue.

Posted Feb 28, 2017 - 18:16 UTC