Source note · Troubleshooting number port rejections
The multi-day lead times that cloud platforms impose on port-ins (for example Twilio's 7-day minimum) are platform policy layered on the FCC's one-business-day simple-port interval; they are not the regulatory porting interval.
inferred · Checked 2026-10-01
- Vendor
- not restricted
- Product
- not restricted
- Subsystem
- lnp-porting-interval
- Deployment
- multi-tenant
- Region
- us
- Release range
- current as of 2026-10-01
- Status
- inferred
- Checked
- 2026-10-01
Sources
- 47 CFR § 52.35 - Porting Intervals — Legal Information Institute (Cornell Law School), reproducing the Code of Federal Regulations · tier 1 standards and regulators · 47 CFR 52.35(a) read with Twilio PortIn target_port_in_date
Cite this note
APA
WarmTransfer. (2026, October 1). Troubleshooting number port rejections: source note number-port-rejections-platform-lead-times-not-fcc-interval. WarmTransfer. https://warmtransfer.net/knowledge/claims/number-port-rejections-platform-lead-times-not-fcc-interval
BibTeX
@misc{warmtransfer-claim-number-port-rejections-platform-lead-times-not-fcc-interval,
title = {Troubleshooting number port rejections: source note number-port-rejections-platform-lead-times-not-fcc-interval},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/number-port-rejections-platform-lead-times-not-fcc-interval},
note = {Source note number-port-rejections-platform-lead-times-not-fcc-interval, checked 2026-10-01}
}