Historial de interrupciones de Flowroute

1. July 27, 2026 at 2:22 PM UTCinvestigating

   Actualmente estamos investigando informes de fracasos en llamadas libres de llamadas inbound toll.

2. July 27, 2026 at 2:40 PM UTCidentified

   Se ha determinado la cuestión y se está aplicando una solución.

3. July 27, 2026 at 2:42 PM UTCmonitoring

   Se ha implementado una solución y nuestra prueba inicial muestra que está fijada. Continuamos monitoreando los resultados.

4. July 27, 2026 at 3:51 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. May 14, 2026 at 3:45 PM UTCinvestigating

   We are investigating reports of intermittent inbound call failures to Toll Free numbers.

2. May 14, 2026 at 3:49 PM UTCidentified

   The issue has been identified and a fix is being implemented.

3. May 14, 2026 at 3:54 PM UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. May 14, 2026 at 4:55 PM UTCresolved

   This incident has been resolved.

1. March 3, 2026 at 3:15 PM UTCinvestigating

   We are currently investigating intermittent outbound one way audio.

2. March 3, 2026 at 3:19 PM UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. March 3, 2026 at 5:20 PM UTCresolved

   This issue has been fully resolved

1. February 11, 2026 at 7:53 PM UTCinvestigating

   We are currently investigating delays with our CDR exports in both the Manage portal and CDR export APIs.

2. February 13, 2026 at 8:09 PM UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. February 17, 2026 at 7:00 PM UTCinvestigating

   We are currently investigating new delays with our CDR exports.

4. February 19, 2026 at 5:23 PM UTCresolved

   This incident has been resolved.

1. July 23, 2025 at 4:27 PM UTCidentified

   The Manage Portal is currently inaccessible. Our Dev team is aware and working to implement a fix. Call traffic across the network is working as normal.

2. July 23, 2025 at 6:45 PM UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. July 23, 2025 at 8:16 PM UTCresolved

   This incident has been resolved.

1. July 1, 2025 at 3:37 PM UTCidentified

   3CX customers are experiencing issues with some outbound calls due to Private IP addresses in the SIP headers. Some outbound carriers are no longer accepting traffic from Private IP addresses. 3CX has pushed an update for v20 update 6 that allows customers to update to a new 3CX Flowroute template and adjust the Via Header IP address to the Public IP address. This can be done by selecting the new template and navigating to the “Voice and Chat” tab, enabling the “Public IP in VIA Header” setting, entering your public IP address.

2. July 1, 2025 at 6:41 PM UTCresolved

   This incident has been resolved.

1. June 23, 2025 at 6:37 PM UTCidentified

   One of Flowroutes Partner Carriers is having issues with outbound calling. This may affect outbound calling intermittently to certain domestic destinations. We will update as we receive updates.

2. June 23, 2025 at 7:17 PM UTCidentified

   Our Partner Carrier reports they have identified the issues and are putting a fix in place.

3. June 23, 2025 at 9:13 PM UTCidentified

   Our partner carrier reports they are continuing to work on a fix for this issue.

4. June 23, 2025 at 10:17 PM UTCmonitoring

   Our Partner has implemented a fix and the network is being monitored.

5. June 23, 2025 at 11:58 PM UTCresolved

   This incident has been resolved.

1. February 25, 2025 at 6:42 PM UTCinvestigating

   We are looking into reports of inbound SMS/MMS that are being rejected when handed off to 3CX webhooks.

2. February 25, 2025 at 7:54 PM UTCinvestigating

   We have reached out to the 3CX Team for investigation and will update this event as new information becomes available. At this time only 3CX webhooks are experiencing failures.

3. February 26, 2025 at 3:56 PM UTCinvestigating

   We are still actively working on the issues with failed SMS/MMS handoffs to 3CX Webhooks. Our in-house development team has been notified and is currently investigating the matter further. Additionally, we have provided updates to 3CX, as other customers not using 3CX PBX systems are not experiencing any issues with SMS/MMS handoffs. At this time, it appears the issue is only affecting 3CX PBX systems. We will provide an update as soon as we have more information.

4. February 26, 2025 at 6:43 PM UTCmonitoring

   We are receiving reports of completing messages through 3CX. We are continuing to work with them to ensure the issue is resolved.

5. February 27, 2025 at 4:12 PM UTCresolved

   This incident has been resolved.

1. February 15, 2025 at 12:44 AM UTCinvestigating

   Peering networks connecting traffic to local Canadian services have reported an outage with their network. They are aware of the issue and have deployed resources to investigate.

2. February 15, 2025 at 1:26 AM UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. February 15, 2025 at 3:43 AM UTCresolved

   This incident has been resolved.

1. January 15, 2025 at 4:11 PM UTCinvestigating

   We are actively collaborating with our peer networks to resolve the intermittent inbound call failures impacting AT&T customers, particularly in Southeast Florida, including the Miami and Melbourne areas. This issue appears to be localized to this region. We will continue to monitor the situation closely and provide updates as new information becomes available.

