Skip to content
System status

Is HearthVault up?

Independently monitored every 5 minutes — the public record lives at status.hearthvault.family, hosted outside our infrastructure so it stays reachable during an outage.

All systems normalchecked Nov 18, 12:25 AM · every 5 min
  • Website & vault app
    Landing pages and the vault interface
    Operational
    99.755% uptime · 812 ms
    30 days agoToday
  • API
    Uploads, filing, chat and every in-app action
    Operational
    99.614% uptime · 277 ms
    30 days agoToday
  • Database
    Where your encrypted documents and settings live
    Operational
    100% uptime · 3 ms
    30 days agoToday

90-day history

Monthly uptime across the website, API and database, with every incident and maintenance window.

MonthUptimeIncidentsDowntime
September 2026no data00 min
October 202699.684%6133 min
November 202699.922%226 min

Incidents & maintenance

  1. ResolvedAPI · Nov 6, 9:43 PM → Nov 6, 9:57 PM
    API is unreachable

    Our monitor could not reach this component. We're looking into it.

  2. ResolvedWebsite & vault app · Nov 6, 9:43 PM → Nov 6, 9:57 PM
    Website & vault app is unreachable

    Our monitor could not reach this component. We're looking into it.

  3. ResolvedAPI · Oct 29, 7:41 PM → Oct 29, 7:47 PM
    API unreachable — DNS Resolving problem

    Detected by our independent external monitor: DNS Resolving problem. Lasted about 5 minutes.

    What happened

    On Oct 29, while we moved HearthVault to hearthvault.family, the new address's DNS records weren't fully in place, so for about 45 minutes (2:45–3:30 pm ET) and again for 6 minutes (3:41–3:47 pm ET) some visitors couldn't reach the site. No data was affected; everything stayed encrypted and safe.

    What we changed

    We fixed the DNS records, added independent outside monitoring of the home page and API with certificate and domain-expiry alerts, and now post every outage here automatically.

  4. ResolvedAPI · Oct 29, 6:49 PM → Oct 29, 7:39 PM
    API is unreachable

    Our monitor could not reach this component. We're looking into it.

    What happened

    On Oct 29, while we moved HearthVault to hearthvault.family, the new address's DNS records weren't fully in place, so for about 45 minutes (2:45–3:30 pm ET) and again for 6 minutes (3:41–3:47 pm ET) some visitors couldn't reach the site. No data was affected; everything stayed encrypted and safe.

    What we changed

    We fixed the DNS records, added independent outside monitoring of the home page and API with certificate and domain-expiry alerts, and now post every outage here automatically.

  5. ResolvedWebsite & vault app · Oct 29, 6:49 PM → Oct 29, 7:39 PM
    Website & vault app is unreachable

    Our monitor could not reach this component. We're looking into it.

    What happened

    On Oct 29, while we moved HearthVault to hearthvault.family, the new address's DNS records weren't fully in place, so for about 45 minutes (2:45–3:30 pm ET) and again for 6 minutes (3:41–3:47 pm ET) some visitors couldn't reach the site. No data was affected; everything stayed encrypted and safe.

    What we changed

    We fixed the DNS records, added independent outside monitoring of the home page and API with certificate and domain-expiry alerts, and now post every outage here automatically.

  6. ResolvedAPI · Oct 18, 6:22 PM → Oct 18, 6:42 PM
    API is unreachable

    Our monitor could not reach this component. We're looking into it.

  7. ResolvedAPI · Oct 17, 3:59 PM → Oct 17, 4:04 PM
    API is unreachable

    Our monitor could not reach this component. We're looking into it.

  8. ResolvedWebsite & vault app · Oct 17, 3:59 PM → Oct 17, 4:04 PM
    Website & vault app is unreachable

    Our monitor could not reach this component. We're looking into it.