numbering identity · published

Troubleshooting calls that fail to ported numbers after cutover

Verified 2026-10-02 · 57 sources · tier 1–3

Also known as ported-number-not-receiving-calls, post-port-call-failures.

Zoom attributes calls that still route to the customer's old setup after a port to residual translations left in the losing carrier's network 56. In the US, FCC rules define the database method of number portability as one that uses 1 or more external databases to provide called-party routing information 5, and once a ported number is activated in the NPAC, real-time network downloads are sent from the NPAC to all Local Service Management Systems (LSMS) 20.

How post-port routing works

FCC rules define number portability as keeping existing numbers at the same location when switching carriers 18. Keeping a number while moving to a different location is defined separately as location portability 18.

A Location Routing Number (LRN) is a unique 10-digit telephone number assigned to each switch to support call routing to ported numbers 10.

Service providers submit subscription version information to the NPAC through the web Low Tech Interface, a mechanized Service Order Administration system, NPAC Help Desk requests, or a Service Bureau 21.

NPAC data is available to service providers and to providers of telecom-related services, for call rating, routing and billing 19.

Genesys describes port activation as the gaining carrier notifying the NPAC to activate the port, which is then broadcast to the industry network 6. Genesys states that for toll-free numbers the carrier instead updates the toll-free routing configuration 6.

Porting intervals and cutover timing

US FCC rules set these porting intervals 31 17:

Simple ports. Simple wireline-to-wireline and simple intermodal ports must be completed within 1 business day, unless the new provider or the customer requests a longer period 31.
Non-simple ports. Non-simple wireline-to-wireline and non-simple intermodal ports have a 4-business-day interval, unless a longer period is requested 17.

In the FCC porting-interval rule, intermodal ports include wireline-to-wireless ports, wireless-to-wireline ports, and ports involving interconnected VoIP service 8.

For the 1-business-day interval, a complete Local Service Request must arrive between 8 a.m. and 1 p.m. local time to count as received that business day 11. A request that arrives after 1 p.m. is treated as received at 8 a.m. the next business day 11. In this rule, "local time" means the predominant time zone of the NPAC region in which the number is ported 9.

Zoom Phone. US and Canada number ports activate at 11:30 AM Eastern Time, and that time cannot be changed 57.
Teams Calling Plan. US user numbers can target any port time from 8 am to 8 pm US Eastern 42. Canadian numbers and US toll-free numbers are scheduled at 11:30 am US Eastern unless a special request is made 42.
Bandwidth default and custom times. Port orders activate at 11:30 a.m. ET by default 1. A custom trigger time can be set from 5:00 a.m. to 10 p.m. ET, but times outside 8 a.m.-8 p.m. ET fall outside standard business hours 1.
Bandwidth porting guide. The guide gives a 6 am-10 pm ET activation window for domestic off-net ports 3. It gives an 11:30 am ET default for on-net, toll-free and complex ports 3.
Bandwidth manual activation. Customers can manually activate a port on the FOC day before the chosen activation time 2.
Genesys Cloud Voice. The standard DID porting schedule is Monday to Friday, 8:00 AM to 7:00 PM Eastern 7.
Telnyx. Telnyx states that numbers may port slightly later than the scheduled FOC time, particularly at high volumes 44.

Microsoft warns that choosing a late-day port time risks waiting until the next business day for a fix if the losing provider's help is needed, because some porting teams are only available until 5 pm Eastern 39.

The losing carrier's side of cutover

Lumen's port-out procedure includes these steps 14 12 15:

Trigger. Lumen, as the old provider, sets the 10-digit unconditional trigger no later than 11:59 PM the day before the port due date 14.
Activation. The new network service provider sends the activation to the NPAC on the due date and frame due time, and the NPAC broadcasts it to all service providers 12.
Removal. Disconnect and removal of the number's switch translations at Lumen is the last step, after NPAC activation and service order completion 15.

Lumen's documentation states that when a subscription arrives at the NPAC the t1 timer of 9 business hours starts, that a t2 timer of 9 business hours follows if it is not matched, and that the new provider may then activate on the due date without concurrence 13.

WarmTransfer's reading of the sources is that a window exists after activation, because removing the old provider's switch translations is a separate, later step 32. We infer that, during that window, calls that originate on the old provider's own switch can still terminate there, unless a 10-digit unconditional trigger forces a database query 32.

