A tailored link.For complex setups.
Addressing, routing, multiple sites and SLA.
Describe your requirements
A short description is enough. It helps to include:
- addresses and the number of sites,
- the expected addressing or routing,
- support and SLA requirements.
We will reply with a proposed solution or technical follow-up questions.
Parameters matched to the deployment
Not every project needs every element. We match these parameters when a standard package does not describe the deployment.
- Throughput
- From needs, not a table
- A project may involve high throughput, but it may also be a lower-speed link with a subnet, SLA or routing that the standard package does not include.
- Addressing
- Single IPv4 · /29 · /28
- We match addressing for integrations, VPN, reverse DNS, own hosting or requirements of systems running on the client's side.
- Routing
- Multi-homing · BGP
- If the client's network needs own routing, a prefix or redundancy, BGP and multi-homing are defined as part of the project.
- Integration
- With the existing network
- We account for routers, addressing, service separation, monitoring and limitations on the client's infrastructure side.
- Multiple sites
- Many sites, one scope
- Each location may use a different access technology. The project aligns parameters, responsibility and support mode for the whole service.
- SLA
- Response and escalation
- Response parameters, service windows and escalation are written into the agreement after the service criticality is assessed.
Not every case needs a project
If a ready package at the address is enough, we do not complicate the process. An individual quote makes sense when technical parameters must be solved first.
An unusual parameter set
You need a parameter set that cannot be responsibly described as one ready package variant.
Fixed addressing
You require public addressing, a /29 or /28 subnet, reverse DNS or a fixed setup for an external system.
Production traffic
You run production traffic where throughput, latency, service windows or predictable escalation matter.
Several locations
You connect several locations and want one scope, even if different access technologies are available at each address.
A critical service
The service is operationally critical and response time must be contractual, not a general declaration.
Your own routing
Your infrastructure requires BGP, multi-homing, your own prefix or integration with existing routing.
From requirements to launch
Your requirements
You tell us where and what you need the connection for. A few sentences in the form are enough.
Location check
For each address we establish the available technology and, where needed, ask for technical details.
Quote and contract
Service parameters, response times and the scope of responsibility are set out in the offer and contract.
Launch and support
Once the contract is signed, we launch the service. You contact RFC directly about it.
Questions before a quote
Do I need to know the technical parameters?
No. Tell us where and what you need the connection for. We will agree addressing, routing or SLA together when preparing the quote.Can you serve locations in different towns?
We check availability separately for each address. Different technologies may be available at each one, and we agree the scope of services across all locations together.What if fibre is not available at the address?
The available technology depends on the location: FTTH fibre, a radio connection or wholesale access on partner networks.Where are the parameters and response times set out?
In the offer and contract. Response times, service windows and escalation are agreed once the service criticality is assessed.
Tell us what your business needs
Addresses and number of sites, addressing, routing or SLA — describe what you already know. We will work out the rest together.
Prefer to talk? Call our sales team:
+48 52 55 11 333