What the fortnight came to: the figures the meeting opens on, what went well, and what to put to Tata.
Broadcaster-minutes of impact
2m
across 2 outage windows · 2m wall-clock · <1m average
Longest single outage
2m
CXE-BX-LON-01 · Zixi ContentXchange - CXE
Incidents
3
+2 vs 15 – 28 Jul 2026
Unplanned, service-affecting
Still open
0
no change vs 15 – 28 Jul 2026
Customers affected
2
+2 vs 15 – 28 Jul 2026
CS Test, Zixi ContentXchange - CXE
Maintenance windows
6
1 emergency
Notifications, no impact
0
Logged, no Zixi impact
SLA met
—
No SLA verdict recorded this period
Open the meeting with these.
Each one should name the thing you want Tata to do.
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.
All times UTC. Bar width is the outage window; overlapping lanes in the same window indicate one shared fault rather than separate incidents.
Counted per broadcaster, stacked by region. Hover a day for its impact minutes; use the region chips above to isolate one.
Sum of every broadcaster outage attributed to each customer.
Which Tata region carried the fault.
A host appearing repeatedly points at infrastructure rather than chance.
| 4 Aug 17:59 | 4 Aug 17:59 | <1m | travis-gpu-telev8 | CS Test | NJ | wl-cloudlyte-sr02 | Resolved |
| 10 Aug 19:19 | 10 Aug 19:21 | 2m | CXE-BX-LON-01 | Zixi ContentXchange - CXE | LONDON | LDN SR03 | Resolved |
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.
Zixi severity ladder, as classified on the originating ticket.
3 incidents, all Sev 3.
Normalized issue category.
None written.
None written.
None written.
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.
| Refs | ||||
|---|---|---|---|---|
| Emergency | Emergency maintenance activity || CHGP1248184CHGP1248184 | window not stated notified 29 Jul 04:44 | No | #27677CHGP1248184 |
| Planned | Planned Maintenance Activity || CHGC1248697CHGC1248697 | window not stated notified 29 Jul 14:02 | No | #27683CHGC1248697 |
| Planned | Planned Maintenance Activity || CHGC1248701CHGC1248701 | window not stated notified 30 Jul 10:24 | No | #27693CHGC1248701 |
| Planned | Planned maintenance activity || CHGC1249994CHGC1249994 | window not stated notified 1 Aug 07:22 | No | #27710CHGC1249994 |
| Planned | Re: Planned maintenance activity || CHGC1243360CHGC1243360 | window not stated notified 6 Aug 07:32 | Yes | #27742CHGC1243360 |
| Planned | Planned maintenance activity || CHGC1254745CHGC1254745 | window not stated notified 10 Aug 11:05 | No | #27770CHGC1254745 |
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 | |||||
|---|---|---|---|---|---|
| Blocked | Provide restoration time for the 10 July NJ Cloudlyte event (ZAASOPS-251) Outstanding four weeks. Tata has not been able to retrieve the restoration timestamp. | Tata | 2026-07-14 | — | ZAASOPS-251 |
| In progress | Agree a minimum lead time for emergency change notifications Draft proposal circulated: 4 hours minimum for emergency changes. | Joint | 2026-07-28 | — | #27650 |
| Open | Clarify whether CHGC1248701 actually removed redundancy during its window Tagged Sev 2 with a cross-connect loss-of-redundancy category but recorded as no-issue. | Tata | 2026-08-11 | — | #27693 |
| Done | Confirm host-level anti-affinity for redundant broadcaster pairs in LA Cloudlyte Tata confirmed redundant pairs are now placed on separate physical hosts. | Tata | 2026-07-14 | — | — |
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.
