Status pages for your uptime monitors

A status page shows your customers whether your app is up, without them having to ask. It lists the uptime monitors you pick, each with its current status and a bar per day, plus the incident and maintenance notices you post. It lives at https://app.lampwick.dev/status/your-name, updates itself from the monitors, and needs no login, cookies or JavaScript to view.

What you get

• Overall status at the top: All systems operational, Partial outage, Major outage, Ongoing incident or Maintenance in progress, worked out from the monitors and your notices.
• Daily uptime per component: green from 99.5%, orange from 95%, red below. The bars cover up to 90 days, fewer when data retention is shorter; on a phone, 30.
• Incident and maintenance notices: incidents go through investigating, identified, monitoring and resolved; maintenance through scheduled, in progress and completed, with a start and end time in UTC. Closed notices stay visible for 14 days.
• Monitors from several projects on one page, each under a public name you choose. The page never shows URLs, error messages, status codes, response times or project names.
• JSON for your own site: https://app.lampwick.dev/status/your-name.json, with CORS open, so you can show the status in your app's footer or help center.
• Drafts and preview: build the page, preview it as a team member, then Save and publish. Unpublish takes it offline at once.

Is there a free status page?

Not on the Free plan. Status pages start at Pro, €29 per team per month, which also includes 20 uptime monitors every minute and 5 projects. Free gives you 3 monitors and alerts to your own team, without a public page. If a free public status page is the only thing you need, a dedicated status page tool will fit better than Lampwick.

Set it up

1. Add an uptime monitor for each part you want to show, such as the website and the API.
2. Go to Status pages in the sidebar, enter a Title and a Slug (the end of the URL) and click Create status page.
3. Tick the monitors under Monitors on the page, give each a public name and set the order.
4. Click Save and publish, then open the URL in a private window.

During an outage, open the page and use Post a notice. All steps and limits: the status page docs.

What it doesn't do

• No custom domain: the page is always on app.lampwick.dev/status/…. A link from status.example.com can redirect there.
• No logo, colors or custom CSS.
• Visitors can't subscribe to updates by e-mail or SMS.
• Notices are plain text, posted by a team owner by hand. Lampwick doesn't post an incident when a monitor goes down.
• At most 10 status pages per team, and team owners only: members can view them, not change them. An AI agent on the MCP server can read status pages but not create or change them.

What it costs

When a team moves back to Free, its status pages go offline and come back after an upgrade. See pricing.

Related

• One status page per client: Lampwick for agencies.
• Tell your own team first: alerts.
• Status pages for apps built with Lovable, Replit or v0: monitoring for AI-built apps.

Start free, add your monitors, and publish a page when you move to Pro.