01 Getting Started(7)

• Account Dashboard
• Top Notifications
• Live Queue Status
• Say NO To Pageloads
• Free Accounts Inactivity
• Live Detected Outages

02 Contact Lists(40)

• Pushover Notifications
• SMS Notifications
• Default Contact List
• Splunk/VictorOps Integration
• HipChat Integration
• Blacklist Monitoring Webhook Notifications

03 Blacklist Monitor(63)

• 03.01 RBL Info(15)

• Export as Text
• Blacklist Monitor Report
• Group Actions
• Block View
• Delete Multiple Blacklist Monitors
• Queue Priority

04 Uptime Monitor(73)

• Daily/Weekly/Monthly Uptime Monitoring Reports for Status Pages
• How to whitelist our Uptime Monitoring Nodes in CSF
• Categories
• Add private notes to your Uptime Monitors
• Set Domain Expiration Date Manually
• How do we perform Uptime Monitoring network changes

05 Server Monitor(46)

• Debug Mode – Windows Agent
• How to install S.M.A.R.T. (smartmontools) on your server (macOS)
• Resource Usage Privacy
• Service Monitoring
• Misconfigured Network Interface Name (PHP Agent)
• Installing the Windows Server Monitoring Agent

06 Status Pages (Bulk Reports)(15)

• Uptime Percentage Period (per status page)
• Create Status Page
• Protect your Status Page with a Password
• Remove monitors from a Status Page
• Add monitors to a Status Page
• How to order Categories

07 Billing(24)

• Remove a saved Payment Method
• Change Billing Cycle
• Account Credit
• Creating and Canceling Stripe Subscriptions
• Placing A New Order
• The Basic Package

08 White Label(11)

• Configure DNS settings for your White Label Domain
• Add A White Label Domain Name
• Embed White Label Status Pages and Reports
• White Label is not package exclusive
• How to set up a White Label Domain or Subdomain
• Fixed Header

09 Support(10)

• Opening A Ticket
• Which Support Desk Is This?
• Disable Bulk Report Title
• API Keys Access
• Difference between ‘not ideal’ and ‘critical’ RAID health warnings
• In-House Support

10 Settings(21)

• Activity Log
• Inherit Password Protection
• Change Password
• Dark Mode
• Sub-Account – Switch Account
• Sub-Accounts

11 Affiliate Program(6)

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

12 F.A.Q.(40)

• How do blacklist notifications work? When do I get notified?
• How are your Uptime Monitoring statistics calculated?
• If I wasn’t referred by an affiliate, can I get the commission as discount for my order?
• Why does my Uptime Monitor show as Offline, when it’s actually not?
• How to edit White Label domain settings?
• Where can I see my Package Limits?

13 Best Practice(28)

• 13.01 Blacklist Monitor(13)

• 13.02 Uptime Monitor(13)

• How to track your uptime using HetrixTools
• How to use Quick PING
• Hiring Freelancers For Delisting
• Markdown
• This is how we use our own platform when performing non-impacting planned maintenance on our infrastructure
• Add your Microsoft SNDS Key to your HetrixTools account (SNDS Monitoring)

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)

• Understanding our APIs
• API – Delete Uptime Monitor
• API v3
• API – Edit Blacklist Monitor
• Understanding API Limits
• API – Add Website/Ping/Service/SMTP Uptime Monitor

16 Announcements(178)

• 16.01 Incidents(57)

• 16.02 Network Changes(15)

• v0.8.6 Beta
• v0.9.13 Beta – Ping Monitoring & Company Info
• Announcing the new Blacklist Monitor pricing structure
• v0.9.67 – ‘Google Safe Browsing’ Blacklist Monitoring
• v0.9.60 – Low SMS Credit Warnings
• v0.9.53 – Blacklist Monitor Bookmarks

17 Common Errors(10)

• Error 7: Failed to connect to <target>: Connection refused
• Error 0: Name or service not known
• Error 92: HTTP/2 stream 0 was not closed cleanly: PROTOCOL_ERROR
• Error 35: error:0A000102:SSL routines::unsupported protocol
• Error 0: keyword not found
• Error 35: error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure