Web Hosting
Servers · Linux
Operational
- 30 days
- 100%
- 90 days
- 100%
Read at 31 Oct 2026, 09:32 · Europe/Amsterdam
Servers · Linux
Operational
Mail · Secure
Operational
Network · Edge
Operational
Runtime · Node
Operational
Automation · Signed
Operational
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.
2026-09-02
Resolved · Maintenance
5 min, no downtime
api
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.
2026-08-27
Resolved · Maintenance
30 min, no downtime
ai
Integrating AI Workflows into Fyzno phone services, everything is operational.
2026-08-22
Resolved · Maintenance
1 min degraded
all
All services will be down for approximately 2 minutes due to large-scale updating. UPDATE: All services are operational again, actual downtime <10 seconds.
2026-08-22
Resolved · Maintenance
5 min, no downtime
smtp
Improving encryption and security.
What changed and why, written the same way as the incidents. Also in the RSS feed.
2026-10-19
New
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.
2026-10-18
Changed
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.
2026-10-13
New
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.
2026-10-13
New
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.
2026-10-12
Fixed
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.
2026-10-12
New
Your Bio Link page on your own domain, with an email address on it.
Why: A page on your own name reads as yours.
2026-10-12
New
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.
2026-10-11
Changed
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.
2026-10-11
Changed
The site was rebuilt with a new design.
Why: The old one no longer described what Fyzno does.
2026-09-02
New
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.
2026-08-27
New
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.
2025-09-10
New
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.
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.
<a href="https://fyzno.com/status">
<img src="https://fyzno.com/badge.svg?theme=light" alt="Fyzno status" height="22">
</a>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.