2. January 15, 2025 at 7:32 PM UTCinvestigating

   We are continuing to work with our peer networks to address this issue.

3. January 15, 2025 at 7:49 PM UTCidentified

   Our peer networks have identified the issue and are working on a fix.

4. January 15, 2025 at 9:04 PM UTCmonitoring

   A fix has been implemented by the upstream carrier, and we are currently monitoring the results.

5. January 15, 2025 at 10:22 PM UTCresolved

   This incident has been resolved.

1. January 14, 2025 at 3:01 PM UTCinvestigating

   We are actively working with our peer networks to address the intermittent inbound call failures affecting AT&T customers, specifically in Southeast Florida, including the Miami and Melbourne areas. This issue appears to be localized to that region. We will continue to monitor the situation and provide updates as we receive them.

2. January 14, 2025 at 4:00 PM UTCinvestigating

   We are continuing to work with our peer networks to address this issue.

3. January 14, 2025 at 5:04 PM UTCidentified

   Our peer networks have identified the issue and are working on a fix.

4. January 14, 2025 at 6:16 PM UTCmonitoring

   A fix has been implemented and we are monitoring the results.

5. January 14, 2025 at 7:48 PM UTCresolved

   This incident has been resolved.

1. September 27, 2024 at 5:14 PM UTCinvestigating

   We are investigating intermittent inbound call failures in the Dallas TX LATA 552.

2. September 27, 2024 at 7:20 PM UTCinvestigating

   We are continuing to work with our peer networks to investigate this issue.

3. September 27, 2024 at 7:38 PM UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. September 27, 2024 at 9:52 PM UTCresolved

   This incident has been resolved.

1. September 10, 2024 at 9:32 PM UTCinvestigating

   We are currently investigating an issue with the Flowroute Manage Portal providing 500 errors.

2. September 10, 2024 at 9:35 PM UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. September 10, 2024 at 11:13 PM UTCresolved

   This incident has been resolved.

1. July 18, 2024 at 5:01 PM UTCinvestigating

   We are currently investigating an issue with receiving email to [email protected].

2. July 18, 2024 at 5:21 PM UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. July 18, 2024 at 7:28 PM UTCresolved

   This incident has been resolved.

1. June 27, 2024 at 7:39 PM UTCinvestigating

   We are working with internal teams to identify an issue with the Flowroute support number 18553569768 that is providing a busy signal on inbound calls.

2. June 27, 2024 at 8:06 PM UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. June 28, 2024 at 12:44 AM UTCresolved

   This incident has been resolved.

1. January 17, 2024 at 9:31 PM UTCinvestigating

   Emergency Service Partners are currently investigating an issue that is preventing E911 profile requests from provisioning/updating. This does NOT impact 911 call routing.

2. January 17, 2024 at 10:42 PM UTCresolved

   This incident has been resolved.

1. January 9, 2024 at 10:12 PM UTCinvestigating

   We are currently investigating an issue with our ticketing system and are unable to send outbound email.

2. January 10, 2024 at 12:14 AM UTCidentified

   The issue has been identified and a fix is being implemented.

3. January 10, 2024 at 3:00 AM UTCmonitoring

   Email sending from our ticketing system has been restored. We will continue to monitor the situation.

4. January 11, 2024 at 1:42 PM UTCresolved

   This incident has been resolved.

1. December 11, 2023 at 9:53 PM UTCidentified

   We have been made aware of inbound calls failing to reach our network from AT&T due to a fiber cut in the Florida area. We are receiving updates from peering networks that are monitoring the situation and will provide an update here once we see movement on the matter.

2. December 12, 2023 at 5:34 PM UTCresolved

   This incident has been resolved.

1. November 8, 2023 at 4:56 PM UTCinvestigating

   We are reviewing the incident from yesterday where multiple Auto-Replenishments had been triggered and are working to understand the full scope of the event. We will provide further updates as we collect more information.

2. November 8, 2023 at 11:00 PM UTCidentified

   Our team is still investigating the full scope of this event. We expect to be reverting associated auto-replenishment charges that were triggered within the next 48 hours. Those reverted charges may take several business days for the reversal of those transactions to be visible on credit card reports. We thank you for your patience with this as we look to correct the issue that was experienced.

3. November 9, 2023 at 6:18 PM UTCresolved

   Our team has reinstated Auto-Replenishments and reverted the erroneous charges for applicable accounts. This incident did NOT affect all accounts. Email notifications have been sent to those accounts that will be receiving refunds. Please allow 5-7 business days for those transactions to be reflected on bank statements.

1. November 7, 2023 at 11:54 PM UTCinvestigating

   We are currently investigating an issue where duplicate auto-replenishment emails are being triggered.

2. November 8, 2023 at 12:59 AM UTCmonitoring

   Our team has implemented a fix to prevent further auto-replenishment notification triggers. We are monitoring and will provide more updates as they become available.

3. November 8, 2023 at 4:50 AM UTCresolved

   Operations have returned to normal.