Disaster recovery bandwidth.On standby until you need it.
Stop paying full price for a circuit you hope to never use. Recovery on Demand pre-provisions your failover path to a secondary site or DR data center, then activates full burst capacity within minutes of a declared event — billed only for what you actually consume.
Your DR plan shouldn't cost as much as production.
Most disaster recovery circuits sit idle 99% of the time, yet customers still pay for full bandwidth around the clock. That math rarely survives a budget review — so DR links get under-sized, and the one time you need them, they can’t carry the failover load.
Recovery on Demand flips the model. We pre-provision a low-cost standby path to your DR site today, and reserve the headroom to burst it to full capacity the moment you declare an event. You pay a small standby fee plus metered usage only during activation — not a 24/7 premium circuit you may never fully use.
- Pre-provisioned standby path. The physical and logical route to your DR site is built and tested before you ever need it.
- Burst to 100G in minutes. Activation is a logical bandwidth upgrade, not a new cross-connect or truck roll.
- Pay for standby, not idle peak. Metered burst billing means you're never paying premium rates for capacity sitting unused.
- Self-service or NOC-triggered. Activate via the DCConnect NaaS portal, API, or a single call to our 24×7 NOC.
What you get
Four things that come standard.
Every Recovery on Demand order includes these four capabilities — built so failover is fast, predictable, and affordable.
Fast Activation
Full burst capacity is live within 15 minutes of a declared event — whether triggered through the portal, the API, or a phone call to our 24×7 NOC. No re-cabling, no new circuit order, no waiting on a vendor.
Metered Burst Billing
Pay a low monthly standby fee for the reserved path, then metered usage only for the hours or days you’re actually bursting. No flat-rate premium circuit billed 24/7 for capacity you rarely touch.
Pre-Tested Standby Path
The route to your DR site is built, cross-connected, and tested before you ever need it. We run quarterly activation drills on request, so the failover path is proven — not theoretical — when it counts.
Any On-Net DR Site
Works between any two on-net facilities in our 500+ partner data center footprint across APAC — same-city standby for fast RTO, or cross-border for full regional resilience.
How it works
From standby to fully live in three steps.
The hard part — designing and provisioning the path — happens once, up front. Activation is the easy part.
We provision the standby path
Tell us your primary and DR sites. We build the physical cross-connects at both ends and configure a low-bandwidth standby circuit so the path is live, monitored, and ready — at a fraction of full-capacity cost.
You declare an event
Trigger activation through the NaaS portal, a REST API call, or a direct line to our 24×7 NOC. There’s no approval queue or contract amendment in the critical path — declaration is the activation trigger.
Burst capacity goes live
The standby link is upgraded in software to its full contracted burst speed — up to 100G — typically within 15 minutes. You’re billed metered usage for the burst window, then the link reverts to standby once you stand down.
One path, two states: idle and active.
Recovery on Demand keeps a single logical path provisioned at all times between your primary and DR sites. In standby state it carries only health checks and low-volume replication traffic. On activation, the same path is upgraded to its full contracted burst rate — no new circuit, no new cross-connect.
Same-city standby paths support sub-second activation for application-level failover; cross-border paths support full regional DR with burst rates up to 100G. Multi-site standby — fanning out to two or more DR locations — is supported on the same platform.
Technical specifications
The engineering details, on the table.
From standby port speeds to activation SLAs and monitoring standards.
Interface
Physical Port
Ethernet UNI at both primary and DR endpoints, provisioned at order time. Burst rate is provisioned logically up to the contracted ceiling — the physical port is sized for the maximum burst from day one.
Activation
Time to Full Burst
From declaration to full contracted burst bandwidth. Same-city standby paths often activate in under 5 minutes. Activation is logical bandwidth reprovisioning — no field work required.
Standby bandwidth
Idle-State Rate
The standby path carries health checks, replication heartbeats, and low-volume sync traffic at a fraction of the port speed — keeping standby fees low while the path stays warm and tested.
Burst capacity
Peak Activated Rate
Contracted burst ceiling, selected at order time. Multiple burst tiers are available (1G–100G) so the activated rate matches your actual failover throughput requirement, not an arbitrary maximum.
Billing
Metered Activation
Fixed monthly fee for the standby reservation, plus metered hourly billing for any period spent above standby rate. Usage is itemized in the NaaS portal in real time during an active event.
Monitoring
Continuous Path Health
The standby path is continuously monitored for reachability and degradation — not just checked at activation time. Quarterly live activation drills are available on request to validate RTO assumptions.
Who uses this
Where Recovery on Demand wins.
Any organization that needs a credible DR path without paying full freight for capacity that sits idle most of the time.
Regulated Industries with DR Mandates
Financial services, healthcare, and insurance firms are required to maintain a tested DR plan but rarely activate it. Recovery on Demand satisfies audit requirements for a provisioned, tested path at a fraction of an always-on circuit’s cost.
Mid-Size Enterprises Outgrowing Cold DR
Tape backups and cold-standby DR no longer meet RTO targets, but a full active-active DCI circuit is overkill. Recovery on Demand bridges the gap — warm standby today, full bandwidth the moment it’s declared.
Seasonal & Event-Driven Businesses
Retail, ticketing, and media businesses face concentrated risk windows — peak season, major launches, live events. Activate burst capacity for the exposure window only, then scale back down once the risk period passes.
MSPs & System Integrators
Offer DR-as-a-service to clients without carrying the cost of dedicated bandwidth per client. Stand up standby paths across your client base, activate and bill only the clients who declare an event.
Frequently asked
Questions we get a lot.
Still have questions? Reach out our team
How is this different from just ordering a smaller permanent circuit?
A smaller permanent circuit caps your bandwidth at all times — including during a real failover, when you need the most capacity. Recovery on Demand keeps standby costs low while guaranteeing the full contracted burst rate is available the moment you declare an event.
What actually triggers activation?
You trigger it — through the DCConnect NaaS portal, a REST API call, or a phone call to our 24×7 NOC. There’s no automatic failure detection on our side; activation is always a deliberate action by your team, so there’s no risk of unexpected charges from a transient blip.
Can I test activation without it counting as a real DR event?
Yes. We offer scheduled activation drills — typically quarterly — at a discounted test rate, specifically so you can validate your RTO assumptions and runbooks without paying full burst pricing every time you rehearse.
What happens if I need to stay at burst rate for an extended period?
There’s no contractual cap on how long you can remain at burst rate. Usage is metered hourly for as long as you need it. If you expect an extended outage, our team can also discuss converting to a permanent upgraded circuit at standard rates.
Does the standby path carry any of my data today?
Yes — the standby rate (1–10 Mbps depending on tier) is sized for health checks and low-volume replication or sync traffic, so the path is exercised continuously rather than sitting completely dormant and untested.
Can I fan out one primary site to multiple DR locations?
Yes, through our custom multi-site tier. Hub-and-spoke standby topologies connecting one primary to two or more DR sites are supported, with independent activation per destination if your DR strategy requires geographic diversity.
Ready to stop paying for idle DR bandwidth?
Tell us your primary and DR sites and your target burst rate. We’ll design the standby path and have it provisioned in days.