User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 2 hr ago. Last stored result reached it in 268 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 18 | 0 | 0.0 | 371 ms | 0 |
| Mon 20 | 0 | 0.0 | 361 ms | 0 |
| Mon 22 | 0 | 0.0 | 303 ms | 0 |
| Tue 01 | 0 | 0.0 | 284 ms | 0 |
| Tue 03 | 0 | 0.0 | 238 ms | 0 |
| Tue 05 | 0 | 0.0 | 273 ms | 0 |
| Tue 07 | 0 | 0.0 | 248 ms | 0 |
| Tue 09 | 0 | 0.0 | 238 ms | 0 |
| Tue 11 | 0 | 0.0 | 237 ms | 0 |
| Tue 13 | 0 | 0.0 | 276 ms | 0 |
| Tue 16 | 0 | 0.0 | 361 ms | 0 |
| Tue 18 | 0 | 0.0 | 363 ms | 0 |
| Tue 20 | 0 | 0.0 | 255 ms | 0 |
| Tue 22 | 0 | 0.0 | 241 ms | 0 |
| Wed 01 | 0 | 0.0 | 280 ms | 0 |
| Wed 03 | 0 | 0.0 | 297 ms | 0 |
| Wed 05 | 0 | 0.0 | 276 ms | 0 |
| Wed 07 | 0 | 0.0 | 264 ms | 0 |
| Wed 10 | 0 | 0.0 | 221 ms | 0 |
| Wed 12 | 0 | 0.0 | 340 ms | 0 |
| Wed 14 | 0 | 0.0 | 288 ms | 0 |
| Wed 16 | 0 | 0.0 | 377 ms | 0 |
| Wed 18 | 0 | 0.0 | 354 ms | 0 |
| Wed 20 | 0 | 0.0 | 348 ms | 0 |
| Wed 23 | 0 | 0.0 | 337 ms | 0 |
| Thu 01 | 0 | 0.0 | 325 ms | 0 |
| Thu 02 | 0 | 0.0 | 285 ms | 0 |
| Thu 04 | 0 | 0.0 | 322 ms | 0 |
| Thu 06 | 0 | 0.0 | 362 ms | 0 |
| Thu 08 | 0 | 0.0 | 281 ms | 0 |
| Thu 10 | 0 | 0.0 | 265 ms | 0 |
| Thu 12 | 0 | 0.0 | 249 ms | 0 |
| Thu 15 | 0 | 0.0 | 306 ms | 0 |
| Thu 17 | 0 | 0.0 | 452 ms | 0 |
| Thu 19 | 0 | 0.0 | 290 ms | 0 |
| Thu 21 | 0 | 0.0 | 275 ms | 0 |
| Thu 23 | 0 | 0.0 | 359 ms | 0 |
| Fri 01 | 0 | 0.0 | 509 ms | 0 |
| Fri 03 | 0 | 0.0 | 326 ms | 0 |
| Fri 05 | 0 | 0.0 | 227 ms | 0 |
| Fri 07 | 0 | 0.0 | 248 ms | 0 |
| Fri 08 | 0 | 0.0 | 252 ms | 0 |
| Fri 10 | 0 | 0.0 | 261 ms | 0 |
| Fri 12 | 0 | 0.0 | 251 ms | 0 |
| Fri 14 | 0 | 0.0 | 282 ms | 0 |
| Fri 16 | 0 | 0.0 | 376 ms | 0 |
| Fri 18 | 0 | 0.0 | 318 ms | 0 |
| Fri 20 | 0 | 0.0 | 305 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Zype yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Zype goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Zype alerts to Slack, Discord or a webhook — free.
Zype, at zype.com, is one of the AI services we monitor. Zype is the AI-enabled, API-first video content management system (CMS) for mission-critical streaming. Built for enterprises to manage, deliver, and scale video across the web, mobile, and OTT.
Zype publishes an official status page at status.zype.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 318 ms average, 227–602 ms range across 17 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Zype incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
318 ms on average over the last 24 hours (227–602 ms).
Yes, at https://status.zype.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report Zype here at once, the problem is on Zype's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Zype. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.