История сбоев Flowroute

1. 3 октября 2026 г. в 00:23 UTCidentified

   Мы выявили проблему, затрагивающую систему выставления счетов. В результате некоторые расчетные операции с сентября могут быть не полностью отражены со всеми применимыми налогами, а последняя платежная ведомость временно недоступна. Наша инженерная команда активно работает над решением проблемы и восстановлением пострадавших сервисов. Последуют обновления.

2. 5 октября 2026 г. в 20:25 UTCresolved

   Инцидент урегулирован, сентябрьские заявления теперь доступны на портале Manage.

Автоматический перевод официального обновления инцидента.

1. 27 июля 2026 г. в 14:22 UTCinvestigating

   В настоящее время мы расследуем сообщения о сбоях в бесплатных звонках.

2. 27 июля 2026 г. в 14:40 UTCidentified

   Этот вопрос был определен, и в настоящее время осуществляется исправление.

3. 27 июля 2026 г. в 14:42 UTCmonitoring

   Было реализовано исправление, и наше первоначальное тестирование показывает, что оно исправлено. Мы продолжаем следить за результатами.

4. 27 июля 2026 г. в 15:51 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 14 мая 2026 г. в 15:45 UTCinvestigating

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

2. 14 мая 2026 г. в 15:49 UTCidentified

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

3. 14 мая 2026 г. в 15:54 UTCmonitoring

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

4. 14 мая 2026 г. в 16:55 UTCresolved

   This incident has been resolved.

1. 3 марта 2026 г. в 15:15 UTCinvestigating

   We are currently investigating intermittent outbound one way audio.

2. 3 марта 2026 г. в 15:19 UTCmonitoring

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

3. 3 марта 2026 г. в 17:20 UTCresolved

   This issue has been fully resolved

1. 11 февраля 2026 г. в 19:53 UTCinvestigating

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

2. 13 февраля 2026 г. в 20:09 UTCmonitoring

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

3. 17 февраля 2026 г. в 19:00 UTCinvestigating

   We are currently investigating new delays with our CDR exports.

4. 19 февраля 2026 г. в 17:23 UTCresolved

   This incident has been resolved.

1. 23 июля 2025 г. в 16:27 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. 23 июля 2025 г. в 18:45 UTCmonitoring

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

3. 23 июля 2025 г. в 20:16 UTCresolved

   This incident has been resolved.

1. 1 июля 2025 г. в 15:37 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. 1 июля 2025 г. в 18:41 UTCresolved

   This incident has been resolved.

1. 23 июня 2025 г. в 18:37 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. 23 июня 2025 г. в 19:17 UTCidentified

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

3. 23 июня 2025 г. в 21:13 UTCidentified

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

4. 23 июня 2025 г. в 22:17 UTCmonitoring

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

5. 23 июня 2025 г. в 23:58 UTCresolved

   This incident has been resolved.

1. 25 февраля 2025 г. в 18:42 UTCinvestigating

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

2. 25 февраля 2025 г. в 19:54 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. 26 февраля 2025 г. в 15:56 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. 26 февраля 2025 г. в 18:43 UTCmonitoring

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

5. 27 февраля 2025 г. в 16:12 UTCresolved

   This incident has been resolved.

1. 15 февраля 2025 г. в 00:44 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. 15 февраля 2025 г. в 01:26 UTCmonitoring

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

3. 15 февраля 2025 г. в 03:43 UTCresolved

   This incident has been resolved.

1. 15 января 2025 г. в 16:11 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. 15 января 2025 г. в 19:32 UTCinvestigating

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

3. 15 января 2025 г. в 19:49 UTCidentified

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

4. 15 января 2025 г. в 21:04 UTCmonitoring

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

5. 15 января 2025 г. в 22:22 UTCresolved

   This incident has been resolved.

1. 14 января 2025 г. в 15:01 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. 14 января 2025 г. в 16:00 UTCinvestigating

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

3. 14 января 2025 г. в 17:04 UTCidentified

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

4. 14 января 2025 г. в 18:16 UTCmonitoring

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

5. 14 января 2025 г. в 19:48 UTCresolved

   This incident has been resolved.

1. 27 сентября 2024 г. в 17:14 UTCinvestigating

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

2. 27 сентября 2024 г. в 19:20 UTCinvestigating

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

3. 27 сентября 2024 г. в 19:38 UTCmonitoring

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

4. 27 сентября 2024 г. в 21:52 UTCresolved

   This incident has been resolved.

1. 10 сентября 2024 г. в 21:32 UTCinvestigating

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

2. 10 сентября 2024 г. в 21:35 UTCmonitoring

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

3. 10 сентября 2024 г. в 23:13 UTCresolved

   This incident has been resolved.

1. 18 июля 2024 г. в 17:01 UTCinvestigating

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

2. 18 июля 2024 г. в 17:21 UTCmonitoring

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

3. 18 июля 2024 г. в 19:28 UTCresolved

   This incident has been resolved.

1. 27 июня 2024 г. в 19:39 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. 27 июня 2024 г. в 20:06 UTCmonitoring

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

3. 28 июня 2024 г. в 00:44 UTCresolved

   This incident has been resolved.

1. 17 января 2024 г. в 21:31 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. 17 января 2024 г. в 22:42 UTCresolved

   This incident has been resolved.

1. 9 января 2024 г. в 22:12 UTCinvestigating

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

2. 10 января 2024 г. в 00:14 UTCidentified

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

3. 10 января 2024 г. в 03:00 UTCmonitoring

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

4. 11 января 2024 г. в 13:42 UTCresolved

   This incident has been resolved.

1. 11 декабря 2023 г. в 21:53 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. 12 декабря 2023 г. в 17:34 UTCresolved

   This incident has been resolved.

1. 8 ноября 2023 г. в 16:56 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. 8 ноября 2023 г. в 23:00 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. 9 ноября 2023 г. в 18:18 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.