System Status

Ziphay
Status

Real-time health of all Ziphay systems. Last checked: March 2026.

All Systems Operational

Ziphay is running normally. 100% uptime this month.

90 days
Today

99.6% uptime over the last 90 days

Core Services

Image Compression Engine
Canvas API · WebP, JPEG, PNG output
Operational~0ms (browser-local)
Image Upscaler
Canvas interpolation · 2×/4×/8× · Multi-pass
Operational~0ms (browser-local)
fflate GZIP Engine
PDF, video, document, archive compression
OperationalCDN: cdn.jsdelivr.net
Before/After Comparison Slider
Real image loading via Object URLs
Operational
Batch Processing
Multi-file queue, parallel compression
Operational
Google Fonts CDN
Syne + Outfit typefaces
Operational
Pro Backend API
User accounts, Stripe, cloud storage
In DevelopmentQ2 2026
Neural Compression Engine
ONNX WebAssembly neural models
Planned Q3 2026

Incident History

March 2026
✅ Resolved — File Upload Not Responding on Some Browsers
A CSS pointer-events conflict caused by a gradient overlay on the upload card was blocking click events on Chromium-based browsers. Fixed in v2.0.0 by moving the file input outside the overlay stack and wiring click via explicit JavaScript event delegation.
February 2026
✅ Resolved — Before/After Slider Showing Placeholder Instead of Real Images
The comparison slider was using CSS gradient backgrounds instead of loading the user's actual compressed output. Fixed in v2.0.0 with Object URL injection into real <img> elements after compression completes.
January 2026 — Present
✅ No Incidents — Stable Browser-Side Operation
All core compression and upscaling functionality operates client-side with no server dependency. This architecture means zero downtime risk for core features.

⚡ Why no downtime? Ziphay's core compression engine runs entirely in your browser. There is no server to go down, no API to fail, and no upload queue to slow down. Files never leave your device.