# Possible Fire OS networking issue: repeated mDNS AAAA queries (~2,600 mDNS packets/sec) can overload entire local networks **URL:** \ **Category:** Q&A\ **Tags:** appstore-fire-tv\ **Created:** [July 27, 2026, 4:01pm UTC](https://community.amazondeveloper.com/t/possible-fire-os-networking-issue-repeated-mdns-aaaa-queries-2-600-mdns-packets-sec-can-overload-entire-local-networks/28820 "2026-07-27T16:01:25Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![Mike\_Leck](https://avatars.discourse-cdn.com/v4/letter/m/ecc23a/32.png) [@Mike\_Leck](https://community.amazondeveloper.com/u/Mike_Leck)\ **Post date:** [July 27, 2026, 4:01pm UTC](https://community.amazondeveloper.com/t/possible-fire-os-networking-issue-repeated-mdns-aaaa-queries-2-600-mdns-packets-sec-can-overload-entire-local-networks/28820/1 "2026-07-27T16:01:25Z")
Hello, while investigating unexpected multicast traffic in my home network, I isolated what appears to be a reproducible networking issue originating from an Amazon Fire TV Stick 4K Max. The issue does not only affect the Fire TV itself. In my environment, it generated approximately 2,600 mDNS multicast packets per second and significantly affected the stability of the entire local network. Several older embedded and low-performance devices became overloaded by the sustained multicast traffic and were partially or completely unable to operate normally until the traffic stopped. I would like to know whether this behavior is already known to the Fire OS engineering team and whether additional diagnostic information would be helpful. ## Device Device: Amazon Fire TV Stick 4K Max Fire OS: 7.7.1.3 (PS7713/5443) Fire TV Home Version: 7280112.1 ## Network connection The Fire TV is normally connected via Ethernet using the official Amazon Ethernet Adapter for Fire TV. However, the behavior is not specific to Ethernet or to the Ethernet adapter. I explicitly reproduced the same issue while the Fire TV was connected directly via Wi-Fi. The observed mDNS behavior and its impact on the local network were the same with both connection types. Tested connection types: - Ethernet via the official Amazon Ethernet Adapter for Fire TV - Direct Wi-Fi connection Gateway / DNS: 192.168.0.1 The Fire TV is the only device on my network exhibiting this specific behavior. ## Observed behavior The Fire TV continuously transmits mDNS (Multicast DNS) AAAA queries for hostnames within the \*.fritz.box domain. Examples observed include: - fritz-box.fritz.box. - fritzbox-ug.fritz.box. When no device responds to these AAAA queries, the Fire TV continues sending them repeatedly. During my measurements, the resulting multicast traffic reached approximately 2,600 mDNS packets per second on the local network. Because mDNS is multicast traffic, the packets are distributed throughout the relevant local broadcast domain rather than affecting only the Fire TV itself. The sustained traffic significantly affected the entire local network. Several older embedded and low-performance devices became overloaded, partially or completely unresponsive, and were unable to maintain normal operation until the multicast traffic stopped. ## Investigation To better understand and isolate the behavior, I implemented a minimal mDNS responder that answers only the relevant AAAA queries from the Fire TV. The responder returns a single valid IPv6 link-local address for the requested hostname. Immediately after the Fire TV receives a valid AAAA response: - the repeated AAAA mDNS queries stop immediately - multicast traffic returns to normal - affected devices recover and resume normal operation - the Fire TV itself continues operating normally When the responder is disabled and the cached response expires, the repeated AAAA queries begin again. This behavior is fully reproducible. The test was successfully reproduced with both: - Ethernet via the official Amazon Ethernet Adapter for Fire TV - Wi-Fi without the Ethernet adapter This makes an issue limited to the Ethernet adapter or its connection unlikely. ## Technical conclusion Based on these experiments, the Fire TV appears to correctly accept and cache a valid mDNS AAAA response. However, when no AAAA response is available, the device appears to retransmit the queries continuously or at an excessive rate without a reasonable retry backoff. The fact that a single valid AAAA response immediately terminates the repeated traffic strongly suggests that the behavior is triggered by the absence of an mDNS AAAA response rather than by general network instability. From my perspective, this is not merely a cosmetic networking issue. The resulting multicast rate is capable of significantly degrading the stability of an otherwise normally operating local network and can overload older or lower-performance network devices. ## Diagnostics available I have collected the following diagnostic material: - packet captures showing the mDNS traffic - packet captures before and after enabling the workaround - measured traffic statistics - responder statistics - Fire TV device and software information - network topology - source code of the minimal mDNS responder used during testing I would be happy to provide this material or perform additional tests if it would help the Fire OS engineering team reproduce and diagnose the issue. ## Questions for the Fire OS engineering team 1. Is this mDNS retry behavior expected? 2. Is there a known Fire OS issue involving repeated mDNS AAAA queries when no responder is available? 3. Would packet captures and the minimal reproduction setup be useful for further investigation? 4. Is there an official channel through which I should submit the complete diagnostic package? Thank you for your time. ---
**Author:** ![Emma](https://dhm3gbtzu79o6.cloudfront.net/user_avatar/community.amazondeveloper.com/emma/32/880_2.png) [@Emma](https://community.amazondeveloper.com/u/Emma)\ **Post date:** [July 28, 2026, 7:59am UTC](https://community.amazondeveloper.com/t/possible-fire-os-networking-issue-repeated-mdns-aaaa-queries-2-600-mdns-packets-sec-can-overload-entire-local-networks/28820/3 "2026-07-28T07:59:44Z")
Hi, Thanks for posting. We have messaged the appropriate team for further investigation and will let you know once we receive an update. ---
**Author:** ![boo50](https://avatars.discourse-cdn.com/v4/letter/b/c4cdca/32.png) [@boo50](https://community.amazondeveloper.com/u/boo50)\ **Post date:** [August 23, 2026, 11:19am UTC](https://community.amazondeveloper.com/t/possible-fire-os-networking-issue-repeated-mdns-aaaa-queries-2-600-mdns-packets-sec-can-overload-entire-local-networks/28820/4 "2026-08-23T11:19:02Z")
Hi, I’m following up on this issue, as it has now been 26 days since the last update. You mentioned that the appropriate team had been contacted for further investigation and that you would provide an update once you received further information. Unfortunately, there hasn’t been any update so far. I’m also affected by this issue and I’m very interested in finding out what is causing the problem and whether a solution is being worked on. Could you please let us know if there has been any progress or whether the issue is still under investigation? Thank you! ---
**Author:** ![Joseph\_Madden](https://avatars.discourse-cdn.com/v4/letter/j/dc4da7/32.png) [@Joseph\_Madden](https://community.amazondeveloper.com/u/Joseph_Madden)\ **Post date:** [September 21, 2026, 7:49am UTC](https://community.amazondeveloper.com/t/possible-fire-os-networking-issue-repeated-mdns-aaaa-queries-2-600-mdns-packets-sec-can-overload-entire-local-networks/28820/5 "2026-09-21T07:49:55Z")
@Emma Has there been any update to this? I also seem to get the same issue I have a wire shark trace which I’ve attached which shows the issue. > **[wireshark1.pcap](https://drive.google.com/file/d/1fOuFh_lpXBNiNOt5ehDFKy0MlEEelcRS/view?usp=sharing)** > > Google Drive file. It seems to happen when the fire stick goes to idle. I’ve factory reset the fire stick and install Plezzy Plex TivyMate SmartTube Beta and the issue reoccours within one day. @Mike_Leck Do either of you have these apps installed? ---
**Author:** ![Joseph\_Madden](https://avatars.discourse-cdn.com/v4/letter/j/dc4da7/32.png) [@Joseph\_Madden](https://community.amazondeveloper.com/u/Joseph_Madden)\ **Post date:** [September 21, 2026, 8:30am UTC](https://community.amazondeveloper.com/t/possible-fire-os-networking-issue-repeated-mdns-aaaa-queries-2-600-mdns-packets-sec-can-overload-entire-local-networks/28820/6 "2026-09-21T08:30:47Z")
Also - Just to add another thing that might be unique is that I’m using the amazon Ethernet adaptor rater than WIFI. ---
**Author:** ![Sam\_K](https://avatars.discourse-cdn.com/v4/letter/s/3ab097/32.png) [@Sam\_K](https://community.amazondeveloper.com/u/Sam_K)\ **Post date:** [October 9, 2026, 4:29pm UTC](https://community.amazondeveloper.com/t/possible-fire-os-networking-issue-repeated-mdns-aaaa-queries-2-600-mdns-packets-sec-can-overload-entire-local-networks/28820/7 "2026-10-09T16:29:53Z")
I have the same problem with my Fire Cube. I’m also using the Ethernet adapter and wifi is disabled. The FireCube hits my desktop PC so hard I lose internet connectivity, local RDP barely works, etc. ---
**Author:** ![Mike\_Leck](https://avatars.discourse-cdn.com/v4/letter/m/ecc23a/32.png) [@Mike\_Leck](https://community.amazondeveloper.com/u/Mike_Leck)\ **Post date:** [October 26, 2026, 7:17am UTC](https://community.amazondeveloper.com/t/possible-fire-os-networking-issue-repeated-mdns-aaaa-queries-2-600-mdns-packets-sec-can-overload-entire-local-networks/28820/8 "2026-10-26T07:17:06Z")
Hi @Emma, I would like to follow up on this issue, as almost three months have passed without a substantive update from Amazon’s engineering team. I own **two identical Fire TV Sticks, and both exhibit the same problematic behavior** , over both Ethernet and Wi-Fi. I also want to explain the real impact this issue has had on me. **This problem has cost me years of troubleshooting, considerable money, and an enormous amount of frustration.** When I originally purchased the Fire TV Stick, the problem was barely noticeable. However, as my home network and infrastructure grew over the years, the excessive mDNS traffic became an increasingly serious issue, causing network instability and latency problems that were extremely difficult to diagnose. I replaced network switches, repeatedly investigated and modified various software systems and applications, and spent countless hours trying to eliminate performance issues and unexpected delays. I invested enormous amounts of time optimizing, reconfiguring, and troubleshooting systems that I believed were responsible for these problems — without realizing that the actual trigger was an entirely different device on my network. **For years, I was trying to fix problems in software and infrastructure that were actually symptoms of the excessive network traffic triggered by the Fire TV Stick.** It ultimately took extensive packet captures, network monitoring, and AI-assisted technical analysis to identify the Fire TV Stick as the trigger. **Years of troubleshooting because of a problem originating from a consumer streaming device.** And the issue is still present. On October 25, 2026, my monitoring system recorded another critical mDNS storm: - **41,969 mDNS packets in just 15 seconds** - Approximately **2,798 mDNS packets per second** - The affected Fire TV Stick (`XXX.168.3.50`) identified as the leading source IP - Its previously identified MAC address accounted for 65.42% of the captured traffic The total packet count includes network-wide traffic, but our earlier investigations identified the Fire TV device as the trigger. Other users have now reported similar issues, including with a Fire TV Cube. This is clearly not an isolated incident. I am not expecting Amazon to undo the years I have spent investigating this. But I do expect the company to take responsibility for investigating a problem that can seriously affect an entire home network. **Could Amazon please provide a concrete engineering update? Has the issue been reproduced, is a firmware fix being developed, and when can affected customers expect a solution?** After nearly three months, I believe a substantive technical response is long overdue. Thank you, Mike ---
**Author:** ![Emma](https://dhm3gbtzu79o6.cloudfront.net/user_avatar/community.amazondeveloper.com/emma/32/880_2.png) [@Emma](https://community.amazondeveloper.com/u/Emma)\ **Post date:** [October 29, 2026, 7:26am UTC](https://community.amazondeveloper.com/t/possible-fire-os-networking-issue-repeated-mdns-aaaa-queries-2-600-mdns-packets-sec-can-overload-entire-local-networks/28820/9 "2026-10-29T07:26:07Z")
Hi @Mike_Leck , Thank you for the detailed reports and captures. We’ve re-escalated it to the engineering team along with your data. We’ll post here when we have an update. ---
**Author:** ![LSO](https://avatars.discourse-cdn.com/v4/letter/l/67e7ee/32.png) [@LSO](https://community.amazondeveloper.com/u/LSO)\ **Post date:** [October 30, 2026, 9:50am UTC](https://community.amazondeveloper.com/t/possible-fire-os-networking-issue-repeated-mdns-aaaa-queries-2-600-mdns-packets-sec-can-overload-entire-local-networks/28820/11 "2026-10-30T09:50:20Z")
Dear @Emma, thanks for re-escalating this issue. As it has been more than 3 months since the first post was made and no update addressing the bug has been made available yet, I think a reaction from amazon should be incoming rather sooner than later. Especially as the current situation seriously impacts the general usability of the Fire TV products, providing a fix asap is in amazon’s best interest. So maybe there should be a high prio response. Thanks for your efforts, Lars ---
**Author:** ![ceh](https://avatars.discourse-cdn.com/v4/letter/c/5fc32e/32.png) [@ceh](https://community.amazondeveloper.com/u/ceh)\ **Post date:** [October 31, 2026, 10:38am UTC](https://community.amazondeveloper.com/t/possible-fire-os-networking-issue-repeated-mdns-aaaa-queries-2-600-mdns-packets-sec-can-overload-entire-local-networks/28820/12 "2026-10-31T10:38:14Z")
I decided to stop investing into any new Amazon Echo, Amazon Fire, and related products until this bug is resolved. The bug severely affects my home network to the point that I am considering to retire all affected Amazon products. ---
**Author:** ![Steven\_Goossens](https://avatars.discourse-cdn.com/v4/letter/s/ea5d25/32.png) [@Steven\_Goossens](https://community.amazondeveloper.com/u/Steven_Goossens)\ **Post date:** [November 1, 2026, 10:57am UTC](https://community.amazondeveloper.com/t/possible-fire-os-networking-issue-repeated-mdns-aaaa-queries-2-600-mdns-packets-sec-can-overload-entire-local-networks/28820/13 "2026-11-01T10:57:03Z")
Same issue here. I have 6 echo devices 1 fire tv. Currently it seem te be my echo spots who generate the issue, been having this for a long time with ups and downs. Last 2 weeks it has been extremely worse. Seems to be a combination of things here that increase the issue. It helped to find where it originated and then found this thread that confirms my findings. Hoping for a fix from amazon soon, or this could be the final push for me to throw all amazon devices out.