Service Status & Reliability

Reliability by design

DMARC Engine is built to be resilient from the ground up. The entire platform runs on a global edge network rather than on servers we manage ourselves, which removes whole categories of single points of failure. Our compute runs as serverless workers that execute close to your users and scale automatically with demand, so we do not depend on a single machine, a single data centre or a single region staying healthy. Requests are routed over a global anycast network, which directs traffic to the nearest available location and routes around regional disruption automatically. Because there is no fixed origin server to keep online, there is no traditional maintenance window for the core application, and capacity scales up and down to match load without manual intervention. Our infrastructure provider holds SOC 2 Type II and ISO 27001 certifications. You can read more about our wider controls on our Security page.

How we communicate incidents and maintenance

If a service-affecting incident occurs, our priority is to resolve it quickly and to keep you informed in a way that is honest and proportionate. Depending on the nature and scope of an incident, we may:

• Email the administrators of affected accounts directly, so that the people responsible for your domains hear about it from us.
• Post a notice on this page describing what is happening, who is affected and what we are doing about it, with updates as the situation develops.
• Share updates on our public channel at @dmarcengine where appropriate for wider awareness.
• Publish a brief summary once an incident is resolved where it is useful to explain the cause and any follow-up actions.

Where we need to carry out planned maintenance that could affect availability, we will aim to announce it in advance and to schedule it to minimise disruption. In practice, the serverless architecture described above means most changes can be rolled out without downtime.

Reporting a problem

If you think something is wrong, please tell us so we can investigate. You can reach our reliability team at status@dmarcengine.com, raise a request through our contact page, or use the in-app support options available when you are signed in. When reporting an issue it helps to include the affected domain, the approximate time the problem started, what you were trying to do and any error messages you saw. Security-related concerns should be reported as described on our Security page.

Data durability

Your data is stored on managed, redundant cloud storage rather than on disks we maintain ourselves. Account, domain and configuration data is held in a managed SQL database, and raw DMARC aggregate (RUA) and failure (RUF) reports are stored in managed object storage. Both are operated with platform-level redundancy and durability built in, so your records and ingested reports remain available across distributed infrastructure rather than living on a single server. This durability model works alongside the security controls and encryption described on our Security page.

A note on this page

The component statuses above are produced by live checks against our platform, and the 90-day history is recorded from real availability data, so days before tracking began are shown as "no data" rather than back-filled. This page is provided in good faith to give you a transparent view of how we approach reliability, and it may be updated as our practices and tooling evolve. It does not form part of a contractual service-level commitment; any service levels that apply to your subscription will be set out in your agreement with us. If anything here is unclear, please get in touch at status@dmarcengine.com.