Operational

Everything is where it should be.

Read at 31 Oct 2026, 09:32 · Europe/Amsterdam

100%
Uptime, 90 days
4
Incidents, 6 months
0 min
Total downtime, 6 months

Five surfaces · ninety days

Web Hosting

Servers · Linux

Operational

90 days agoDegraded · 2026-08-22Today
30 days
100%
90 days
100%

SMTP & S/MIME

Mail · Secure

Operational

90 days agoDegraded · 2026-08-22Today
30 days
100%
90 days
100%

DNS & Certificates

Network · Edge

Operational

90 days agoDegraded · 2026-08-22Today
30 days
100%
90 days
100%

Application APIs

Runtime · Node

Operational

90 days agoDegraded · 2026-08-22Today
30 days
100%
90 days
100%

AI Workflows

Automation · Signed

Operational

90 days agoDegraded · 2026-08-22Today
30 days
100%
90 days
100%

Own hardware, Drenthe

Drenthe, the Netherlands · 52.95°N 6.62°E

Single primary node on our own hardware in Drenthe, the Netherlands. Backups run daily to local disks; an off-site backup target and a second operational node are being implemented, and the failover design is written down. Production workloads run in the EU by default, in line with § 5 of our plain-language terms. The most recent incidents are listed below, measured windows and all.

Subscribe to failures

Incidents · six months

  1. 2026-09-02

    Resolved · Maintenance

    5 min, no downtime

    api

    Release deployed

    New release rolled out. The mail health check is now available to AI assistants over MCP, hosted at fyzno.com/mcp and published as @fyzno/mcp. The service restarted during the swap; no requests were dropped.

  2. 2026-08-27

    Resolved · Maintenance

    30 min, no downtime

    ai

    Integrating AI Workflows

    Integrating AI Workflows into Fyzno phone services, everything is operational.

  3. 2026-08-22

    Resolved · Maintenance

    1 min degraded

    all

    Scheduled maintenance

    All services will be down for approximately 2 minutes due to large-scale updating. UPDATE: All services are operational again, actual downtime <10 seconds.

  4. 2026-08-22

    Resolved · Maintenance

    5 min, no downtime

    smtp

    Scheduled maintenance

    Improving encryption and security.

Every incident on record, older ones included

Changes

What changed and why, written the same way as the incidents. Also in the RSS feed.

  1. 2026-10-19

    New

    Status badge and incident history

    A small badge with live status and 90-day uptime to show on your own site, and a history page that keeps every incident on record.

    Why: The status page covers six months; older write-ups now stay reachable, and a site can show who runs it with a figure instead of a slogan.

  2. 2026-10-18

    Changed

    Security updates and smaller fixes

    Framework and mail library updated, code blocks on the guides reachable by keyboard, and clearer lines on what we do not do.

    Why: Published security issues in both libraries, and a few pages that were harder to read or use than they should be.

  3. 2026-10-13

    New

    Spot the Phish

    A new mail in a practice inbox every day: real or phishing? Every clue explained afterwards.

    Why: Spotting a fake takes practice, and most of the tells are in places people never look.

  4. 2026-10-13

    New

    Guides: bounce codes, phishing, DKIM

    What each bounce code means and how to fix it, how to spot a phishing mail, and DKIM set up step by step.

    Why: These are the questions people search when mail goes wrong.

  5. 2026-10-12

    Fixed

    Domain check on missing domains

    Domains that do not exist now score 0 and are named as such.

    What was wrong: They got points for checks that cannot fail on an empty name.

  6. 2026-10-12

    New

    Bio Link+

    Your Bio Link page on your own domain, with an email address on it.

    Why: A page on your own name reads as yours.

  7. 2026-10-12

    New

    Check your domain on the home page

    Mail, website and DNS in one check, summed up in plain words.

    Why: Three full reports are a lot to read when you only want to know if things are fine.

  8. 2026-10-11

    Changed

    Terms 3.0 and an online withdrawal form

    New terms with a Dutch translation, and a withdrawal form at /legal/withdraw.

    Why: Dutch law requires a way to withdraw online from contracts made online.

  9. 2026-10-11

    Changed

    New website

    The site was rebuilt with a new design.

    Why: The old one no longer described what Fyzno does.

  10. 2026-09-02

    New

    Fyzno MCP

    The free checks are available to AI agents as an MCP server: npx -y @fyzno/mcp.

    Why: So an agent can check a domain the same way a person can.

  11. 2026-08-27

    New

    AI workflows and a 24/7 phone line

    We now build AI workflows, and the phone line answers around the clock.

    Why: Repetitive work belongs in a workflow, and outages do not keep office hours.

  12. 2025-09-10

    New

    Fyzno founded

    Hosting, mail and websites for individuals and small organisations, run and answered by one person.

    Why: Infrastructure you depend on should come with a name you can write to.

Show it on your site

A small badge with the live state and the 90-day uptime of the service you run with us. It is one image: no script, no cookie, nothing stored about who loads it. It refreshes every few minutes.

Fyzno status badge, darkFyzno status badge, minimal, dark
Fyzno status badge, lightFyzno status badge, minimal, light
<a href="https://fyzno.com/status">
  <img src="https://fyzno.com/badge.svg?theme=light" alt="Fyzno status" height="22">
</a>
theme
dark (default) or light, to match your background
style
status (default) with text, or mark for the mark and a dot only
service
hosting (default), smtp, dns, api or ai

The figure is the uptime of the service, not of one website: we measure the platform, not each site on it. If your site has a Content-Security-Policy, add https://fyzno.com to img-src.