A real notice, worked through the review framework.
This is a complete public-scope Intelplexis review of a genuine, publicly announced infrastructure change: co-location order-entry switch maintenance announced by a major European derivatives exchange. It is shown in the same structure a client would receive — with one difference: it is bound to no firm, so the applicability section shows the test, not a determination.
Provider & notice
change review| Record | IPX-CHG-2026-0003 · v1 |
| Provider | Eurex (Deutsche Börse Group) |
| Notice | Order Entry switch maintenance, Equinix FR2 co-location facility — Eurex Circular 027/26 and Implementation News updates of 24 June and 2 July 2026 |
| Classification | Technical maintenance — co-location order-entry infrastructure |
| Urgency | High — four-date programme with the first date imminent at review time |
What changed
provider factsThe exchange announced maintenance on the Order Entry switches in its Equinix FR2 co-location facility across four Saturdays, split between the A-side and B-side of the order-entry infrastructure. Dedicated support is available 12:00–15:00 CEST on each date, with the exchange’s technical account contacts named for issues during the window.
| Sat 18 July 2026 | A-side · switches RFRA3214, RFRA3215 · support window revised — see reconciliation note |
| Sat 25 July 2026 | A-side · switch RFRA3216 |
| Sat 08 August 2026 | B-side · switches RFRA3236, RFRA3239 |
| Sat 15 August 2026 | B-side · switches RFRA3230, RFRA3231 |
Source reconciliation. The provider’s two notices state different dedicated-support windows for 18 July: 10:00–14:00 CEST in the 24 June notice, and 12:00–15:00 CEST in the 2 July update, which flags the window as revised. Providers legitimately update their own information; the review’s job is to catch the change. The later notice is treated as controlling, and both source documents are retained. A separate market-data maintenance on 11 July is recorded as related context only — it is not part of this programme.
Why it may matter
Intelplexis analysis — not provider factThis is availability-critical infrastructure: firms whose order-entry sessions route through a named switch could experience session interruption or failover during the relevant window. Functions typically touched where a dependency exists: network operations, exchange connectivity and session routing, failover and redundancy configuration, and support-desk coverage during each maintenance window. Standard A-/B-side redundancy may absorb single-side maintenance without impact — an assumption that holds only once verified against a firm’s actual topology.
Applicability test
both branches, equal weight- It holds co-location order-entry sessions in the named facility routed through any named switch on the corresponding side (A-side, July dates; B-side, August dates)
- It has no co-location order-entry presence in that facility, or its sessions route only through switches not named in this programme
A ruled-out determination is recorded with its reason and retained. “Checked and not applicable” is a control result — the dismissal record is part of the deliverable.
Confirmation required from the firm
the deciding questionDo any of the firm’s order-entry sessions traverse the named switches — RFRA3214, RFRA3215 or RFRA3216 (A-side), or RFRA3236, RFRA3239, RFRA3230 or RFRA3231 (B-side)?
Only the firm’s own connectivity records can answer this. In a live engagement this question goes to the named client contact with a respond-by date tied to the provider’s schedule. This sample is bound to no firm, so the question is shown unanswered — which is the honest state of any review before the client confirms its dependencies.
Candidate ownership & contingent actions
activated only on confirmed dependency| Ownership domain | Network Operations / Exchange Connectivity, with Trading Infrastructure for failover readiness — proposed as roles; named owners are assigned by the client firm |
| Action 1 | Confirm which named switch(es) the firm’s order-entry sessions traverse — closure evidence: documented switch-to-session mapping |
| Action 2 | Review routing and failover readiness across A-side and B-side for the affected dates — closure evidence: failover test or readiness confirmation |
| Action 3 | Confirm operational support coverage during each maintenance window, noting the revised 18 July window — closure evidence: staffed-coverage confirmation per date |
Owner names, due dates and deadlines are assigned only with the firm; none are asserted here.
Evidence expected for closure
Each action names its closure evidence before work begins, so “done” has a defined meaning. On closure, the review records what the evidence was, who supplied it and when — held or referenced at the firm’s choice — and the closure is countersigned by the firm’s owner. Where the change turns out not to apply, the closure record is the reasoned dismissal itself.
Boundaries
determined / not determined- The provider facts: seven named switches, four dates, A-/B-side split, facility scope, support arrangements including the revised 18 July window
- That the two source notices conflicted, and which one controls
- A bounded position of potential — at infrastructure and firm-type level only
- Whether any specific firm is co-located in the facility
- Whether any firm’s sessions traverse a named switch
- Whether any firm’s redundancy would absorb the maintenance without impact
- Any firm-specific operational or trading outcome
Firm-specific applicability cannot be determined without dependency evidence supplied by the firm. That is a design principle, not a limitation being apologised for.
Source material
| Official channel | Eurex Implementation News (provider’s official publication channel) |
| Documents retained | Implementation News of 24 June 2026 and 2 July 2026 (both source documents kept; the 2 July notice controls the 18 July support window); Eurex Circular 027/26 cited by the provider as the originating announcement — identified as cited, not held |
| Provenance discipline | Every review lists its sources, retains what was received, and marks anything cited but not held as exactly that |
This sample is a genuine review of a genuine public notice. It names no firm, contains no client data, and makes no claim that this maintenance affects any particular firm. In a live engagement, the same review would additionally carry the client’s confirmed dependencies, the resulting determination, named owners, due dates, and the closure trail.
Want this on your own notices?
A pilot processes real changes from the providers you name.