Checking the Esqase service status

Esqase publishes the live health of its services on a public status page at status.esqase.com. When part of Esqase seems slow or unavailable, the status page tells you whether the problem is on Esqase's side, which services are affected, and what the Esqase team is doing about it. This page explains how to read the overall status, each service row, and the incident and maintenance notices, and where to find past incidents.

Before you begin

• The status page is public. There is no sign-in, no account, and nothing to configure. It opens even when you cannot sign in to Esqase, which is often when you need it most.
• Anyone can open it. You can share the link with your team, or with a client who is having trouble reaching a booking page, a form, or a payment link.
• It is read only. It shows what the automatic checks and the Esqase team report. You cannot report a problem from it. See Common questions for what to do instead.

Open the status page

1. In any browser, on a computer or a phone, go to status.esqase.com.
2. The page opens on the current status: the overall banner at the top, then any active incidents and scheduled maintenance, then one row per service, then the incidents of the last 14 days.
3. If you are waiting for a fix, leave the tab open. The page refreshes itself about once a minute while its tab is showing, so you do not need to reload it.

The footer at the bottom of every page says how often the services are checked (Checks run every 2 minutes.) and reminds you that Times are shown in UTC. To return to the current status from any other page of the site, click Status in the header.

Read the overall status

The banner at the top of the page sums up every service in one line. Beneath that line, Last checked gives the time of the most recent check, for example Last checked 14:32 UTC. If no check has been recorded yet, the banner reads No checks recorded yet.

The banner shows one message at a time. An outage takes priority over degraded performance, and degraded performance takes priority over scheduled maintenance, so a maintenance window never hides a problem. When the page cannot confirm the current state, the out of date or unavailable message replaces all the others.

Read a service row

Below the banner, the nine services are listed in two groups, one row each.

The Applications group holds the parts of Esqase that you and your clients open in a browser:

• Firm dashboard: the Esqase app you and your team sign in to every day.
• Client app: the client portal, where your clients sign in to see their invoices, forms, documents, meetings, and messages.
• Booking pages: the public pages where clients book meetings with you.
• Intake forms: the public forms that clients and leads fill in.
• Payment links: the pages where clients pay their invoices.
• Document signing: the pages where clients sign the documents you send and open the documents you share.

The Platform group holds the services the applications rely on:

• Public API: the Esqase API that your own systems and integrations use.
• Application data: loading and saving your firm's records. Almost every part of Esqase depends on it, so a problem here usually affects the applications too.
• Background processing: the work Esqase does behind the scenes, such as sending emails and notifications, syncing calendars, and running automations. When it is slow, those can arrive late even though the apps themselves load normally.

Each row shows the service name and, on the right, a badge with its current state:

Under the name, a bar of 90 small cells shows the service's last 90 days, one cell per day, from 90 days ago on the left to Today on the right. Each day runs from midnight to midnight UTC.

• Green: every check that day passed.
• Amber: at least 99 percent of that day's checks passed.
• Red: fewer than 99 percent of that day's checks passed.
• Gray: no checks were recorded that day.

Hover over a cell to see that day's detail, for example Sep 26, 2026: 99.86% uptime, 1 failed check of 720.

Between the 90 days ago and Today labels, the row shows the service's uptime percentage across the whole 90 days, for example 99.97% uptime, or No data when there are no results yet. The percentage is rounded down, so even a single failed check keeps it below 100.00%.

When the banner reads Status information is out of date, each row also shows Last checked followed by how long ago that was (for example, Last checked 9 minutes ago), and Background processing shows Down until fresh results arrive.

Incidents and scheduled maintenance

The Esqase team posts a notice on the status page when something goes wrong and when maintenance is planned. Notices appear at the top of the page, just under the banner, in two sections that only show when they have something in them:

• Active incidents: problems the Esqase team is working on, newest first. An incident stays here until it is resolved.
• Scheduled maintenance: planned work, with maintenance already in progress first and then upcoming maintenance by start time. Maintenance stays here until it is completed.

Each notice shows:

• Its title. Click the title to open the notice on a page of its own, which you can bookmark or share.
• Whether it is an Incident or Scheduled maintenance, its current status, and its impact (Minor impact, Major impact, or Critical impact) when it has one.
• For maintenance, the planned time window in UTC, for example Sep 30, 2026, 02:00 UTC to 04:00 UTC.
• Affected: followed by the services involved.
• Every update the Esqase team has posted, newest first, each with its status, its date and time in UTC, and the message.

Incident history

Below the service rows, Past incidents covers the last 14 days, one heading per day with the most recent day first. Each resolved incident or completed maintenance is listed under the day it started, with its final status and the date and time it was resolved or completed. A day with nothing to report reads No incidents reported. Click a title to open that incident's page with every update.

To see further back:

1. At the bottom of Past incidents, click View full history. You can also go straight to status.esqase.com/history.
2. The Incident history page lists resolved incidents and completed maintenance from the last 90 days, grouped by month with the newest first. Each entry shows the same details as a notice at the top of the status page, including every update.
3. If nothing happened in that time, the page reads No incidents in the last 90 days.
4. Click Current status to return to the live page.

On a single incident's page, the Current status and History links at the top take you back to the live page or to the full history.

Common questions

The page says All systems operational, but Esqase is not working for me. What should I do? The status page checks whether each service is up for everyone. A problem that only affects your connection, your browser, or a single record may not show there. Work through these in order:

1. Open another website to confirm your internet connection is working.
2. Reload the Esqase page. If it still fails, try a private (incognito) window or a different browser, which rules out an out of date cache or a browser extension.
3. If you have had the status page open for a while, reload it and check that the Last checked time on the banner is recent.
4. If Esqase still does not work, email support@esqase.com. Say what you were trying to do, the page or link you were on, when it happened (with your time zone), and any message you saw.

Why are the times in UTC? People use Esqase in many time zones, and the status page is the same for all of them, so it shows every time in one zone: Coordinated Universal Time (UTC). The footer says so on every page. To convert, add or subtract your own offset from UTC. For example, 14:00 UTC is 10:00 in New York during daylight saving time and 22:00 in Manila. The days in the uptime bars and under Past incidents also run from midnight to midnight UTC, so an incident late in the evening in the Americas, or early in the morning in Asia, can be listed under a different date than you expect.

Why did a service show Degraded for a few minutes and then go back to Operational? One slow response or one failed check is enough to mark a service Degraded, so a brief network hiccup or a short spike in load can show up for a check or two. When the following checks pass, the row returns to Operational by itself, usually within a few minutes, and that day's cell in the uptime bar may turn amber. A service only shows Down after repeated failed checks. If a problem lasts, look for a notice under Active incidents.

Can I get an alert when an incident is posted? Not at the moment. The status page does not send emails or notifications, and there is no subscription or feed to follow. While you wait for a fix, keep the page open: it refreshes itself about once a minute.

Related

• Signing up and signing in
• Two-factor authentication (2FA)
• The client portal
• The Esqase API