Sign in Get started
live system status

Nightlamp status

A monitoring service should show you its own vitals. The components below are computed from the same probes and scheduled health checks that run in production — when something can't be verified, it says unknown instead of pretending.

Checking live component status…

Honesty note: this page reports live component health and is served from the same infrastructure it reports on. If it's unreachable, that itself is signal — email hi@nightlamp.app and a human will answer.

components

Component health

  • API

    Live state loads in your browser from the Nightlamp API.

    unknown

  • Probe pipeline

    Live state loads in your browser from the Nightlamp API.

    unknown

  • Data storage

    Live state loads in your browser from the Nightlamp API.

    unknown

  • Authentication & encryption

    Live state loads in your browser from the Nightlamp API.

    unknown

  • Alert dispatch

    Live state loads in your browser from the Nightlamp API.

    unknown

  • Email dispatch

    Live state loads in your browser from the Nightlamp API.

    unknown
methodology

What we monitor about ourselves

Probe pipeline

The probes that watch customer apps leave timestamps every time they run. If the most recent probe activity is older than twice its normal cadence, this page says degraded — the same standard we hold customer monitors to.

Deep health checks

Every five minutes a scheduled run exercises storage round-trips, event ingest, magic-link auth, credential encryption, and the alerting dispatch path. Storage, authentication, and dispatch statuses come from the latest run.

Email dispatch

The same run verifies our email provider is reachable with valid sending credentials. That's reachability, not per-message delivery confirmation — we label it accordingly instead of overclaiming.

What you won't find here

No invented uptime percentages and no green-by-default badges. We only publish states we can compute from recorded data; when we can't verify a component, it is marked unknown.

incident history

Public incidents

No public incident history yet — we publish post-mortems here as they happen. Until then, an honest empty section beats a wall of retroactive green checkmarks.

platform status hub

Is the platform down, or is it just your app?

Official platform status pages tell you when the platform is down. They say nothing when your app breaks on its own — a failed webhook, a paused backend, an expired key. These pages show each platform's live status and how to triage the difference.

Newsletter

One real no-code incident + the fix, monthly

A post-mortem from a real no-code outage — what broke, how it was found, and the fix — once a month. Confirming also gets you the no-code incident runbook pack.

Double opt-in. One-click unsubscribe. No spam, ever.