Flowroute 장애 기록

1. 2026년 10월 3일 오전 12:23 UTCidentified

   우리는 청구 시스템에 영향을 미치는 문제점을 발견했습니다. 그 결과, 9 월의 특정 청구 거래는 모든 적용 가능한 세금과 완전히 반영되지 않으며, 최신 청구서는 일시적으로 사용할 수 없습니다. 우리의 엔지니어링 팀은 문제를 해결하고 영향을받는 서비스를 복원하기 위해 적극적으로 노력하고 있습니다. 업데이트가 따릅니다.

2. 2026년 10월 5일 오후 8:25 UTCresolved

   사건은 해결되었습니다, 9 월 문은 현재 관리 포털에서 사용할 수 있습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 27일 오후 2:22 UTCinvestigating

   우리는 현재 inbound toll 무료 통화에 실패의 보고서를 조사하고 있습니다.

2. 2026년 7월 27일 오후 2:40 UTCidentified

   문제는 식별되고 수정이 구현됩니다.

3. 2026년 7월 27일 오후 2:42 UTCmonitoring

   수정이 시행되었고 초기 테스트는 수정되었습니다. 우리는 결과를 감시하는 것을 계속합니다.

4. 2026년 7월 27일 오후 3:51 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 5월 14일 오후 3:45 UTCinvestigating

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

2. 2026년 5월 14일 오후 3:49 UTCidentified

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

3. 2026년 5월 14일 오후 3:54 UTCmonitoring

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

4. 2026년 5월 14일 오후 4:55 UTCresolved

   This incident has been resolved.

1. 2026년 3월 3일 오후 3:15 UTCinvestigating

   We are currently investigating intermittent outbound one way audio.

2. 2026년 3월 3일 오후 3:19 UTCmonitoring

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

3. 2026년 3월 3일 오후 5:20 UTCresolved

   This issue has been fully resolved

1. 2026년 2월 11일 오후 7:53 UTCinvestigating

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

2. 2026년 2월 13일 오후 8:09 UTCmonitoring

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

3. 2026년 2월 17일 오후 7:00 UTCinvestigating

   We are currently investigating new delays with our CDR exports.

4. 2026년 2월 19일 오후 5:23 UTCresolved

   This incident has been resolved.

1. 2025년 7월 23일 오후 4: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. 2025년 7월 23일 오후 6:45 UTCmonitoring

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

3. 2025년 7월 23일 오후 8:16 UTCresolved

   This incident has been resolved.

1. 2025년 7월 1일 오후 3: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. 2025년 7월 1일 오후 6:41 UTCresolved

   This incident has been resolved.

1. 2025년 6월 23일 오후 6: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. 2025년 6월 23일 오후 7:17 UTCidentified

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

3. 2025년 6월 23일 오후 9:13 UTCidentified

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

4. 2025년 6월 23일 오후 10:17 UTCmonitoring

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

5. 2025년 6월 23일 오후 11:58 UTCresolved

   This incident has been resolved.

1. 2025년 2월 25일 오후 6:42 UTCinvestigating

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

2. 2025년 2월 25일 오후 7: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. 2025년 2월 26일 오후 3: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. 2025년 2월 26일 오후 6: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. 2025년 2월 27일 오후 4:12 UTCresolved

   This incident has been resolved.

1. 2025년 2월 15일 오전 12: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. 2025년 2월 15일 오전 1:26 UTCmonitoring

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

3. 2025년 2월 15일 오전 3:43 UTCresolved

   This incident has been resolved.

1. 2025년 1월 15일 오후 4: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. 2025년 1월 15일 오후 7:32 UTCinvestigating

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

3. 2025년 1월 15일 오후 7:49 UTCidentified

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

4. 2025년 1월 15일 오후 9:04 UTCmonitoring

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

5. 2025년 1월 15일 오후 10:22 UTCresolved

   This incident has been resolved.

1. 2025년 1월 14일 오후 3: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. 2025년 1월 14일 오후 4:00 UTCinvestigating

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

3. 2025년 1월 14일 오후 5:04 UTCidentified

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

4. 2025년 1월 14일 오후 6:16 UTCmonitoring

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

5. 2025년 1월 14일 오후 7:48 UTCresolved

   This incident has been resolved.

1. 2024년 9월 27일 오후 5:14 UTCinvestigating

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

2. 2024년 9월 27일 오후 7:20 UTCinvestigating

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

3. 2024년 9월 27일 오후 7:38 UTCmonitoring

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

4. 2024년 9월 27일 오후 9:52 UTCresolved

   This incident has been resolved.

1. 2024년 9월 10일 오후 9:32 UTCinvestigating

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

2. 2024년 9월 10일 오후 9:35 UTCmonitoring

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

3. 2024년 9월 10일 오후 11:13 UTCresolved

   This incident has been resolved.

1. 2024년 7월 18일 오후 5:01 UTCinvestigating

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

2. 2024년 7월 18일 오후 5:21 UTCmonitoring

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

3. 2024년 7월 18일 오후 7:28 UTCresolved

   This incident has been resolved.

1. 2024년 6월 27일 오후 7: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. 2024년 6월 27일 오후 8:06 UTCmonitoring

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

3. 2024년 6월 28일 오전 12:44 UTCresolved

   This incident has been resolved.

1. 2024년 1월 17일 오후 9: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. 2024년 1월 17일 오후 10:42 UTCresolved

   This incident has been resolved.

1. 2024년 1월 9일 오후 10:12 UTCinvestigating

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

2. 2024년 1월 10일 오전 12:14 UTCidentified

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

3. 2024년 1월 10일 오전 3:00 UTCmonitoring

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

4. 2024년 1월 11일 오후 1:42 UTCresolved

   This incident has been resolved.

1. 2023년 12월 11일 오후 9: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. 2023년 12월 12일 오후 5:34 UTCresolved

   This incident has been resolved.

1. 2023년 11월 8일 오후 4: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. 2023년 11월 8일 오후 11: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. 2023년 11월 9일 오후 6: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.