Public Status

Dilly should feel operationally calm, not mysteriously silent.

This is the public surface for uptime, incidents, and maintenance communication.

When a system touches profiles, applications, reminders, and AI guidance, users should not have to guess whether it is healthy. This site exists so Dilly can communicate like a serious operating system, not like a black box.

View Incident History Read Reliability Notes
Current Services

The surfaces that matter most stay visible here.

Dilly is one connected system, so the status surface tracks the parts that create the most downstream impact when they drift.

Healthy Profile and account system Onboarding, sign-in, profile reads, and profile edits are the foundation for every other surface.
Healthy Jobs and fit narratives Listing ingestion, filters, and fit reads are monitored because they influence search, tracker, and resume work.
Healthy Resume generation and audit Forge and Audit stay visible here because degraded output is not always obvious from one request alone.
Healthy Chat and AI surfaces Context seeding, daily limits, and model-backed responses should fail legibly instead of silently.
Healthy Calendar and reminder sync Event sync is tracked separately because reminder failures break trust quickly.
Observed Background jobs and briefs Nightly refreshes, brief generation, and weekly surfaces are treated as visible operational layers, not hidden back-office work.
Communication Rules

What users should be able to expect.

Incidents We post visible incident summaries. If a failure affects user trust, system state, or core surfaces, it belongs here in plain language.
Maintenance We announce planned disruption. If work is likely to degrade sync, chat, or generation, the system should not pretend everything is normal.
Recovery We say what recovered and what still needs watching. Healthy does not mean vague. It means users know what changed and whether any follow-up is still underway.
Why Status Exists

Connected systems need public operational trust.

Dilly is not just one isolated screen. When profile, search, reminders, and AI surfaces all read shared context, outages carry through the system. A public status site makes that visible instead of making users triangulate from broken screens.

Related surfaces

help.hellodilly.com explains how to use Dilly when things are working. privacy.hellodilly.com explains how Dilly handles trust and data. This site explains operational health.