Physical route diversity
Ask how circuits reach the building, where routes separate and which access-network dependencies remain shared.
Diverse access & internet continuity · Designed around your business
A second route.
A stronger continuity plan.
Explore diverse fibre and supported failover around the faults your site needs to tolerate and the work that must continue.
Scope agreed around your business · One point of contact
Resilience around your siteRoutes · Equipment · Applications
RO2 failover, explained
What is RO2 failover?
More than two connections.
A design around shared dependencies.
RO2 and diverse-fibre arrangements can provide greater separation between primary and secondary access paths. The exact routes, exchanges and termination arrangements depend on the service proposed for your site.
Radian helps compare those options with equipment, local power, addressing and application needs. The aim is a usable alternative route whose behaviour is agreed and tested before the business depends on it.
See the bigger picture →Built around the work you do
Plan the alternative.
Understand its limits.
The features that matter, with the practical details made clear.
Termination choices
Review available exchange and termination separation, with the offered design confirmed by delivery specialists.
Fault detection
Agree the conditions used to detect an unusable path and trigger the supported routing response.
Router & firewall resilience
Consider suitable high-availability equipment where a single device would otherwise remain a shared failure point.
Active or standby use
Explore how both circuits should operate during normal use and after a fault, with capacity and routing implications understood.
A tested fallback
Exercise the intended application, connectivity and recovery behaviour in a suitable test window.
Service availability, equipment, features, licences and support scope are confirmed in your proposal. Optional services are priced and agreed separately.
The picture, made clearer
Different paths.
A tested changeover.
A simplified service view. The components and responsibilities are agreed around your requirements.
Your businessPeople, applications and local equipment
PRIMARY ACCESS
Primary circuitNormal routing and capacity
CONFIRMED ALTERNATIVE
Diverse secondary routeAgreed fault detection and failover
Business servicesCalling, cloud and internet access
Route, exchange, equipment and power separation must be confirmed. Session continuity depends on the agreed design and applications.
Illustrative service view. The components, features and responsibilities depend on the agreed setup.
Make an informed choice
Choose the setup around your work.
Diverse fibre
A suitable design can provide greater physical separation. Different providers or account numbers alone do not establish independent routes.
Active-active or active-standby
Both links may carry traffic, or one may take over after a fault. The selected routing, capacity and service model determine the behaviour.
Equipment and sessions
Local switches, routers, firewalls and power matter alongside circuits. Public-IP changes and rerouting can affect live sessions and applications.
The practical details
Choose the failure scenarios.
Then prove the response.
The backup specification should follow the business impact of disruption and the work that needs to remain usable.
Plan your setup ↗Prioritise essential work
Identify the applications and capacity needed on the alternative path, including calling and remote access.
Record the dependencies
Confirm route, termination, equipment and power assumptions in the service design.
Test failover and return
Check the fault conditions and the move back to normal operation, then keep the results current after changes.
From enquiry to everyday use
A clearer path, with Radian.
- 01
Define
Identify fault scenarios and essential applications.
- 02
Confirm
Review routes, terminations, equipment and addressing.
- 03
Implement
Coordinate the circuits and supported configuration.
- 04
Test
Exercise failover, recovery and the agreed application paths.
A little more clarity
RO2 failover,
answered.
Have a question about your setup?
Tell us what you want to achieve.
Does RO2 mean no downtime?
No design should be read as removing every possible failure. The proposal confirms the separation, operating behaviour and applicable service commitments.
Can two providers share infrastructure?
Yes. Physical routes and network dependencies need checking rather than relying on provider names alone.
Do both circuits need identical bandwidth?
Not necessarily. A smaller alternative may support priority work, while full normal operation may need a different specification.
Will existing calls and sessions continue?
That depends on the platform, addressing, routing and applications. Some sessions may reconnect. Test the actual services that matter.
Do we need two routers and firewalls?
That depends on the fault scenarios and design. A second circuit does not protect against every shared device or power failure.
How often should we test?
Agree a review schedule and test after material changes to equipment, routing or applications that could affect the fallback behaviour.
UK-wide service enquiries
RO2 failover across the UK.
Resilience depends on the actual primary and backup paths at each UK site. Check physical and supplier dependencies, power, application behaviour and the agreed failover design rather than assuming two services are automatically independent.
Based in Charlwood, we welcome enquiries nationwide, with a particular focus on Horley, Crawley, Gatwick, Surrey, Sussex and London. Delivery, availability and any site attendance are confirmed for your chosen service.
Let’s talk
Let’s make your
alternative route useful.
Tell us about your current setup, priorities and plans. We’ll help you work through the next steps.
hello@RadianNetworks.co.uk