How LoreVia communicates uptime, incidents, and maintenance

LoreVia publishes operational updates on this status page rather than trying to scatter service communication across support threads or unrelated product screens. If there is an outage, degradation, or planned maintenance event, this page is where users should look first.

This page explains how that status channel should be interpreted. It is the reference page for what sorts of updates you can expect, what belongs on the public status feed, and what should still go through direct support instead.

The public status page is where LoreVia communicates active incidents, planned maintenance, and notable service disruptions that affect broader product availability. It is meant for operational visibility, not for private support conversations or case-by-case account debugging.

If one user's workspace is behaving strangely while the rest of the service appears healthy, that may be better handled through support than through a public incident notice. The status page is most useful when the event is broader than a single account and should be visible to everyone affected.

When LoreVia identifies a live incident that meaningfully affects availability, core workflows, or the ability to access important features, the goal is to acknowledge the problem quickly, share what is known, and update the notice as the situation becomes clearer.

Early updates may be incomplete because they are written while the issue is still being investigated. Follow-up updates should describe whether the issue is still active, whether mitigation is in progress, and when the incident has been resolved.

Some interruptions are deliberate. LoreVia may post maintenance windows when planned work could affect sign-in, uploads, analysis features, exports, or billing-related flows.

The goal of a maintenance notice is to give users enough lead time to avoid surprise during important work sessions. Not every deployment or minor backend change requires a public maintenance notice.

Not every security issue will appear as a fully detailed public incident post while it is still active. Some issues need private containment first. LoreVia may limit public detail during an active security investigation to avoid expanding the blast radius or giving would-be attackers a roadmap before a fix is in place.

If you discover a possible security issue, use direct email instead of waiting for the status page to confirm it. The status page is a communication surface, not the intake channel for responsible disclosure.

LoreVia aims for a reliable product, but this page does not create a contractual uptime guarantee, service-level agreement, or automatic credit program unless a separate written agreement says otherwise.

Publicly visible status reporting is valuable because it is honest about real incidents, but it is not the same thing as an enterprise SLA. Users with deadline-sensitive work should still maintain sensible local backups.

Check the public status page first. If there is no incident posted and you are still seeing a serious issue, contact support with the affected account, route, and approximate time of failure.

That gives us a better starting point for deciding whether the problem is account-specific or broader than one user. Support reports from multiple users sometimes become the first signal of an emerging incident.

Use our support channel for issues that are not already covered on the public status feed, including account, content, billing, and workflow problems that persist even though the status page shows no incident.

Use our legal channel for questions about policies, refund terms, data handling, or other compliance topics. Security reports should go through private contact rather than public discussion.