70411 [Tata Communications] Re: Zixi services on LOR || CSP0605082643523
None written.
- Combined downtime
- None measured
- Elapsed time
- —
- Started (UTC)
- 5 Aug 15:05
- Customers affected
- —
- References
- CSP0605082643523L5G2WV-4311WCase 00027731
Bi-weekly service review
Prepared for Tata Communications by Zixi
In brief
The headline figures for the period, and what stood out.
Combined downtime
2m
across 2 outages · 2m elapsed · <1m on average
Longest single outage
2m
Zixi ContentXchange - CXE
CXE-BX-LON-01
Combined downtime adds up the time every affected broadcaster was down, so two broadcasters down for the same hour count as two hours. Elapsed time counts that hour once.
Unplanned incidents
2 vs 15 – 28 Jul 20263
Events that affected service
Still open
No change0
Every incident resolved
Customers affected
2 vs 15 – 28 Jul 20262
CS Test, Zixi ContentXchange - CXE
Maintenance windows
6
1 of them emergency
Notices, no impact
0
Tracked, but service was unaffected
SLA met
—
Not assessed this period
Changes are against the previous review, 15 – 28 Jul 2026.
How much disruption customers saw, when it happened and where it landed.
Each row is one broadcaster, and each bar shows how long an outage lasted. Bars that line up across rows come from the same event.
Which customers were affected most.
Which Tata region the outages were in.
A server that keeps appearing points to the infrastructure rather than to 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 |
Unplanned events that affected service, and what we know about each one.
Incidents by severity level.
3 incidents, all Sev 3 · Degraded service.
Incidents by cause.
None written.
None written.
None written.
Maintenance Tata told us about during the period, and whether it affected service.
| Reference | ||||
|---|---|---|---|---|
| Emergency | Emergency maintenance activity || CHGP1248184CHGP1248184 | Time not stated Notified 29 Jul 04:44 | No impact | CHGP1248184Case 00027677 |
| Planned | Planned Maintenance Activity || CHGC1248697CHGC1248697 | Time not stated Notified 29 Jul 14:02 | No impact | CHGC1248697Case 00027683 |
| Planned | Planned Maintenance Activity || CHGC1248701CHGC1248701 | Time not stated Notified 30 Jul 10:24 | No impact | CHGC1248701Case 00027693 |
| Planned | Planned maintenance activity || CHGC1249994CHGC1249994 | Time not stated Notified 1 Aug 07:22 | No impact | CHGC1249994Case 00027710 |
| Planned | Re: Planned maintenance activity || CHGC1243360CHGC1243360 | Time not stated Notified 6 Aug 07:32 | Affected service | CHGC1243360Case 00027742 |
| Planned | Planned maintenance activity || CHGC1254745CHGC1254745 | Time not stated Notified 10 Aug 11:05 | No impact | CHGC1254745Case 00027770 |
What we agreed to follow up on, and who is on point. Open items carry forward until they are closed.
| Reference | |||||
|---|---|---|---|---|---|
| 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 | 14 Jul 2026 | Not set | ZAASOPS-251 |
| In progress | Agree a minimum lead time for emergency change notifications Draft proposal circulated: 4 hours minimum for emergency changes. | Joint | 28 Jul 2026 | Not set | Case 00027650 |
| 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 | 11 Aug 2026 | Not set | Case 00027693 |
| 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 | 14 Jul 2026 | Not set | — |
How this period compares with earlier reviews.
Completed reviews only. The live review is left out, because its window overlaps the last meeting and would count the same events twice.