Report an Incident
Twilio Services
Issues related to Twilio’s Software
    External Connectivity
    Issues found outside of Twilio’s Network
      Zipwhip Gateway
      Issues related to Zipwhip's Services
        Scheduled maintenance
        System Metrics

        Flex Issue - Customers Getting 502 Bad Gateway Error When Calling TaskRouter API

        Incident Report for Twilio

        Resolved

        For Flex, when calling the TaskRouter API, is now operating normally.
        Posted Feb 22, 2022 - 16:36 PST

        Monitoring

        For Flex, when calling the TaskRouter API, is now operating normally. We will continue to monitor for system stability. We'll provide another update in 2 hours or as soon as more information becomes available.
        Posted Feb 22, 2022 - 14:46 PST

        Identified

        Our engineers have identified the issue causing the 502 Bad Gateway Error when calling the TaskRouter API and are working to deploy a fix. We expect to provide another update in 1 hour or as soon as more information becomes available.
        Posted Feb 22, 2022 - 13:56 PST

        Update

        We are investigating an issue where customers are getting a 502 Bad Gateway Error when calling the TaskRouter API. We expect to provide another update in 1 hour or as soon as we have more information.
        Posted Feb 22, 2022 - 13:04 PST

        Update

        We are investigating an issue where customers are getting a 502 Bad Gateway Error when calling the TaskRouter API. We expect to provide another update in 1 hour or as soon as we have more information.
        Posted Feb 22, 2022 - 13:01 PST

        Investigating

        We've become aware of a potential issue with Flex. Our engineering team has been alerted and is actively investigating. We will update as soon as we have more information.
        Posted Feb 22, 2022 - 12:54 PST
        This incident affected: TaskRouter.
        ← Current Status Powered by Atlassian Statuspage