Zoom states that losing carriers have 24 hours to remove ported numbers 56. If calls still reach the old setup after 24 hours, or if faster resolution is wanted, Zoom advises asking the previous provider to remove the numbers from its network or switch 52.

For Teams Calling Plan ports, the losing provider releases the numbers to Microsoft on the firm order commitment date, and Microsoft directs them to the customer's tenant 37. Microsoft notes that, in rare cases, a losing service provider can override a firm order commitment it has already sent 38.

Number portability parameters in SIP signalling

RFC 4694 defines an 'rn' parameter and an 'npdi' parameter for the tel URI 28 26.

'rn' parameter. It carries the routing number for a telephone number that has been ported out from a donor carrier to another carrier 28.
'npdi' parameter. It tells downstream servers or switches that a number portability database dip has already been performed for the number 26.
Dip that returns a routing number. The node that performs the dip must add both 'rn' and 'npdi' 25.
Dip that returns no routing number. For example, for a non-ported geographic number, the node must still add 'npdi', without 'rn' 30.
Receiving 'npdi'. A network node that receives a tel URI containing 'npdi' must not retrieve number portability information for a geographic number again, even if it is configured to do so 27.
Trust. RFC 4694 states that these parameters are meant for use between call signalling entities that share a trust relationship 29.

Diagnosing failures by pattern

Pattern	Cited explanation
Calls still reach the old setup	Zoom attributes this to residual translations in the losing carrier's network 56.
Calls from some originating carriers reach the new provider while others reach the old one	WarmTransfer's reading of the sources is that this is consistent with those carriers not querying correctly on an N-1 basis, or not yet holding updated NPAC routing data, rather than with a missing activation 24.
The port activates correctly but inbound calls still fail on the new platform	WarmTransfer's reading of the sources is that the number may have no routing configured on the new side 4.

WarmTransfer's reading of the sources is that, across the vendors reviewed, the gaining platform expects numbers to be configured and routed on the new platform before the activation time 4.

Platform differences

Microsoft Teams

Before the port, Microsoft gives this advice 33 40:

Disable advanced call control features, such as call hunt or distinctive ring, at the current provider before the number port 33.
Do not arrange any service termination with the current provider until all porting activity is complete, because inactive or disconnected numbers cannot be ported 40.

For Teams Calling Plan ports in the US or Canada, numbers moving from Direct Routing or Operator Connect cannot be pre-assigned 43. An existing assignment can be kept if each number has a Calling Plan licence and an emergency location before port completion 43.

Microsoft documents these Direct Routing requirements 35 34 36:

Porting out of Direct Routing. Numbers moved by porting to another Teams PSTN connectivity option must be unassigned and released from Microsoft's number inventory with New-CsOnlineTelephoneNumberReleaseOrder before the port event 35.
Assigning a ported-in number. The number reaches a user only after it is assigned with Set-CsPhoneNumberAssignment using -PhoneNumberType DirectRouting, or the Teams admin center equivalent, which also enables Enterprise Voice 34.
Teams Only mode. Users must be in Teams Only mode for incoming calls to land in the Teams client 36.

Microsoft directs customers to report issues with ported numbers in the first 24-48 hours after port completion to the Phone Number Service Center, and issues after 48 hours to Microsoft Support 41.

Webex Calling

In Control Hub, the Activate Numbers Later option makes added numbers available for configuration immediately while deferring activation 49. It is intended for numbers that will be ported later 49. An inactive number that is already assigned to a user, workspace or feature stays inactive until an administrator activates it 51. Control Hub can bulk-activate up to 500 numbers at a time 50.

Zoom Phone

Zoom makes porting numbers available in the Zoom web portal on or before port day 55. It recommends pre-assigning them before the port so that they route on activation 55.

Zoom states that service must stay active with the current provider throughout the porting process 53. That service should be cancelled only after the transfer is confirmed complete 53. Zoom's 2026 porting guide recommends keeping legacy service running in parallel for at least 48 to 72 hours after each porting batch completes, as a fallback 54.

Twilio

Twilio's Port In API tracks each ported phone number through the statuses In Review, Waiting for Signature, Port Submitted, Port Pending, Port Rejected, Completed, Canceling and Canceled 46.

The API supports webhooks for port-in status updates 47. Twilio's page states that email notifications are not yet supported in the beta 47.

