Retreaver incident

Outage at Twilio involving inbound Toll-free

Major Resolved View vendor source →

Retreaver experienced a major incident on October 4, 2016, lasting 53m. The incident has been resolved; the full update timeline is below.

Started
Oct 04, 2016, 03:09 PM UTC
Resolved
Oct 04, 2016, 04:03 PM UTC
Duration
53m
Detected by Pingoru
Oct 04, 2016, 03:09 PM UTC

Update timeline

  1. monitoring Oct 04, 2016, 03:09 PM UTC

    We've investigating an outage at our phone service provider, Twilio, which is affecting some customers on inbound US Toll-Free numbers. We will provide updates as soon as they are available.

  2. monitoring Oct 04, 2016, 03:21 PM UTC

    Twilio's upstream provider is reporting an outage at a major carrier involving some inbound US Toll-Free numbers. This is currently affecting some Retreaver customers. We are following the situation closely and will provide an update as soon as possible.

  3. monitoring Oct 04, 2016, 03:28 PM UTC

    Twilio has provided an update regarding the outage in US Toll-Free inbound calls: "At this point of time, a large part of inbound Toll Free calls and approximately 50% of inbound calls to numbers in United States are not able to reach Twilio. We are working towards identifying ETA of service recovery." Retreaver continues to follow the situation closely and will provide updates shortly.

  4. monitoring Oct 04, 2016, 03:46 PM UTC

    Twilio has reported that inbound Toll-free is restored: "Inbound traffic to US numbers has been restored. We will keep monitoring until confirmed full resolution with our carrier partner." Retreaver continues to monitor the situation.

  5. resolved Oct 04, 2016, 04:03 PM UTC

    Toll-free traffic has returned to normal levels and calls are being processed correctly. We've been informed that the outage in US Inbound Toll-free was being caused by a major nation-wide outage at Level 3. Retreaver is currently fast-tracking a solution to provide carrier-redundancy on inbound US Toll-free lines, which we will detail in a future blog post. We continue to monitor the situation at Level 3 and Twilio and will provide more updates as necessary.