Tier 1 ISP configuration management
Back up, audit, and control configuration across a national, multi-vendor estate at six-figure device counts, on infrastructure you own.
~200k devices under management in a single Tier 1 ISP deployment.
TRANSPORT Routing, Switching, Opticalone plane, every layerBACKBONE Scheduled Backup at Scaleversioned, diffable, on cadenceCOMPLIANCE Continuous Policy & RBACaudit trail, always on
EMEA-WHA Regional clusterdevices · sites · local collectionAMER-EHA Regional clusterdevices · sites · local collectionAPAC-NHA Regional clusterdevices · sites · local collectionRIM-OTHA Regional clusterdevices · sites · local collection
A Tier 1 ISP runs its national, multi-vendor estate on rConfig, one configuration standard across hundreds of thousands of devices.
- ~200kdevices under management
single Tier 1 ISP deployment
- 100,000+fleet design point
built for six-figure estates
- 1configuration standard
enforced across every region and vendor
- 24/7scheduled collection
backup cadence that keeps closing
Deployment figures are approximate and published with customer permission.
Scale changes everything
A Tier 1 ISP does not run a network, it runs an estate built up over a decade. At that size the hard problem is not configuring one device. It is holding every device to one standard, proving it, and changing it safely while the network stays up.
Tools built for a few thousand devices quietly fall over here: backup windows stop closing, drift goes unnoticed until it causes an outage, and a change that is fine on ten devices becomes a national incident on a hundred thousand. The platform is engineered for this in the rConfig reference architecture, and the scale is proven, not asserted, validated against estates of up to 200,000 simulated devices with rConfig Sim network simulator.
Manage the network you have, not the one a vendor wants you to buy
A Tier 1 estate is multi-vendor by necessity, so its management layer has to be genuinely neutral. rConfig sells no network hardware, so its neutrality is structural, not promised: no hardware line to protect, no reason to favour one vendor. Driver support is template-driven and customer-extensible, so a new platform is a configuration change, not a wait for a roadmap. See multi-vendor configuration management for how that works in practice.
That reach includes the optical transport layer, the part of a carrier estate most tools leave to the vendor's own element manager. See configuration management for optical networks for how rConfig holds it to the same standard.
What it has to do
The disciplines an enterprise needs, executed at a scale where every one of them has to hold without manual effort. The same platform proven on managing 100,000 network devices.
True multi-vendor reach
One platform across routing, switching, optical, and security, from every vendor in the estate. Drivers are template-driven and customer-extensible, so a new platform is a config change, not a vendor roadmap request.
Scheduled backup at estate scale
Parallel, queue-driven collection keeps six-figure device counts backed up on a tight cadence without flooding the management plane. Every config is versioned and diffable from the first poll.
Multi-region, one standard
Distributed collectors reach POPs and regional cores close to the kit, while policy, inventory, and audit stay centralised. A national estate is governed as one network, not a dozen islands.
Continuous compliance and RBAC
Policy checks run against every collected config, drift is flagged on change, and role-based access plus full audit trails hold operations to the standard auditors and regulators expect of a carrier.
Controlled change with rollback
Push validated changes in bulk, capture a known-good before and after every window, and roll back to a verified state fast when a change goes wrong. Change at scale stops being the thing that keeps the NOC up at night.
Drift and change observability
See what changed, where, by whom, and when across the whole estate. Real-time change detection turns silent configuration drift into an alert the operations team can act on before it becomes an outage.
AI you can audit
The industry sells the top of the ladder and asks for your trust. rConfig shows you every step.
Network AI is sold to carriers as full autonomy today. For a Tier 1 estate, where a wrong automated change is a national outage, that is a claim that owes you a rollback story and rarely has one. rConfig maps its AI to the TM Forum L0 to L5 scale and is honest about where it stands: read-only and grounded in your real configuration data, assistive today and earning trust before it is given the keys to production. See the network AI maturity model for the full picture, or our approach to honest, grounded network AI.
Bring your estate up to one standard
See rConfig run against a Tier 1 ISP-scale, multi-vendor network. Book a working demo, or talk to our team about your estate.