Flowroute had 14 outages in the last 2 years totaling 278h 18m of downtime — averaging 0.6 incidents per month.
There were 14 Flowroute outages since June 27, 2024 totaling 278h 18m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are investigating reports of intermittent inbound call failures to Toll Free numbers.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating intermittent outbound one way audio.
A fix has been implemented and we are monitoring the results.
This issue has been fully resolved
We are currently investigating delays with our CDR exports in both the Manage portal and CDR export APIs.
A fix has been implemented and we are monitoring the results.
We are currently investigating new delays with our CDR exports.
This incident has been resolved.
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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
This incident has been resolved.
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.
Our Partner Carrier reports they have identified the issues and are putting a fix in place.
Our partner carrier reports they are continuing to work on a fix for this issue.
Our Partner has implemented a fix and the network is being monitored.
This incident has been resolved.
We are looking into reports of inbound SMS/MMS that are being rejected when handed off to 3CX webhooks.
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.
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.
We are receiving reports of completing messages through 3CX. We are continuing to work with them to ensure the issue is resolved.
This incident has been resolved.
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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
We are continuing to work with our peer networks to address this issue.
We are continuing to work with our peer networks to address this issue.
We are continuing to work with our peer networks to address this issue.
Our peer networks have identified the issue and are working on a fix.
A fix has been implemented by the upstream carrier, and we are currently monitoring the results.
This incident has been resolved.
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.
We are continuing to work with our peer networks to address this issue.
Our peer networks have identified the issue and are working on a fix.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are investigating intermittent inbound call failures in the Dallas TX LATA 552.
We are continuing to work with our peer networks to investigate this issue.
We are continuing to work with our peer networks to investigate this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating an issue with the Flowroute Manage Portal providing 500 errors.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating an issue with receiving email to [email protected].
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.