Skip to content
upcertain

Changelog

What changed in Upcertain

User-facing changes, newest first, dated by the day they reached production.

  1. Choose the time between confirmation checks

    • Each monitor can wait 15, 30, 60 or 120 seconds between confirmation checks, set in Advanced settings.
    • Set confirmation for many monitors at once with Confirmation on the monitor list.

  2. Alerts from alerts@upcertain.com

    • Alert emails, reports and sign-in emails are sent from alerts@upcertain.com.

  3. MCP sign-in, clearer status pages and upcertain.com

    • Connect Claude, Claude Code, Cursor and VS Code to the MCP server by signing in, read-only by default, next to API keys.
    • Status pages show each service's own downtime when several fail together.
    • Brief outages fold into one line a day, with an option to hide them; uptime still counts them.
    • A history page shows 90 days of incidents a month at a time.
    • Report an issue from Settings, Help.
    • The app moved to upcertain.com; the earlier address keeps working.

  4. Guided setup, CSV import and a new layout

    • Guided setup turns one site into several monitors in one step.
    • Import up to 200 monitors from a CSV file or a list of URLs, with a preview of every row.
    • A collapsible sidebar and a settings menu.

  5. Upcertain is live

    • HTTP, keyword, ping, port, SSL and heartbeat monitors, as often as every 30 seconds.
    • Incidents with confirmation checks, acknowledgement and recovery.
    • Alerts to email, Slack, Discord, Microsoft Teams, Google Chat and signed webhooks.
    • Status pages on your own domain.
    • Team roles, a REST API and an MCP server.