SUPPORT & STATUS · SYSTEM STATUS
Current ZoikoTax service status — with freshness and source visible.
See the current source-backed state of approved ZoikoTax services, active incidents and planned maintenance. Status is time-sensitive; live states should show when they were last verified and what scope they apply to.
Partial Service Degradation
We are currently investigating elevated latency affecting API processing for North America scopes. Core dashboard services remain fully operational.
Active incidents
Elevated API Latency
Incident ID: INC-20261011-842 · Scope: North America API
Impact Summary
API requests directed to North American endpoints are experiencing intermittent latency increases of up to 2 seconds. No data loss has been detected.
Oct 11, 2026, 22:15 IST
Operations engineering has identified the cluster causing the latency and is currently shifting traffic to healthy fallback nodes. The next update will be provided within 30 minutes.
Oct 11, 2026, 21:40 IST
We are investigating reports of elevated latency affecting API endpoints in the North America region.
Service health
Registry-driven component states reflecting current public operational health. Missing or unverified data is explicitly marked as unknown.
Core Platform
AvailableAvailableIntegration & Delivery
DegradedAvailablePlanned maintenance
Database Cluster Upgrade
Window: Oct 20, 2026, 02:00 - 04:00 IST
Routine maintenance on reporting clusters. We expect up to 5 minutes of unavailability for historical exports. No impact expected for core ingestion.
Incident history
Dashboard loading delays
Oct 02, 2026Resolved — Root cause mitigated successfully.
European endpoint packet loss
Sep 28, 2026Resolved — Upstream transit provider issue.
Still having trouble?
If your issue is not reflected in the current public status, use Customer Support for account-specific help. The absence of a public incident does not by itself confirm that an individual account, transaction or workflow is unaffected.
Developer handoff
For API, webhook, batch and integration-specific technical guidance, use Developers/Documentation. Any developer status view should reference the same canonical incident and service-health authority.
Security handoff
Found a potential security vulnerability? Use Responsible Disclosure. System Status is for operational availability and approved incident communication.
Coverage handoff
Current service health does not establish market or capability availability. Use Coverage for governed availability.
System Status FAQ
Use System Status for the current authoritative answer. The page should show the source-backed overall state, affected services, active incidents and when that information was last verified. If status data is stale or unavailable, it must say so rather than defaulting to operational.