API Status

API Status

This page publishes the live, current status of the LICOFY platform services: the marketplace storefront, the licencing and activation API, hosted instance provisioning, the portal, and infrastructure that products depend on. Check here first when something seems slow or unreachable, and use the contact page if you see a problem that is not reflected here so we can investigate quickly.

Service Areas We Monitor

We monitor the following services continuously: the marketplace web application, including product search, category browsing, and checkout; the licencing API that products call to verify keys and read entitlements; the provisioning pipeline that creates and manages hosted instances; the portal, including purchases, licences, billing, messages, and notifications; the blog, documentation, and CMS pages; and the underlying infrastructure, including the web server, database, cache, and worker queues that these services depend on. Status is published automatically from our monitoring so it reflects reality rather than manual updates.

What Status Means

Operational means the service is fully available and performing normally. Degraded means the service is available but experiencing reduced performance, elevated latency, or a non-critical feature is unavailable; in this state we are actively working to restore full capacity. Maintenance means the service is intentionally unavailable for scheduled work; maintenance windows are announced ahead of time through notifications and, where relevant, the blog. Outage means the service is unavailable and we are actively restoring it; updates are posted here until service returns.

Incident and Maintenance Policy

We aim for high availability for all buyer-facing flows and treat the licencing API with special care, because many products depend on it at runtime. Planned maintenance is scheduled for low-traffic periods where possible and announced in advance with an estimated duration. Incidents are recorded with start time, affected services, cause where known, and resolution time; a history is kept so you can review reliability over time and plan your own deployments with confidence.

What to Do During an Incident

If you are experiencing an issue and this page shows everything operational, please first confirm that the problem is not on your network, your DNS, or locally cached data. If the platform still misbehaves, report it through the contact page with the exact time, the affected feature, and any error message you saw. Transient failures in hosted product instances are automatically retried where safe; if your instance is unavailable and you have billing or data concerns, support prioritises hosted incidents and keeps the affected subdomains up to date.

Subscribe to Updates

Status announcements are published here and, for impact events, through platform notifications and the blog. For the technical history of what has shipped, see the changelog announcements on the blog. You can bookmark this page and refer to it whenever you are planning maintenance of your own or troubleshooting a slow response.

Region and Instance Health

Hosted product instances run on infrastructure that is monitored per region and per instance, so the status page can report not only whether the platform is healthy but whether a specific product deployment is behaving normally. If an individual instance reports elevated resource usage, repeated restarts, or a failed health check, our systems flag it automatically and apply the configured remediation steps, which may include restarting the process, rotating credentials, or restoring from the latest backup. Buyers see the result as a stable, responsive product, and sellers can rely on the same telemetry to diagnose issues in their own code. This per-instance visibility means that a problem in one product rarely affects another, and it lets us promise meaningful isolation for buyers who run multiple products on the same account.

The status page also records the health of integrations that products depend on, such as the payment gateways used at checkout and the object storage used for script downloads. If a gateway provider reports an incident, we surface it here alongside our own services so that a slow checkout or a delayed download can be explained within seconds. For organisations that build on LICOFY, we recommend subscribing to notifications for status changes and maintaining their own probes against the licencing endpoint so that client-side monitoring exists even when the rest of the network is behaving normally.