1What FoxPlug reads from UptimeRobot
These are the exact things it reads, and nothing else.
| What | The details it takes |
|---|---|
| Your monitors | one request lists the monitors on the account: id, friendly name, address, current status, the date the monitor was created |
| The down log of each monitor | the 50 newest log entries per monitor are requested; entries of the down type give a start time, a duration and the reason text UptimeRobot recorded; the newest entry counts as still open only while the monitor itself is down |
| UptimeRobot's own 30 and 90 day uptime percentages | asked for as one pair per monitor and split into a 30 day and a 90 day figure; FoxPlug passes them on as UptimeRobot gave them |
| A one-line summary of the read | how many monitors and how many are down right now, shown in the success message and kept on the connection with the time of the read |
2Moments it finds, and what each becomes
A moment is one thing that happened in UptimeRobot worth a second look. Each one is scored, then it becomes a post, a changelog entry, a thing to fix or an idea to email, or it is skipped.
a monitor is down right now
The moment is titled like this: Checkout API is down
Your monitor named Checkout API stopped answering at 08:12 UTC on Nov 9. The next time you press Check for what's new, the moment reads 'Checkout API is down', with a line saying it has been down since that day and time, the reason UptimeRobot gave if there is one, and the monitor's address. It is held back from posting and shows as the first card in the Today brief.
a monitor that went down comes back
The moment is titled like this: Checkout API was down for 42 minutes and is back
The same monitor recovers after 42 minutes. FoxPlug makes the moment 'Checkout API was down for 42 minutes and is back', with the description 'Checkout API went down on 2026-11-09 and came back after 42 minutes' plus the cause UptimeRobot recorded. It is an ordinary update that goes through scoring, and you can skip it.
UptimeRobot reports 99 percent or better over 30 or 90 days
The moment is titled like this: Marketing site stayed up 99.95% over 90 days
A monitor created more than 90 days ago, with nothing down right now, shows 99.95 percent for 90 days in UptimeRobot. FoxPlug makes one moment, 'Marketing site stayed up 99.95% over 90 days', saying it was up that share of the period according to UptimeRobot. The 90 day figure wins when both windows qualify.
3How the brain uses it
The rules below are the ones that apply to UptimeRobot. The same rules, with worked examples, are on the brain page.
- A monitor that is down becomes the first card in the Today brief and stays until the monitor reports it back up or three days pass. It is never posted and nothing about it is upbeat. How the brain decides
- When an incident is over, one short honest update says how long it was down and that it is fixed. It is written only when you press Check for what's new, and you can skip it. How the brain decides
- A 30 or 90 day availability of 99, 99.5, 99.9, 99.95 or 99.99 percent becomes an update, once per month or quarter, only when the monitor is older than that window and nothing is down. The percentage is the figure the monitoring tool reports; FoxPlug never works one out. How the brain decides
- Reads happen only when you press Build the brief or Check for what's new, never in the background. How the brain decides
4Set up UptimeRobot in a few steps
Access: read-only API key. What to give it: read-only API key.
- Open dashboard.uptimerobot.com/integrations and sign in.
- Find the API section.
- Create a Read-only API key. This kind of key can only list monitors, never create, edit or delete one.
- Copy the key.
- Paste it into FoxPlug and press Connect.
5Limits worth knowing
Where it stops, so nothing surprises you.
- Only the 50 newest log entries per monitor are requested, so a monitor with a long noisy history is cut off.
- Incidents that began more than 14 days ago are ignored; they count as history from before FoxPlug looked.
- A monitor counts as still down only when UptimeRobot's status says so, and only its newest down entry is treated as open.
- The uptime moment needs a monitor older than the window and nothing down on it; it is made once per calendar month for 30 days and once per quarter for 90 days.
- A refused key stops the read with a plain message that the API key was refused.
- A reply FoxPlug does not recognise stops the read with an error instead of being guessed at.
6What it never reads
Read only means read only, and the list below is what the code leaves alone.
- Anything that creates, edits, pauses or deletes a monitor (the read-only key cannot, and only the monitor list request is made)
- Alert contacts, status pages or maintenance windows (they are not asked for)
- An uptime figure of its own: FoxPlug never works out a percentage itself
7Questions
Is the UptimeRobot key read-only?
Yes, if you create the Read-only API key type. The connect guide says it can only list monitors, never create, edit or delete one, and FoxPlug sends only the monitor list request.
Does FoxPlug calculate my uptime?
No. It shows the 30 and 90 day figures UptimeRobot itself reports and only decides whether one is high enough to mention.
Will it post when my site goes down?
No. A monitor that is down becomes a fix-first card in the Today brief, never a post. Only the later 'was down for X and is back' update can become a post, and you can skip it.
When does it look at UptimeRobot?
Only when you press Check for what's new.
FoxPlug reads this tool only when you press Check for what's new, and only to read. Plans and limits are on the pricing page. Questions: support.