←DashboardTata operations review — 15 – 28 Jul 2026
1 / 9

Prepared for
Tata Communications
Zixi Operations · all times UTC
Bi-weekly operations review
No broadcaster outages were recorded in this window. 1 unplanned incident logged, most severe Sev 3. 2 maintenance windows, 1 of them emergency.
← → or space to navigate · f fullscreen · g slide index

Prepared for
Tata Communications
Zixi Operations · all times UTC
Bi-weekly operations review
No broadcaster outages were recorded in this window. 1 unplanned incident logged, most severe Sev 3. 2 maintenance windows, 1 of them emergency.
Broadcaster-minutes of impact
0m wall-clock across 0 outage windows
Maintenance windows
1 emergency
What went well
- ✓No broadcaster outages recorded in the period — a clean fortnight after the 6 July LA event.
- ✓The 23 July cross-connect LOR stayed on the redundant leg with no customer impact.
Concerns to raise
- ◆Emergency maintenance CHGP1245620 arrived with short notice on 24 July. Ask Tata for the standard lead time on emergency changes.
- ◆Two of the three action items raised on 14 July are still open, including the ZAASOPS-251 restoration time.
By severity
●1 incidents, all Sev 3.
By cause
Cross-connect / fiber1Cross-connect / fiberIncidents1
●Sev 3Sev 3 — Degraded, no outageCross-connect / fiberLoss of redundancy#27645CSP0623072678722 Impact
broadcaster-minutes
Tata reported a cross-connect fibre issue placing ContentXchange circuits into loss of redundancy on 23 July. Traffic stayed on the surviving leg.
Resolution: Redundancy restored by Tata; no customer impact observed.
■ PlannedPlanned maintenance activity || CHGC1243360notified 20 Jul 14:50
▲ EmergencyEmergency Maintenance Activity || CHGP1245620notified 24 Jul 07:12
● ActiveConfirm host-level anti-affinity for redundant broadcaster pairs in LA CloudlyteTata—
○ OpenProvide restoration time for the 10 July NJ Cloudlyte event (ZAASOPS-251)Tata—
○ OpenAgree a minimum lead time for emergency change notificationsJoint—
✓ DoneConfirm the Ceph RBD remap remediation is complete and no further LA reboots are queuedTata—
Incidents per review
430 Jun – 14 Jul 2026incidents4115 – 28 Jul 2026incidents1vs previous−3
Jul 14Jul 28
Broadcaster-minutes
20h 59m30 Jun – 14 Jul 2026impact20h 59m0m15 – 28 Jul 2026impact0mvs previous−20h 59m
Jul 14Jul 28
Customers affected
530 Jun – 14 Jul 2026customers5015 – 28 Jul 2026customers0vs previous−5
Jul 14Jul 28
Before the next review
- →Confirm host-level anti-affinity for redundant broadcaster pairs in LA CloudlyteTata
- →Provide restoration time for the 10 July NJ Cloudlyte event (ZAASOPS-251)Tata
- →Agree a minimum lead time for emergency change notificationsJoint
Window 2026-07-15 → 2026-07-28 · all times UTC