
The Covered List Has a Working Door — Two Taiwan-Linked Router Makers Just Walked Through It
September 9, 2026
On September 9, 2026 the FCC's Public Safety and Homeland Security Bureau released DA 26-957, announcing that the Department of War granted Conditional Approvals to named router products from ASUS Computer International and Comtrend Corporation, effective September 9, 2026 through March 6, 2028. The identified equipment is now excluded from the Covered List's foreign-produced-router restriction. The approvals are entity- and product-specific, and they do not replace ordinary FCC equipment authorization.
1. Named products from two Taiwan-linked router makers received Conditional Approval
On September 9, 2026, the FCC's Public Safety and Homeland Security Bureau (PSHSB) released Public Notice DA 26-957, announcing that the Department of War (DoW) has granted Conditional Approvals for the following equipment, which is therefore exempt from the Covered List:
- ASUS Computer International's RT Router Series, ROG GT Series, ROG Strix GS Series, TUF Gaming Series, ExpertWiFi Series, ZenWiFi Mesh Series, 5G MiFi Series, repeaters, and wireless access points.
- Comtrend Corporation's GRG-4366u, VG-8043u, PBL-6201, and NL-3131 wireless routers.
Both approvals run for the same term: September 9, 2026 through March 6, 2028. The FCC has updated the Covered List accordingly, excluding this identified equipment from the foreign-produced-router restriction for the duration of the approval period. The same notice also carries an approval in the advanced-robotic-devices category, which is a separate class of equipment and does not touch networking product lines.
The background matters. On March 23, 2026 the Commission added "routers produced in a foreign country" to the Covered List, based on a National Security Determination from an Executive Branch interagency body. That structure is worth noting in its own right: the Covered List has historically operated on named producers and named services, while this entry sweeps in an entire class by place of production — a far wider net than naming a single company.
But the same entry carved out an exception in the same breath: except routers granted a Conditional Approval by DoW or DHS. The door was written into the rule from the start. What DA 26-957 supplies is the evidence that it opens — twice, in a single notice.
2. Legal status: this clears the Covered List barrier, not equipment authorization
Getting this wrong misallocates real budget, so it is worth stating plainly.
A Conditional Approval addresses the barrier created by the Covered List. Once equipment falls within the Covered List's scope, it cannot obtain FCC equipment authorization under current Commission rules, and the US market closes in practical terms. A Conditional Approval removes the identified equipment from that class restriction for the term of the approval, and that barrier lifts.
What it does not do is complete the equipment authorization itself. Ordinary FCC certification, obtaining and maintaining an FCC ID, and conformity testing against the technical standards remain a separate and still-required track. A Conditional Approval neither replaces nor shortens it. The accurate mental model is two sequential gates: first establish that the product is not shut out by the Covered List, then complete equipment authorization on its own terms. The two sit under different authorities, different legal bases, different filing processes and different review standards. Fail either one and the product cannot lawfully be marketed in the United States. In planning terms, that means two timelines to estimate separately, not one blended "certification schedule."
The term is the other thing to hold onto. These approvals terminate on March 6, 2028. That is a status with a defined end date, not a permanent qualification earned once. Treating it as something to be maintained — and eventually re-examined — is the more durable assumption.
3. What this means for Taiwanese networking manufacturers
The signal here is structural. A class-wide restriction keyed to place of production looks like a door closed on an entire industry. It is not. The exception written into the rule is genuinely passable, and there is now a concrete, current, verifiable precedent that it has been used. For manufacturers who have treated the foreign-produced-router restriction as irreversible — and who have taken a defensive posture on US market planning as a result — that premise needs updating.
The limits of the precedent are equally clear, and over-reading them would be a mistake. Approvals are granted case by case, company by company, product by product. This is not a green light across a brand's full catalog, and it is certainly not a blanket clearance for Taiwanese OEM/ODM products generally. The structure of the notice says so directly: the subject is a named legal entity, the scope is named product families and models, and the term has specified start and end dates. A model that was not listed does not benefit simply because it shares a brand.
So before any firm assumes its own eligibility, several specific questions need answering. Which legal entity should be the applicant — the Taiwan parent, a US subsidiary, or the entity that actually holds the grantee code? That choice also determines who carries the maintenance obligation afterward. Which product families and models should be in scope, and how does that scope map onto existing FCC IDs and grantee codes? Draw it too narrowly and volume models fall outside the approval; draw it too broadly and review lengthens while more material has to be substantiated. And would the same model in a different production configuration — a different manufacturing site, a different contract-manufacturing arrangement — be treated as a distinct subject? That is a judgment to make before filing, not to discover after.
The last question is usually the real bottleneck: whether firmware, bill-of-materials, component-sourcing and production-location evidence is organized well enough to support a substantive review. The core of that review is a demonstration that the product does not pose a national security risk, and a demonstration has to rest on verifiable technical and supply-chain documentation — narrative does not carry it. Most manufacturers do hold this material. It is simply distributed across procurement, R&D, quality and manufacturing, at inconsistent granularity and versioning, and has never been assembled into a form an external reviewer can read. That gap routinely takes longer to close than the filing itself, and it is the hardest thing to close under deadline pressure.
There is a commercial dimension too. Once a pathway is demonstrably workable, it stops being purely a regulatory matter and starts entering commercial conversations: US-side brand customers, channel partners and system integrators evaluating suppliers can reasonably be expected to start asking how Covered List status is handled, whether an approval is in place, and which models it covers. Being able to answer that clearly becomes a differentiator in itself. Starting the inventory when a customer first asks is generally already late.
Primary sources:
Conclusion
The Covered List remains the most direct structural constraint on Taiwanese networking products entering the US market. What DA 26-957 establishes is that the constraint comes with a workable door, and that the door has now been used twice in a single notice. This is not a blanket clearance, and it changes nothing about the equipment authorization requirement itself — but it is a verifiable, current precedent. It moves the question from "can this path be walked at all" to "which legal entity, which products, and which evidence should actually be inside the application."
About this briefing
Vantikon tracks US regulatory developments that reach Taiwanese manufacturers, their product lines and their supply chains, and helps translate developments like this one into product-level readiness: identifying which entities and models are affected, inventorying and organizing technical and supply-chain evidence, and scoping what an application would reasonably cover — so that later exchanges with qualified advisors or with the agencies themselves rest on facts already in order. We are an advisory and readiness partner, not a law firm and not a certifying body; we do not file on a client's behalf and we do not render legal opinions. If something here touches your product line or your US market planning, get in touch — we are glad to have the conversation.
This briefing is informational and does not constitute legal advice; consult qualified counsel for your specific situation.