Telnyx

Telnyx recommends assigning a connection to numbers before the port, so that calls hit the assigned connection as soon as the numbers port to Telnyx 45.

Industry guidance

The Number Portability Industry Forum publishes these best practices 22 23:

Best Practice 075, "Response Interval Guidelines for End User Issues after Port Activation", dated 06/08/2022 22
Best Practice 078, "Service Outage Prevention and Mitigation", dated 09/13/2022 23

Applicability

Applies to: iconectiv NPAC, Lumen wholesale LNP (port-out), Zoom Phone, Microsoft Teams Calling Plans, Microsoft Teams Direct Routing, Cisco Webex Calling, Twilio Port In API, Bandwidth number porting, Telnyx number porting, and Genesys Cloud Voice. Deployments: multi-tenant, pstn, and sip. Sources checked 2026-10-02. The FCC porting-interval rules cited here are US rules 31 17. The SIP number portability parameters are defined in RFC 4694 28. The Zoom Phone port-time claim covers US and Canada number ports 57. The Teams Calling Plan port-time and pre-assignment claims cover US and Canadian numbers 42 43. Twilio's Port In API is described as a beta 47.

What remains uncertain

Unassigned numbers. What callers experience when a ported number is active at the carrier but not assigned on Teams Direct Routing, Webex Calling or Zoom Phone is not covered by the sources below.
24-hour removal norm. A primary regulatory or industry source for the 24-hour losing-carrier translation removal norm is not covered by the sources below.
E911 records. How E911 records are updated and tested after a port is not covered by the sources below.
SMS and NNID routing. SMS and NNID routing after a voice port completes is not covered by the sources below.
Multi-carrier testing. An authoritative method for testing a ported number from multiple originating carriers is not covered by the sources below.
Erroneous activation. An emergency snapback or port-back procedure for a port that activates in error is not covered by the sources below.
Toll-free routing. How toll-free post-port routing through the toll-free database and RespOrg change is completed and verified is not covered by the sources below.
CNAM. CNAM display that still shows the old name after a port is not covered by the sources below.

Sources

