Last checked: 10 minutes ago
Get notified about any outages, downtime or incidents for Zype and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Zype.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
Component | Status |
---|---|
Ad Bridge | Active |
Admin Platform | Active |
Analytics (API & Dashboard) | Active |
API | Active |
Apps Creator Apps | Active |
Apps Creator Dashboard (admin.zype.com/apps-creator) | Active |
Consumer Login (OAuth) | Active |
Content Delivery | Active |
Embeddable Widgets | Active |
Help Center (support.zype.com) | Active |
Legacy Zype App Templates | Active |
Live Archiver | Active |
Live Encoder Manager | Active |
Manifest Bridge | Active |
Marketplace Connect | Active |
MAZ Apps Creator Dashboard (dashboard.mazsystems.com) | Active |
Player | Active |
Playout | Active |
Playout Analytics API | Active |
RSS Feeds | Active |
Third-Party Video Source Importer | Active |
Upload API | Active |
VOD Transcoder | Active |
Webhook Service | Active |
View the latest incidents for Zype and check for official updates:
Description: I would like to express our apologies for the VOD delivery issues that occurred over the weekend. We understand how important quality of service and performance is to you, as it is to us. **Identification and Diagnosis** Starting Friday morning, we noticed buffering ratios increase in our QoS system. As we monitored throughout Friday afternoon and evening, we saw that the buffering ratio returned to the expected thresholds across viewership. Saturday morning, we identified that it began increasing again. Our team identified the root cause of the issue to be related to a specific header being passed from content delivery network requests. These headers were conflicting with updated browser policies, specifically in relation to updated versions of Google Chrome \(Chromium-based browsers\) and Firefox handling these headers differently than before. Throughout Saturday, our engineering team worked to investigate, mitigate, and ultimately resolve the underlying issue by updating the CDN requests to respond properly without the headers causing the problem. **Next steps** Our team is focused on ensuring stability and preventing this from happening in the future. We have multiple efforts underway to accomplish this, including: * Implementing improved monitoring services for faster detection and recovery * Re-evaluating all CDN endpoints to ensure no configurations will result in future failures * Re-evaluating multi-CDN approach to ensure the ability to quickly update configurations if needed We’re committed to improving the quality of our service, and will continue to implement improvements across all systems.
Status: Postmortem
Impact: Minor | Started At: Oct. 23, 2021, 3:21 p.m.
Description: We have seen CDN performance stabilize at this time.
Status: Resolved
Impact: Minor | Started At: Oct. 22, 2021, 8:37 p.m.
Description: Stability has been restored at this time and this issue has been resolved.
Status: Resolved
Impact: Minor | Started At: Sept. 30, 2021, 9:39 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Major | Started At: Sept. 30, 2021, 2:19 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Critical | Started At: Sept. 23, 2021, 10:36 a.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.