What is down on our status page right now?
Instatus connects Memtro to your status pages and uptime monitors. It reads each page's overall status, incidents with their updates and responders, components and their status, scheduled maintenance, notices, and monitors with their availability over a period. When asked and granted, it can open, update, resolve, acknowledge or delete incidents, schedule or cancel maintenance, change components, post notices, manage subscribers and pause or mute a monitor. Instatus can also tell Memtro when an incident, maintenance or component changes, and a job can start on it. You add the Memtro address to the status page's webhook subscription yourself.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Instatus tool, reads what it needs, and answers with the source cited.
These tools change something in Instatus. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Instatus, choosing the same kinds; the tab shows Instatus's own steps. Each event can start a job, with the event as its input, and can be remembered where you choose. Instatus signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Instatus is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Which incidents are unresolved on our status page?
What is the status of each component right now?
What was the API monitor's uptime over the last 30 days?
Is any maintenance scheduled this week?
Post an update on the login incident saying a fix is rolling out.
Tom Reilly, head of support at BigCo, asked what was down before the morning stand-up. Memtro listed the unresolved incidents with their latest updates and the components not yet operational. He opened the stand-up with the facts in hand.
When an incident was opened on Northwind's status page, Instatus told Memtro and a job started. It read the incident and the affected components, then prepared a summary for Sarah Chen, the on-call engineering lead. Nothing changed on the public page until she asked.
The teams that lean on Instatus most, a question each of them asks, and what they connect beside it.
A record in Instatus is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
UptimeRobot
Honeycomb
Cronitor
FireHydrant
StatusCake
GlitchTip
GLPI
Langfuse
LibreNMS
NetBox
Snipe-IT
Woodpecker CI
Zabbix
LangSmith
Helicone
GrowthBook
Drata
Intruder
GitGuardian
Secureframe
ilert
JumpCloud
ConfigCat
Split
Aikido Security
Astronomer
Comet Opik
CrowdStrike Falcon
Detectify
Domotz
LambdaTest
LangWatch
LlamaCloud
Logz.io
Lunary
NinjaOne
Northflank
Portkey
PromptLayer
PRTG Network Monitor
Raygun
Retell AI
Runpod
Shodan
Spike.sh
Squadcast
Tenable
UpGuard
Uptime.com
Vanta
Zenduty
Cortex
WorkOS
Kandji
Automox
Huntress
SimpleMDM
Healthchecks.io
Rapid7 InsightVM
ZenhubIn the Instatus dashboard, open User settings → Developer settings and copy your API key. It acts as you on every status page you belong to.
In Memtro, open Connections → Instatus and paste the API key. Optionally add the Default status page ID, copied by right-clicking your project.
An administrator grants the actions by name to the teams that may use them. Events are turned on from the connection's Events tab, and the address is then added as a webhook subscription on the public status page.
Ask "What is down on our status page right now?"
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Instatus tools are the same everywhere.
Only when you ask, and only what it has been granted: open an incident on a status page; rename an incident or change its components; post an incident update, including resolving it; acknowledge an incident as the key's user; delete an incident; schedule a maintenance; post a maintenance update; delete a maintenance; change a component's status, name or description; add a component to a status page; post a notice on a status page; delete a notice; subscribe an email address to a status page; remove a subscriber from a status page; pause, mute or resume a monitor. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
API key. In the Instatus dashboard, open User settings → Developer settings and copy your API key. It acts as you on every status page you belong to.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Instatus, choosing the same kinds; the tab shows Instatus's own steps. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time
