JUNIPER MX SERIES · TPM FOR CARRIER-CLASS ROUTERS

Juniper MX Series Maintenance — vendor-independent service for carrier-class routers

We service Juniper MX carrier-class routers after factory warranty and Juniper Care — vendor-independent, with OEM MPCs, MICs, routing engines and power supplies, SLA up to 24×7×4. Complete family: MX204/240/480/960 (mid/high-end), MX2008/2010/2020 (carrier backbone), MX10003/10008/10016 (Universal Chassis). 30 to 60 percent below Juniper Care, up to 70 percent on EOSL models.

Quote in 48 h Calculate savings

Which MX models we service

MX-Series platforms are the most demanding Juniper devices from a maintenance perspective — highly complex chassis with Modular Port Concentrators (MPCs), Modular Interface Cards (MICs), redundant routing engines, switch fabric boards and multiply redundant power supplies. Three generation families coexist: classic MX204/240/480/960 (2008-2014, many EOSL reached), Carrier Backbone MX2008/2010/2020 (2015+), Universal Chassis MX10003/10008/10016 (2018+).

MX204/MX240/MX480/MX960 · mid/high-end

MX204 (compact) · MX240 · MX480 · MX960

MX2008/MX2010/MX2020 · carrier backbone

MX2008 · MX2010 · MX2020

MX10003/MX10008/MX10016 · Universal Chassis

MX10003 · MX10008 · MX10016

MPCs, MICs & components

MPC1E/2E/3E/4E/5E/7E/8E/9E · MIC1/2/3/6 · routing engines (RE-S/RE-X/RE-MX2K) · switch fabric boards · power supplies · 1/10/40/100/400G optics

Why TPM maintenance for Juniper MX

MX-Series maintenance is the highest lever in the Juniper maintenance portfolio. Juniper Care for a fully populated MX2020 with 16 MPCs, redundant routing engines and 8 power supplies moves into six-figure amounts per year — and MX2020/MX10016 are not uncommon in carrier and large enterprise WAN backbones. TPM reduces these maintenance terms to 35-50 percent without limiting MPC or MIC functionality — Junos on MX continues to work without licensing, all MPLS, BGP, OSPF, IS-IS and VPN functions stay active.

We service MX with OEM MPCs, MICs, routing engines, switch fabric boards, power supplies and optics from our own warehouse. We stock MX-specific components for all generations — MPC1E to MPC9E, MIC1 to MIC6, RE-S to RE-MX2K. For very old MPC1/MPC2 modules (early MX240/480/960 from 2008-2010), some components have become rare — we use certified refurbishing partners from the carrier networking ecosystem.

30–60 %

Savings vs. Juniper Care for carrier-class

up to 70 %

Savings on EOSL MX240/480

Carrier SLA

24×7×4 with carrier networking expertise

MPC specialist

Original MPCs of all generations in stock

Generations timeline & TPM coverage

Per hardware generation: vendor phase (slate) and TechCare coverage window (teal) up to ~5 years post-OEM EOSL.

2008

2013

2018

2023

2028

2033

Today · 2026

MX240 / MX480 (early generations)
2008–2022
TPM until2027+
Recommended
MX960 (early generations)
2009–2023
TPM until2028+
Recommended
MX204
2017–2026
TPM until2031+
Supported
MX2008 / MX2010 / MX2020
2013–2027
TPM until2032+
Supported
MX10003 / MX10008 / MX10016
2018–2028
TPM until2033+
Supported

EOSL status of MX generations

MX generations follow an 8-12 year Juniper lifecycle. Early MX240/480 have reached EOSL, MX960 is approaching, MX204 and carrier backbone platforms are current.

Model family	Released	OEM support ends	TPM status
MX240 / MX480 (early generations)	2008–2010	2020–2022	Recommended
MX960 (early generations)	2009–2011	2021–2023	Recommended
MX204	2017	2025–2026	Supported
MX2008 / MX2010 / MX2020	2013–2015	2025–2027	Supported
MX10003 / MX10008 / MX10016	2018+	ca. 2028+	Supported

As of 2026. EOSL data based on official vendor roadmaps and subject to change. Binding case-by-case information available on request.

What we deliver

OEM original parts

Our warehouse stocks OEM original components, including for end-of-life generations.

