01 Getting Started(7)

• Quick Whois Search
• Live Detected Outages
• Free Accounts Inactivity
• Account Dashboard
• Live Queue Status
• Top Notifications

02 Contact Lists(40)

• Discord Integration
• Remove entry from Contact List
• Pushover Notifications
• Google Chat Integration
• SMS Notifications
• Do Not Disturb Schedule

03 Blacklist Monitor(62)

• 03.01 RBL Info(15)

• Group Actions
• Add multiple entries at once
• Change Blacklist Monitor Label
• Meet The Interface
• View further blacklisting details in your reports
• Filter Monitors Based on Recent Changes

04 Uptime Monitor(71)

• Schedule Maintenance
• Auto Refresh Timer
• Location Fails Warning
• Daily/Weekly/Monthly Uptime Monitoring Reports for Status Pages
• Set Domain Expiration Date Manually
• How to order Categories

05 Server Monitor(44)

• Server Agent – Custom Variables
• Install the HetrixTools Server Monitor Agent
• Accessing Server Monitoring Data
• View Running Processes
• HDD/SSD/NVMe Drive Health Monitor
• Reboot Required Warning

06 Status Pages (Bulk Reports)(14)

• How to create a beautiful Uptime Status page
• Embed Status Page On WHMCS Network Status
• Create Status Page
• Add Twitter Feed to Bulk Report
• Delete a Status Page
• How to remove Incident from Status Page

07 Billing(24)

• Remove a saved Payment Method
• Add extra monitors to your order
• Suspension/Termination
• Upgrade/Downgrade
• Cancel Order / Downgrade to the Free plan
• Pay via Stripe using Bitcoins

08 White Label(11)

• White Label is not package exclusive
• How to set up a White Label Domain or Subdomain
• Add A White Label Domain Name
• Embed White Label Status Pages and Reports
• Fixed Header
• Default White Label Landing Page

09 Support(10)

• We Need Your Feedback
• Disable Bulk Report Title
• Opening A Ticket
• Viewing Your Tickets
• Which Support Desk Is This?
• Difference between ‘not ideal’ and ‘critical’ RAID health warnings

10 Settings(21)

• Blacklist monitor change notification threshold
• Default Reports Per Page For Bulk Reports
• Timezone
• Blacklist Monitor Color Indicators
• Sub-Accounts
• Enable Uptime Monitor Plain Text Email Notifications

11 Affiliate Program(6)

• Affiliate Program Overview
• Affiliate Dashboard
• Earn Extra Monitors By Referring New Users
• What Affiliate Program Is This?
• Withdraw Earnings
• Earnings Calculator

12 F.A.Q.(40)

• Do you offer Bulk Blacklist Check?
• How do I access my Uptime Reports?
• What payment methods do you accept?
• If I wasn’t referred by an affiliate, can I get the commission as discount for my order?
• My IP is blacklisted on SPFBL, so why doesn’t your platform show it?
• How to increase Linux Server Monitoring Agent metrics collection intervals

13 Best Practice(28)

• 13.01 Blacklist Monitor(13)

• 13.02 Uptime Monitor(13)

• How to set up Keyword Monitoring
• The importance of ordering your monitors list
• Uptime Monitoring For Display
• This is how we use our own platform when performing non-impacting planned maintenance on our infrastructure
• How to use Quick PING
• How to create a beautiful Uptime Status page

14 Common Issues(3)

• Failed to read CPU temperature natively
• Server Monitoring Agent not sending data from an ArchLinux server
• Disabling the ‘Reboot Required’ warning icons

15 API(19)

• Using the API Relay
• v2 Set Bulk Report Announcement
• v2 List Blacklist Monitors
• API v3
• Blacklist Check API
• API – Edit Blacklist Monitor

16 Announcements(178)

• 16.01 Incidents(57)

• 16.02 Network Changes(15)

• v0.9.38 – Categories
• v0.9.25 Beta – dnsrbl.org RBL added
• v0.9.52 – Uptime Monitoring Scheduled Maintenance & Blacklist Monitoring Webhook Notifications
• v0.9.8r2 Beta – sorbs.net false positive
• v0.9.73 – New Server Monitor Alerts
• v0.9.62 – Changelog

17 Common Errors(8)

• Error 35: error:0A000152:SSL routines::unsafe legacy renegotiation disabled
• HTTP Code [403] Error 0: (Xms)
• Error 0: Name or service not known
• Error 35: error:0A000102:SSL routines::unsupported protocol
• Error 7: Failed to connect to <target>: Connection refused
• Error 92: HTTP/2 stream 0 was not closed cleanly: PROTOCOL_ERROR