Advanced Uptime Monitor

​

What You’ll Learn

• Creating and managing uptime monitors
• Connecting supported monitoring services
• Understanding monitor fields and actions
• Creating monitors for connected child sites

---

The MainWP Advanced Uptime Monitor Integration allows you to monitor your websites’ uptime by integrating with uptime monitoring services through their APIs. This add-on enables you to create, edit, display, start, pause, or delete your monitors directly from the MainWP Dashboard. The integration currently supports these uptime monitoring services:

• Uptime Robot
• Better Uptime
• NodePing
• Site24x7

The integration itself does not check for uptime, nor does it notify in case of some event. Both of these actions are performed by third-party uptime monitoring services.

​

Create New Monitor

​

Monitor Types

• http(s): Perfect for website monitoring. The service regularly sends requests (which are the same as if a visitor is browsing your website) to the URL and decides if it is up or down depending on the HTTP statuses returned from the website (200-success, 404-not found, etc.)
• ping: Good for monitoring a server. Ping (ICMP) requests are sent, and up/down status is decided according to whether responses are received. Ping is not a good fit for monitoring websites as a website (its IP) can respond to ping requests while it is down (which means that the site is down but the server hosting the site is up)
• keyword: Checks if a keyword exists or does not exist on a web page
• port: Good for monitoring services like SMTP, DNS, POP as all these services run from a specific port, and Uptime Robot decides their statuses based on whether they respond to the requests

​

Edit Monitor

​

Start-Pause Monitor

​

Monitor Statistics

​

Delete Monitor

​

Create Monitors for All Child Sites

To automatically create monitors for all child sites that don’t have corresponding monitors:

​

Connect Your Uptime Robot Account

To get your Uptime Robot API Key to use the MainWP Advanced Uptime Monitor Integration, visit the Uptime Robot Webpage. Before being able to create, display, or manage Uptime Robot monitors, you need to add your Uptime Robot API key to your Advanced Uptime Monitor Integration. After you connect your account, you can set the default alert contact. The integration validates the API key when you click Save Settings. If Uptime Robot rejects the key, the integration keeps your previous key and shows the validation error. When you save a different API key, the integration clears stored uptime data and synchronizes monitors from the new account.

​

Uptime Robot API key permissions

The integration connects to the Uptime Robot REST API v3 and detects the permission level of your API key:

• A key with write access allows all monitor actions from the MainWP Dashboard.
• A read-only key lets you view monitors and uptime statistics only. The Settings tab shows a Connected — read-only notice, and the Create New Monitor, Edit, Delete, Start/Pause, and bulk action controls are disabled.
• If Uptime Robot rejects the key entirely, the Settings tab shows Authentication failed — the API key must be replaced. Create a new API key in your Uptime Robot account and save it in the Settings tab.

​

Uptime ratio refresh

The integration stores uptime ratios for each Uptime Robot monitor and refreshes them in the background:

• The monitor list shows the all-time uptime ratio. If the all-time ratio is not available yet, the last 24-hour ratio displays instead.
• When monitors are missing their 24-hour ratio, opening the Monitors tab starts a synchronization dialog. The dialog refreshes each monitor and reports progress as it goes. If Uptime Robot rate limits the requests, the dialog shows a retry countdown and continues automatically after the wait period.
• A scheduled job named MainWP AUM UptimeRobot refresh runs once hourly. Each run refreshes the 24-hour ratio for a small batch of monitors, rotating through all monitors across successive runs, and synchronizes recent incidents from your Uptime Robot account.
• To reload monitor data from Uptime Robot on demand, click the Reload Uptime Robot data button on the Monitors tab.

If you run your MainWP Dashboard with WP-Cron disabled, schedule the direct worker file for the hourly refresh as described in Disable WP-Cron.

​

Connect Other Monitoring Services

The Settings tab also supports:

• Site24x7 - Select the data center, enter the Client ID and Client Secret, then complete the Administrator, Reports, and Operations authorization steps.
• NodePing - Enter the NodePing API Token.
• Better Uptime - Enter the Better Uptime API Key.

​

API limitations of the free Uptime Robot plan

Uptime Robot has recently reduced the limit to only 10 requests per minute. Requests include creating new monitors through the MainWP integration and fetching information about existing monitors. Reaching the limit is fairly easy for a large number of sites. This limit is most often hit when creating monitors for all sites by clicking the “Create Monitors for All Sites” button in the UI. You will likely be able to create 2 or 3 monitors per attempt and receive an error (red exclamation mark) for other sites because the API limit will be reached. When Uptime Robot returns a rate-limit response, the integration pauses further requests for the wait period reported by the API and retries automatically. During uptime ratio synchronization, the progress dialog shows a countdown until the next retry.

​

How to get a Better Uptime API token

To get the Better Uptime API token:

​

Team Control Permissions

If you use the Team Control Extension, the Advanced Uptime Monitor respects each role’s Allowed Child Sites configuration. Users signed in with a restricted role only see monitors that belong to the child sites they are permitted to access; monitors for sites outside their scope are hidden from the Monitors tab and from related views. Notes on how this works:

• Each monitor is automatically associated with the matching child site based on its URL. Monitors created before this association existed are migrated automatically the first time they are viewed or updated.
• Monitors that cannot be matched to a child site (for example, IP-based or standalone endpoints) remain visible to all users so that they are not accidentally hidden.
• Scheduled uptime checks, WP-CLI commands, and the MainWP REST API are unaffected and continue to process every monitor regardless of the current user’s role.

No additional configuration is required. Assign Allowed Child Sites to each role in Team Control as described in the Define Role Permissions section, and the uptime monitor list will honor those permissions automatically.

---

​

Related Resources

• Monitoring Add-ons - Browse all monitoring tools
• Domain Monitor - Track domain expiration
• SSL Monitor - Monitor SSL certificates
• Team Control - Manage role-based access to monitors