Zixi

15 – 28 Jul 2026

Tata Communications

Present

Summary

What the fortnight came to: the figures the meeting opens on, what went well, and what to put to Tata.

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

across 0 outage windows · 0m wall-clock

Incidents

1

−3 vs 30 Jun – 14 Jul 2026

Unplanned, service-affecting

Still open

0

no change vs 30 Jun – 14 Jul 2026

Customers affected

0

−5 vs 30 Jun – 14 Jul 2026

Maintenance windows

2

1 emergency

Notifications, no impact

0

Logged, no Zixi impact

SLA met

—

No SLA verdict recorded this period

What went well

Open the meeting with these.

  • 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

Each one should name the thing you want Tata to do.

  • 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.

Impact

Where the downtime landed. Broadcaster-minutes of impact sum every affected broadcaster; wall-clock minutes count how long there was any impact at all. They are different numbers and are never added together.

No broadcaster outages were recorded in this window. Nothing to plot, and nothing to attribute.

1 unplanned · most costly first

Incidents

Every unplanned, service-affecting event in the window. The root cause and talking points on each are the part no query can produce, and are edited in place here.

The mix

click a segment or a bar to filter the register

By severity

Zixi severity ladder, as classified on the originating ticket.

1 incidents, all Sev 3.

By cause

Normalized issue category.

The register

every value readable without hover
  1. Sev 3Sev 3 — Degraded, no outage

    66837 [Tata Communications] Re: Zixi services on LOR || CSP0623072678722||23072026

    Cross-connect / fiberContentXchangeLoss of redundancy
    SummaryTata reported a cross-connect fibre issue placing ContentXchange circuits into loss of redundancy on 23 July. Traffic stayed on the surviving leg.
    Root causeNot yet established.
    ResolutionRedundancy restored by Tata; no customer impact observed.
    Talking points

    None written.

    Impact
    none measured
    Wall-clock
    —
    Started (UTC)
    23 Jul 11:34
    Status
    Closed
    Customers
    —
    References
    #27645CSP0623072678722
2 notified · 1 emergency · sortable

Maintenance

Provider maintenance notified in this window. The window column is the work itself, as the bulletin stated it; where a bulletin gave no window, the time we were told is shown instead and labelled as such.

Provider maintenance windows notified in the period.
Refs
Planned

Planned maintenance activity || CHGC1243360CHGC1243360

window not stated
notified 20 Jul 14:50		Yes#27623CHGC1243360
Emergency

Emergency Maintenance Activity || CHGP1245620CHGP1245620

window not stated
notified 24 Jul 07:12		No#27650CHGP1245620
3 open · 1 closed

Follow-up

What is outstanding and who owns it. Open items carry forward with the date they were first raised, so an item that has been open for three meetings says so.

Refs
In progress

Confirm host-level anti-affinity for redundant broadcaster pairs in LA Cloudlyte

Carried over. Tata acknowledged the request; awaiting written confirmation.

Tata2026-07-14——
Open

Provide restoration time for the 10 July NJ Cloudlyte event (ZAASOPS-251)

Carried over, still outstanding.

Tata2026-07-14—ZAASOPS-251
Open

Agree a minimum lead time for emergency change notifications

Prompted by CHGP1245620 on 24 July.

Joint2026-07-28—#27650
Done

Confirm the Ceph RBD remap remediation is complete and no further LA reboots are queued

Tata confirmed remediation complete; no further LA reboots queued.

Tata2026-07-14—ZAASOPS-246
each measure on its own scale · click a column to open that review

Trend

How this fortnight sits against the ones before it. Completed reviews only: the live review's window overlaps the last meeting by nearly a fortnight, so plotting it would count the same incidents twice.

Incidents per review

41
Jul 14Jul 28

Broadcaster-minutes of impact

20h 59m0m
Jul 14Jul 28

Customers affected

50
Jul 14Jul 28