Allowlist monitoring node IPs
Connect
SPIRITT
Updown.ioUpdown.io
Uptime, reported and routed
SPIRITT turns your Updown.io checks into operations. It reads every check's status, uptime and settings, builds SLA reports and status pages, routes downtime to the right owner, and keeps your firewall and allowlists in step with Updown.io's monitoring node IPs.
What you can do with Updown.io.
Every check, one view
Status, uptime and settings for all your checks, rolled into dashboards and reports.
Monitors never blocked
IPv4 and IPv6 node addresses kept current in your firewall and allowlists.
Downtime reaches an owner
Scheduled sweeps that route down checks to the team that owns the service.
Works with your other apps.
Get started in three steps.
01
Open your workspace
Start a SPIRITT workspace for your uptime operations and describe your services and owners.
02
Connect Updown.io
Connect Updown.io, plus your firewall, alerting and reporting apps.
03
Hand over the mission
Hand over the reporting. SPIRITT builds it, runs it and routes what needs attention.
Hand over a mission.
Choose a mission. Make it yours.
Put Updown.io to work.
Uptime, reported and routed
Questions
Updown.io, with SPIRITT.
01What does SPIRITT read from Updown.io?+
All your checks with status, uptime and settings, plus the monitoring nodes and their IPv4 and IPv6 addresses.
02Can it alert when a site goes down?+
Yes. It sweeps check status on your schedule and routes down checks to Slack, PagerDuty or any connected app.
03Can it build a status page?+
Yes. SPIRITT builds and hosts a status page that reads live check status.
04Can it keep allowlists current?+
It fetches the current node addresses and syncs them into your firewall or CDN rules.
05Does it create or change checks?+
Checks are managed in Updown.io. SPIRITT reports on them and finds services that still need one.
06How do I connect Updown.io?+
Open a workspace, connect Updown.io and your alerting or firewall apps, then describe what to report and route.