merlon
Log In
PlatformSolutions IntegrationsArchitecture Pricing
Security & ComplianceBlue Team Purple TeamTrust Center Compliance & RegionsResponsible Disclosure
DevelopersAPI Reference ChangelogStatus
Help CenterResources SupportFAQ
About UsCareers ContactLog In
Pricing
System status

merlon platform status

All systems operational

Last checked 2026-07-27 09:45 UTC · all times on this page are shown in UTC. Live checks run every 60 seconds from probes in the US and Switzerland.

99.98%
Uptime — last 90 days
across all components
99.99%
Uptime — last 30 days
rolling window
182 ms
Median API response
p50, last 24 hours
Components

Current component status

Each component is monitored independently. The bar shows the last 90 days — hover a segment for that day's status.

API Operational 99.99% uptime
Web App Operational 99.98% uptime
Secure Vaults Operational 100.00% uptime
Authentication Operational 99.99% uptime
Webhooks Operational 99.96% uptime
Swiss Data Centre Operational 100.00% uptime
US Data Centre Operational 99.97% uptime
Definitions

What each component covers

So there's no ambiguity about what a green dot means, here's exactly what sits behind each monitored component.

API
The public REST API at api.merlon.ch/v1 and its regional hosts — every documented endpoint for documents, vaults, workflows, audit logs and webhooks.
Web App
The browser application where users read, edit, sign and manage documents.
Secure Vaults
The encrypted storage layer and key-management service backing every vault.
Authentication
Sign-in, SSO/SAML, MFA and session management, including OAuth2 token issuance.
Webhooks
Event generation, signing and outbound delivery, including retry queues.
Data Centres
The underlying Swiss and US facilities — power, network and compute for the region.
By region

Region status

merlon runs active infrastructure in two independent regions. Residency is enforced per vault, so an incident in one region never moves data into the other.

United States

Operational

Endpoint
api.us.merlon.ch
90-day uptime
99.97%
Median latency
171 ms (US-east probe)

Switzerland / EU

Operational

Endpoint
api.eu.merlon.ch
90-day uptime
100.00%
Median latency
188 ms (Zürich probe)
Observability

What we watch, around the clock

Status is more than a green dot. Our follow-the-sun SOC and automated monitoring track the signals that actually predict customer impact — long before most users would notice.

Availability

Synthetic probes from the US and Switzerland hit each component's health endpoint every 60 seconds.

Latency

Per-endpoint p50/p95/p99 latency, alerted when it drifts beyond baseline for a region.

Error rates

4xx/5xx ratios per endpoint, with automatic paging when 5xx crosses a threshold.

Webhook delivery

Queue depth and delivery success are tracked so backlogs are caught early.

Security signals

The SOC correlates auth, network, and endpoint telemetry to spot abnormal behaviour.

Capacity

Storage, connection pools, and background job queues are watched against headroom limits.

History

Past incidents

The last 30 days of history. Most days report no incidents; we publish a full post-incident timeline whenever something does go wrong.

July 12 – July 27, 2026 No incidents reported
Resolved

Elevated webhook delivery latency (EU region)

· Duration 1h 12m · Impact: delayed webhook deliveries in the Swiss/EU region. No data was lost; all queued events were delivered after recovery.

Investigating

13:04 UTC — We detected a rising backlog in the EU webhook delivery queue and opened an incident.

Identified

13:26 UTC — Root cause traced to a saturated connection pool after a dependency upgrade. Rollback initiated.

Monitoring

13:52 UTC — Rollback complete, queue draining normally. Watching delivery latency return to baseline.

Resolved

14:16 UTC — All backlogged events delivered, latency at baseline for 20 minutes. Incident closed.

April 20 – May 18, 2026 No incidents reported
Scheduled maintenance

Upcoming maintenance windows

Scheduled Swiss data-centre network upgrade 2026-08-09 · 01:00–03:00 UTC

A redundant network switch will be replaced in the Zürich facility. Traffic fails over automatically; customers should see no downtime, though brief single-digit-second reconnects are possible for long-lived connections.

Scheduled Authentication service database maintenance 2026-08-23 · 02:00–02:45 UTC

Routine database version upgrade for the authentication service. Sign-in may be briefly unavailable for up to two minutes during the failover; existing sessions are unaffected.

Stay informed

Subscribe to status updates

Get an email whenever we open, update, or resolve an incident, and ahead of every scheduled maintenance window.

Prefer a feed reader? An RSS/Atom feed is available on request via support.

Methodology

How we measure uptime

Transparency matters, so here's exactly what the numbers on this page mean.

Probe frequency
External synthetic checks run every 60 seconds from independent probes in the US and Switzerland, against each component's public health endpoint.
Downtime definition
A component is "down" for a minute if two consecutive probes fail from at least two probe locations. Single transient failures are not counted.
Uptime calculation
Uptime % = (total minutes − down minutes) ÷ total minutes over the window, rounded to two decimals.
Maintenance
Announced maintenance windows that cause no measurable downtime are excluded; any downtime during them is counted.
SLA
Our contractual uptime commitment is 99.9%. See the SLA for definitions and remedies.
Status FAQ

Common questions

Why is everything shown in UTC?
Because merlon runs across US and Swiss time zones, we standardise on UTC so incident timelines and maintenance windows read the same for every customer. Convert to your local time as needed.
Do incidents in one region affect the other?
No. The US and Swiss/EU regions run on independent infrastructure. An incident in one region is isolated and never causes data to move between regions.
How quickly do you post about incidents?
We open a public incident as soon as our monitoring or on-call SOC confirms customer impact — typically within minutes — and update at least every 30 minutes until resolved.
Where can I see the SLA?
Our uptime commitment and service credits are documented in the Service Level Agreement. Enterprise customers can request region-specific commitments.

Where to next

Changelog

What changed in the platform, release by release.

Learn more

Security

How our SOC monitors and protects the platform 24/7.

Learn more

Trust Center

Sub-processors, DPA, SLA and compliance in one place.

Learn more

Reliability you can build on

See how merlon keeps sensitive documents available, secure, and audit-ready — in a 30-minute demo.

Talk to Sales