Onsite engineer

German-speaking technicians throughout DACH, 4-hour response time guaranteed.

Flexible SLA per system

Parts Only, 5×9 NBD or 24×7×4 — freely combinable by location and criticality.

Multi-vendor contract

One contract for Juniper and all other vendors. No more individual contracts.

EOSL tracking & reporting

Monthly SLA reports, asset overview, automatic EOSL notifications.

Junos & software stay

Junos OS, Mist Cloud subscription and all Juniper software licenses independent.

Comparison

TechCare vs. Juniper Networks MX-Series Router

Concrete SLA tiers, OEM comparison, coverage details and source footnotes — on a print-friendly page.

Open Battle-Card

FAQ on MX-Series maintenance

Which MX models do you service?

Complete MX family: MX204 (compact 1U edge), MX240, MX480, MX960 (classic mid/high-end), MX2008, MX2010, MX2020 (carrier backbone) and MX10003, MX10008, MX10016 (Universal Chassis). Including all MPCs (MPC1E to MPC9E), MICs (MIC1 to MIC6), routing engines (RE-S, RE-X, RE-MX2K), switch fabric boards and power supplies.

What does TPM cost for MX compared to Juniper Care?

30 to 60 percent savings. An MX480 with 4 MPCs, redundant routing engines and 24×7×4 costs 18,000 to 28,000 EUR/year with Juniper, 8,000 to 13,000 EUR with TechCare. MX2020 with full population 80,000-130,000 EUR Juniper Care, 35,000-60,000 EUR with TechCare. MX10008 higher in absolute terms. For EOSL MX240/480 we see up to 70 percent — Juniper often no longer offers renewal.

Can you service older EOSL MX240/480/960?

Yes, a focus area of our Juniper business. MX240/480 (2008-2010, EOSL 2020-2022) and early MX960 (2009-2011, EOSL 2021-2023) are still productive in DACH carrier and enterprise WAN backbones. We stock MPCs, MICs, routing engines and power supplies for these generations. For very old MPC1/MPC2 modules we use certified refurbishing partners from the carrier networking ecosystem.

Do MPLS, BGP and VPN functions continue to work without a Juniper contract?

Yes. Junos on MX continues to work without licensing — MPLS stack (LDP, RSVP-TE, Segment Routing), BGP (eBGP, iBGP, BGP-LU, BGP-EVPN), OSPF/IS-IS, all layer 2 and layer 3 VPN functions (VPLS, EVPN-VXLAN, L2VPN, L3VPN), MPLS Fast Reroute, BFD and all carrier-class features stay functionally active. Code updates to newer Junos versions require an active Juniper contract.

Which SLA levels do you recommend for MX?

MX as carrier backbone or primary WAN edge: 24×7×4 with German-speaking onsite engineer is standard — an outage affects entire carrier backbones or multi-site WANs. MX204 as edge router in branch sites can be sufficiently covered with 5×9 NBD depending on redundancy concept. For MX2020/MX10016 in carrier core roles with high redundancy (active-active or N+1), 5×9 NBD can be economical — single component failures are absorbed by the backup path.

What about Juniper Paragon Active Assurance?

Paragon Active Assurance (service assurance platform for MX service provider workflows) is a software subscription independent of hardware maintenance. Customers actively using Paragon should keep the subscription with Juniper — hardware maintenance runs in parallel via TPM. Paragon probes and service monitoring stay functionally active.

Can we have MX and other Juniper lines (EX, QFX, SRX) in the same contract?

Yes. Multi-class contracts are our strength — MX as WAN edge and carrier backbone, QFX as data center fabric, EX as campus switching, SRX as security gateway, plus Mist and ACX — all in one contract, one point of contact, one SLA report set. Plus all other vendors (Cisco, Arista, Nokia, etc.) in the same construct.

How fast do we get a quote?

Within 48 hours after receipt of your inventory list with model, generation, MPC and MIC count, routing engine type and serial number.

Service performance

Real actuals Q1 2026 — straight from our ITIL ticketing.

99,2 %

Tickets resolved within agreed response time

2,4 h

Avg. first response on 4h SLA tier

88 %

First-time fix on initial dispatch

97 %

Spare part on site within 4 h, DACH depots