Files.com BYOIP Integration Overview
Provider Details
| Provider | Files.com |
| Category | Managed file transfer / cloud content delivery platform |
| BYOIP Availability | Enterprise plan customers only, by approval |
| Underlying Infrastructure | Amazon Web Services (customers authorize AWS ASNs 16509 and 14618 for the announced prefix) |
| Documentation | Files.com BYOIP Documentation |
Technical Requirements
| Minimum Prefix Size | /24 (256 IPs) per geographic region |
| IP Version Support | IPv4 only; IPv6 not publicly documented |
| RIR Registration | Must be registered with ARIN, RIPE, or APNIC |
| ROA Requirement | Required, published through the customer's RIR RPKI service, authorizing AWS ASNs 16509 and 14618 with max prefix length /24 |
| LOA Requirement | Not required; Files.com uses an RPKI-based process instead of an LOA |
| Additional Proof of Ownership | Customer generates an RSA 2048-bit key pair and self-signed X.509 certificate, published in the prefix's RDAP record |
| Exclusivity | Range must be dedicated entirely to Files.com and cannot be announced elsewhere during use |
Step-by-Step BYOIP Process
Step 1
Contact Files.com Support or your Account Manager to request BYOIP eligibility confirmation and range review.
Step 2
Files.com verifies IP ownership and technical criteria for the submitted range.
Step 3
Customer publishes the ROA and registry certificate (RDAP record) to authorize the required ASNs.
Step 4
Files.com deploys and provisions the range, sequencing any changeover to avoid dual announcements if the range was previously announced elsewhere.
Step 5
Testing and ongoing monitoring of the announced range, including routing health, DNS, and protocol-specific integrations.
Cost and Limitations
| Pricing | Additional charges apply; exact pricing not publicly documented |
| Plan Requirement | All participating sites must be on an Enterprise Plan |
| Minimum Allocation | /24 subnet (256 IPs) per geographic region |
| Address Binding | No per-service binding; each activated address serves all supported protocols (FTP, SFTP, FTPS, WebDAV, HTTPS) |
| Propagation Time | Up to 24 hours for ROA propagation |
Troubleshooting & Gotchas
- Files.com requires the ROA to authorize Amazon's ASNs (16509 and 14618) rather than a Files.com-specific ASN, reflecting that the platform runs on AWS infrastructure.
- There is no LOA document to sign; customers unfamiliar with RPKI/ROA workflows should expect a certificate-based proof-of-ownership process instead.
- A prefix already announced elsewhere must have that announcement withdrawn before Files.com can begin advertising it, and the changeover is sequenced to avoid simultaneous dual announcements.
- Customers should resolve Files.com endpoints by hostname rather than hardcoding IP addresses, since ongoing routing depends on the announced range.
Related Resources
Published 9 September 2026