Service incident log

No incidents recorded.

Every disruption that affects the service is recorded here: when it began, what it affected, and when it was resolved. If something looks wrong on your side and is not listed, the domain checker reads your live DNS in about 30 seconds.

Last reviewed

October 15, 2026

Incidents logged

Since September 5, 2026

Currently open

As of the review date

Enterprise uptime term

99.99%

Written into Enterprise agreements. Public measurement is in preparation.

Faster answer

~30s

A live read of your own DNS

01 — The log

Nothing has been recorded yet.

This log opened on September 5, 2026 and has no entries. When a disruption affects the service, it is recorded here with the time it began, what it affected, each update, and when it was resolved.

If something looks wrong to you right now, tell us and we will look into it.

02 — Where it runs

Three live regions.

Where tenant data is hosted, chosen when a tenant is created. Environments provisioned on request and regions not yet deployed are listed separately below.

United States

AWS

European Union

AWS

Asia Pacific

AWS, Tokyo

Provisioned on request, under an Enterprise agreement

HIPAAHIPAA-eligible (US)An isolated environment for tenants whose forensic samples may carry PHI, built on HIPAA-eligible AWS services under an AWS Business Associate Addendum. That addendum is between AWS and us; our own BAA with you is separate and still in preparation.

GOVAWS GovCloud (US)Hosting in AWS GovCloud (US) for public-sector tenants. This is where the environment runs, not an authorization: we are not FedRAMP authorized.

Announced, not yet deployed

CACanada— Deploying shortly

03 — Limits

What a green page does not prove.

Status pages are the most over-trusted artifact in software. Ours tells you about our infrastructure and nothing else. Here is precisely where it stops being useful.

It covers our infrastructure, not your mail

Every service here can be healthy while your reports stop arriving — because a DNS record changed, a provider stopped sending, or your own sending platform broke. None of that shows up on a status page.

It cannot see the mailbox providers

Aggregate reports arrive because Google, Microsoft, Yahoo and the rest choose to send them. When one of them delays a batch, our side is working normally and there is nothing here to indicate otherwise.

Your own domain check is the faster answer

If you are asking whether something is wrong right now, the domain checker reads your live DNS and answers in about 30 seconds. That is a measurement; this page is a log.

Asking whether something is wrong right now?

A domain check is a measurement taken now; this page is a record of our incidents. For “is my DMARC still working”, the first one answers and the second one cannot.

Check your domain Report a problem

The checker reads your live DNS. This page records our incidents.