Buying a backup internet connection: questions to settle before signing

Define the failure you want to survive

Write down the interruption scenarios separately: an access-cable cut, failed router, loss of building power, an upstream incident and planned maintenance. A second circuit may address some scenarios and leave others unchanged. Agree which failures the design covers before comparing products.

Two different operators can share a duct, building entry or other physical resource. RFC 4202 describes shared risk link groups: links affected together by failure of a common resource. Ask what evidence supports the proposed separation and which dependencies remain unverified.

Size the backup for priority work

Create a minimum operating profile. Order processing and voice calls may need to continue while bulk backups and nonessential downloads can wait. State the required upload as well as download capacity, and test at the time and location that reflect real use.

Consider the access medium against the site. A different fibre route may be suitable where available. RF depends on survey and path conditions. Mobile backup depends on local coverage, usable capacity, equipment and tariff conditions. None should be selected solely because it carries the word “backup”.

Ask what happens to sessions and public IPs

During failover, the public IP, outbound path or VPN tunnel can change. Supplier allowlists, remote administration and open sessions may be affected. Ask who configures routing and firewall rules, what triggers a changeover and how staff recognise an incident.

Separate failover from a promise of uninterrupted applications. A router can detect a failed path without preserving every session. The written design and acceptance test should describe the intended behaviour and any application-side work.

Agree a test and a recovery owner

Use an authorised maintenance window and a reversible procedure. Check the agreed trigger, critical applications, priority traffic, incident notification and return to the primary path. Record the result and any unresolved issue. Avoid uncontrolled live outages as a demonstration.

• Failure coverage: which component is unavailable in the test?
• Business continuity: can staff complete the priority transaction?
• Recovery: who decides when to restore the normal route?
• Support: which team owns coordination across providers?

A test record is more useful than an unqualified “automatic backup” label. Repeat relevant checks after a material route, equipment or application change under the agreed operating process.

Turn the assessment into a comparable proposal

For a Türkiye business site, MyFi Business can evaluate primary and backup options alongside routing, equipment and technical coordination. Share existing circuit details and the tasks that must survive. Request one scope that identifies responsibilities, exclusions, recurring and initial costs, and acceptance criteria.

ADNET and MyFi Business belong to the same brand family. This guide explains the procurement questions; a site-specific proposal comes from MyFi Business following technical review. No capacity or changeover time is established by the article itself.