1
Bandwidth port orders activate at 11:30 a.m. ET by default, and a custom trigger time can be set from 5:00 a.m. to 10 p.m. ET, with times outside 8 a.m.-8 p.m. ET falling outside standard business hours.
Can I manually activate my port order or choose my own activation time? · Article body, activation time paragraphs · Checked 2026-10-02
2
Bandwidth customers can manually activate a port on the FOC day before the chosen activation time.
Can I manually activate my port order or choose my own activation time? · Article body, manual activation paragraph · Checked 2026-10-02
3
Bandwidth's porting guide gives a 6 am-10 pm ET activation window for domestic off-net ports and an 11:30 am ET default for on-net, toll-free and complex ports.
Bandwidth porting guide · Order Activation (Day of FOC) · Checked 2026-10-02
4
Across the vendors reviewed, the gaining platform expects numbers to be configured and routed on the new platform before the activation time, so a port that activates correctly can still fail inbound if the number has no routing on the new side.inferred
Porting In - Day of Port (FOC) · Day of port checks (connection assignment and internal systems ready) · Checked 2026-10-02
5
FCC rules define the database method of number portability as one that uses one or more external databases to provide called-party routing information.
47 CFR § 52.21 - Definitions · 47 CFR 52.21(e) · Checked 2026-10-02
6
Genesys describes port activation as the gaining carrier notifying the NPAC to activate the port, which is then broadcast to the industry network; for toll-free numbers the carrier instead updates the toll-free routing configuration.
Port numbers in US and Canada overview · Port activation section · Checked 2026-10-02
7
Genesys Cloud Voice's standard DID porting schedule is Monday to Friday, 8:00 AM to 7:00 PM Eastern.
Port numbers in US and Canada overview · Porting schedule section · Checked 2026-10-02
8
In the FCC porting-interval rule, intermodal ports include wireline-to-wireless, wireless-to-wireline and ports involving interconnected VoIP service.
47 CFR § 52.35 - Porting Intervals · 47 CFR 52.35(e) · Checked 2026-10-02
9
For the FCC porting-interval rule, 'local time' means the predominant time zone of the NPAC region in which the number is ported.
47 CFR § 52.35 - Porting Intervals · 47 CFR 52.35(e) · Checked 2026-10-02
10
A Location Routing Number (LRN) is a unique 10-digit telephone number assigned to each switch to support call routing to ported numbers.
General FAQs · FAQ: What is a LRN? · Checked 2026-10-02
11
For the one-business-day simple port interval, a complete Local Service Request must be received between 8 a.m. and 1 p.m. local time to count as received that business day; requests after 1 p.m. are treated as received at 8 a.m. the next business day.
47 CFR § 52.35 - Porting Intervals · 47 CFR 52.35(a) · Checked 2026-10-02
12
In Lumen's port-out procedure, the new network service provider sends the activation to the NPAC on the due date and frame due time, and the NPAC broadcasts it to all service providers.
LSR portal support · Order processing procedures, step 5 · Checked 2026-10-02
13
Lumen's documentation states that when a subscription arrives at the NPAC the t1 timer of 9 business hours starts; if it is not matched, a t2 timer of 9 business hours follows, after which the new provider may activate on the due date without concurrence.
LSR portal support · Order processing procedures, NPAC timer paragraph · Checked 2026-10-02
14
In Lumen's port-out procedure, Lumen as the old provider sets the 10-digit unconditional trigger no later than 11:59 PM the day before the port due date.
LSR portal support · Order processing procedures, step 4 · Checked 2026-10-02
15
In Lumen's port-out procedure, disconnect and removal of the number's switch translations at Lumen is the last step, after the NPAC activation and service order completion.
LSR portal support · Order processing procedures, steps 6-7 · Checked 2026-10-02
16
Under FCC rules each designated N-1 carrier is responsible for ensuring number portability database queries are performed on an N-1 basis, where N is the entity terminating the call.
47 CFR § 52.26 - NANC Recommendations on Local Number Portability Administration · 47 CFR 52.26(b) (N-1 query provision; paragraph number not confirmed in rendering) · Checked 2026-10-02
17
US FCC rules set a four-business-day porting interval for non-simple wireline-to-wireline and non-simple intermodal ports unless a longer period is requested.
47 CFR § 52.35 - Porting Intervals · 47 CFR 52.35(d) · Checked 2026-10-02
18
FCC rules define number portability as retaining existing numbers at the same location when switching carriers; keeping a number while moving location is defined separately as location portability.
47 CFR § 52.21 - Definitions · 47 CFR 52.21(m) and 52.21(k) · Checked 2026-10-02
19
NPAC data is made available to service providers and providers of telecom-related services for call rating, routing and billing.
General FAQs · FAQ: Who can receive NPAC data and what can it be used for? · Checked 2026-10-02
20
Once a ported number is activated in the NPAC, real-time network downloads are sent from the NPAC to all Local Service Management Systems (LSMS).
Porting and Access · How Porting Works section · Checked 2026-10-02
21
Service providers submit subscription version information to the NPAC through the web Low Tech Interface, a mechanized Service Order Administration system, NPAC Help Desk requests, or a Service Bureau.
Porting and Access · How Porting Works section · Checked 2026-10-02
22
The Number Portability Industry Forum publishes Best Practice 075, 'Response Interval Guidelines for End User Issues after Port Activation', dated 06/08/2022.
Number Portability Best Practices · Best practices index, BP 075 row · Checked 2026-10-02
23
The Number Portability Industry Forum publishes Best Practice 078, 'Service Outage Prevention and Mitigation', dated 09/13/2022.
Number Portability Best Practices · Best practices index, BP 078 row · Checked 2026-10-02
24
A pattern where calls from some originating carriers reach the new provider while others still reach the old one is consistent with those carriers not querying correctly on an N-1 basis or not yet holding the updated NPAC routing data, rather than with a missing activation.inferred
Porting and Access · How Porting Works section, combined with 47 CFR 52.26 N-1 provision · Checked 2026-10-02
25
Per RFC 4694, a node that performs the dip and retrieves a routing number must add both the 'rn' and the 'npdi' parameters to the tel URI.
RFC 4694: Number Portability Parameters for the "tel" URI · RFC 4694 Section 5.2.1 · Checked 2026-10-02
26
The RFC 4694 'npdi' tel URI parameter tells downstream servers or switches that a number portability database dip has already been performed for the number.
RFC 4694: Number Portability Parameters for the "tel" URI · RFC 4694 Section 1 · Checked 2026-10-02
27
Per RFC 4694, a network node receiving a tel URI that contains 'npdi' must not retrieve number portability information for a geographic number again, even if it is configured to do so.
RFC 4694: Number Portability Parameters for the "tel" URI · RFC 4694 Section 5.1 · Checked 2026-10-02
28
RFC 4694 defines an 'rn' parameter for the tel URI that carries the routing number associated with a telephone number that has been ported out from a donor carrier to another carrier.
RFC 4694: Number Portability Parameters for the "tel" URI · RFC 4694 Section 1 · Checked 2026-10-02
29
RFC 4694 states that the number portability tel URI parameters are meant for use between call signalling entities that share a trust relationship.
RFC 4694: Number Portability Parameters for the "tel" URI · RFC 4694 Section 5 · Checked 2026-10-02
30
Per RFC 4694, when a node performs the dip and no routing number is returned (for example a non-ported geographic number), it must still add 'npdi' without an 'rn' parameter.
RFC 4694: Number Portability Parameters for the "tel" URI · RFC 4694 Section 5.2.1 · Checked 2026-10-02
31
US FCC rules require simple wireline-to-wireline and simple intermodal ports to be completed within one business day unless the new provider or the customer requests a longer period.
47 CFR § 52.35 - Porting Intervals · 47 CFR 52.35(a) · Checked 2026-10-02
32
Because the old provider's removal of switch translations is a separate step that follows NPAC activation, there is a window after activation in which calls originating on the old provider's own switch can still terminate there unless a 10-digit unconditional trigger forces a database query.inferred
LSR portal support · Order processing procedures, steps 4-7 (reasoned from sequence) · Checked 2026-10-02
33
Microsoft advises having advanced call control features such as call hunt or distinctive ring disabled at the current provider before the number port.
What's a port order? - Microsoft Teams · Common mistakes · Checked 2026-10-02
34
For Teams Direct Routing, a ported-in number reaches a user only after it is assigned with Set-CsPhoneNumberAssignment using -PhoneNumberType DirectRouting (or the Teams admin center equivalent), which also enables Enterprise Voice.
Enable users for Direct Routing · Configure the phone number and enable enterprise voice > Use PowerShell · Checked 2026-10-02
35
When Direct Routing numbers are moved to another Teams PSTN connectivity option by porting, they must be unassigned and released from Microsoft's number inventory with New-CsOnlineTelephoneNumberReleaseOrder before the port event.
Enable users for Direct Routing · Upload Direct Routing numbers to your tenant > Order history > Note · Checked 2026-10-02
36
Direct Routing requires users to be in Teams Only mode for incoming calls to land in the Teams client.
Enable users for Direct Routing · Assign Teams Only mode to users to ensure calls land in Microsoft Teams · Checked 2026-10-02
37
For Teams Calling Plan ports, on the firm order commitment date the losing provider releases the numbers to Microsoft and Microsoft directs them to the customer's tenant.
What's a port order? - Microsoft Teams · What happens after you submit a port order request > Approval · Checked 2026-10-02
38
Microsoft notes that in rare cases a losing service provider can override a firm order commitment it has already sent.
What's a port order? - Microsoft Teams · What happens after you submit a port order request > Approval · Checked 2026-10-02
39
Microsoft warns that choosing a late-day port time risks waiting until the next business day for a fix if the losing provider's help is needed, because some porting teams are only available until 5 pm Eastern.
What's a port order? - Microsoft Teams · Plan for port event to process during business hours · Checked 2026-10-02
40
Microsoft advises against arranging any service termination with the current provider until all porting activity is complete, because inactive or disconnected numbers cannot be ported.
What's a port order? - Microsoft Teams · When to disconnect your existing phone lines with your current service provider · Checked 2026-10-02
41
Microsoft directs customers to report issues with ported numbers in the first 24-48 hours after port completion to the Phone Number Service Center, and issues after 48 hours to Microsoft Support.
Transfer phone numbers to Microsoft Teams · Report phone number issues · Checked 2026-10-02
42
For Teams Calling Plan ports, US user numbers can target any port time from 8 am to 8 pm US Eastern, while Canadian numbers and US toll-free numbers are scheduled at 11:30 am US Eastern unless a special request is made.
What's a port order? - Microsoft Teams · Plan for port event to process during business hours · Checked 2026-10-02
43
For Teams Calling Plan ports in the US or Canada, numbers moving from Direct Routing or Operator Connect cannot be pre-assigned, but an existing assignment can be kept if each number has a Calling Plan licence and emergency location before port completion.
Transfer phone numbers to Microsoft Teams · What's the status of your port orders? > Approved (FOCAccepted) row · Checked 2026-10-02
44
Telnyx states that numbers may port slightly later than the scheduled FOC time, particularly at high volumes.
Porting In - Day of Port (FOC) · Day of port article, activation timing paragraph · Checked 2026-10-02
45
Telnyx recommends assigning a connection to numbers before the port so that, as soon as they port to Telnyx, calls hit the assigned connection.
Port-In Best Practices · Port-In Best Practices, connection assignment paragraph · Checked 2026-10-02
46
Twilio's Port In API tracks each ported phone number through the statuses In Review, Waiting for Signature, Port Submitted, Port Pending, Port Rejected, Completed, Canceling and Canceled.
Port phone numbers using Twilio APIs · Port-in phone number statuses section · Checked 2026-10-02
47
Twilio's Port In API supports webhooks for port-in status updates, and the page states email notifications are not yet supported in the beta.
Port phone numbers using Twilio APIs · Webhooks section · Checked 2026-10-02
48
Under FCC rules a carrier that delivers an unqueried call to a ported number to a local exchange carrier's switch is expected to have performed the database query, and the LEC may block such an unqueried call only if performing the query is likely to impair network reliability.
47 CFR § 52.26 - NANC Recommendations on Local Number Portability Administration · 47 CFR 52.26(b) (unqueried-call provision; paragraph number not confirmed in rendering) · Checked 2026-10-02
49
In Webex Calling Control Hub, the Activate Numbers Later option makes added numbers available for configuration immediately while deferring activation, and is intended for numbers that will be ported later.
Manage phone numbers in Control Hub · Add phone numbers section, Activate Numbers Later · Checked 2026-10-02
50
Webex Calling Control Hub can bulk-activate up to 500 numbers at a time.
Manage phone numbers in Control Hub · Activate numbers section · Checked 2026-10-02
51
In Webex Calling, an inactive number that is already assigned to a user, workspace or feature remains inactive until an administrator activates it.
Manage phone numbers in Control Hub · Activate numbers section · Checked 2026-10-02
52
Zoom advises customers whose calls still reach the old setup after 24 hours, or who want faster resolution, to ask the previous provider to remove the numbers from its network or switch.
Best practices when porting numbers · FAQ: Why are my calls routing to my old setup after porting? · Checked 2026-10-02
53
Zoom states that service must remain active with the current provider throughout the porting process and should be cancelled only after confirmation that the transfer is complete.
Best practices when porting numbers · Best practices article, service-active guidance · Checked 2026-10-02
54
Zoom's 2026 porting guide recommends keeping legacy service in parallel for at least 48 to 72 hours after each porting batch completes as a fallback.
Number porting guide for IT teams: what to know in 2026 · Step-by-step process section · Checked 2026-10-02
55
Zoom makes porting numbers available in the Zoom web portal on or before port day and recommends pre-assigning them before the port so they route on activation.
Requesting a number port for US, Canada, or Puerto Rico · Port completion and number assignment section · Checked 2026-10-02
56
Zoom attributes calls that still route to the customer's old setup after a port to residual translations left in the losing carrier's network, and states that losing carriers have 24 hours to remove ported numbers.
Best practices when porting numbers · FAQ: Why are my calls routing to my old setup after porting? · Checked 2026-10-02
57
Zoom Phone's US and Canada number ports activate at 11:30 AM Eastern Time and that time cannot be changed.
Requesting a number port for US, Canada, or Puerto Rico · Port day and time section · Checked 2026-10-02

Documents

tier 1 standards and regulators

Cite this page

APA

WarmTransfer. (2026, October 2). Troubleshooting calls that fail to ported numbers after cutover. WarmTransfer. https://warmtransfer.net/knowledge/post-port-routing-troubleshooting

BibTeX

@misc{warmtransfer-post-port-routing-troubleshooting,
  title  = {Troubleshooting calls that fail to ported numbers after cutover},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/post-port-routing-troubleshooting},
  note   = {Verified 2026-10-02}
}