With newest version of AppBeat you can now periodically run Whois for your domain: You can customize notification rules to receive message when domain is about to expire or set custom regular expression for Whois response: For example, you can set regular expression to ensure correct name servers, registrant name, domain status, or any other information returned from Whois server. Please let us know if you have any questions about this feature.

In newest AppBeat version 1.7.0 you can now define quiet hours for your users, services and/or third-party integrations (I will refer to these as “resources”). Quiet hours are recurring time periods during which alerts (outgoing notifications) are muted for selected resource(s). Quiet hours does not affect monitoring, just notifications. This means that you will always be able to check log entries, even during effective quiet hours. You can access this new feature from “Alerting” module and by clicking “Quiet hours” tab as shown below:

We published new web application with improved UX and some new useful features: you can now quickly filter your checks on “Live status” screen: added quick actions for monitored checks and services “Live status” simplifications due to new quick actions feature Check wizard should now have better support for high DPI displays and show vertical scrollbar where needed Added option to easily clone monitored check (this allows you to quickly create similar monitors) “Live status” - dismiss all alerts is displayed when there is more than one service alert.

AppBeat website monitoring allowed you to easily create public status page for a long time. This page is hosted on our domain by using URL in following format: https://appbeat.io/status/YOUR_STATUS_PAGE_ID However some users wanted more: hosting public status page on their own domain use their own CSS styling We are happy to announce that newest AppBeat allows you all that! Method 1: creating public status page on your domain by using simple static HTML template and JavaScript If you navigate to “AppBeat / Public status / Dashboard” you will be able to enable your status page from there and publish on your web server static HTML file, similar to this:

Today we published new web application with one of the most requested feature for our advanced users - multi-user login! This functionality is very suitable for larger companies and DevOps teams, where it is prefered for each member to have its own AppBeat sub account (and not sharing primary account with all your users anymore). Currently it is possible to add up to 25 power users for your subscription. These users have very similar permissions to primary account administrator with following restrictions:

Yesterday we published AppBeat 1.4.6 which now natively supports Pushover and StatusPage. With Pushover you can now easily receive outage notifications on your Android or iOS phones, and with StatusPage you can automatically publish detected outages on your public status page. With this version we also add support for message personalization for most third-party integrations: All third-party integrations can be managed in “Account / Integrations” section:

On September 8th we deployed AppBeat 1.4.3 which brings you more detailed logging for your web monitors. If error occurs we will save server response (HTTP body with header) and send you unique link where you or your support team can view it. Previously you would receive just HTTP status code. Detailed logs can now help you to diagnose root cause of problem more quickly. They also allow you to keep historic track of incidents (please see note below about how long we keep your detailed logs).

We are continuing with our rapid development and last week new version was published (1.4.2). In this version we introduced new powerful report - Logs & Performance, and published final version of downtime report. Here are some screenshots of new features. Performance statistics & hourly averaged response time chart for your periodic check: Filtering monitoring logs: As you may noticed, we now also allow you to filter logs and calculate downtime reports by “service group”.

Yesterday we published new AppBeat version with improved downtime report. We also added service timeline where you can visually track details about downtimes: List of all changes for version 1.4.1: improved “Downtime overview” report (added more filters and options, added uptime/downtime timeline, more accurate service downtime calculation - if multiple checks on same service fail at same time, we now automatically exclude overlapping intervals) update “Service groups” tab moved to “Services & Checks” removed removed “Uptime” component from “Statistics & Logs” (replaced by more powerful “Downtime overview” report)

Yesterday we rolled out new version of AppBeat which brings fully customizable website monitoring (as promised in previous post): List of all changes: more friendly wizard for creating new checks update web monitor is now fully customizable (you can post data, change protocol version, IP version, send custom headers, …) update DNS monitor can now accept IPv4 or IPv6 address of DNS server used for querying removed “Automated Web Testing” early preview is now removed from UI because we received enough initial feedback.

In new version of AppBeat (1.3.8) we added new option under “Reports / SQL Archive Analyzer”. You can now create your own SQL filters to get archived log data that you need (basic SQL knowledge required). Data can also be exported to CSV files.

Today we published new version of AppBeat with following changes: you can now disable outage notifications for built-in Admin contact by double-clicking it (Contacts / Users) paid users can now select continents for preferred test location: Asia, North America, Europe (Account / Check settings) browser tries to remember collapse state of “Individual check statuses” in “Live status” view added “Public status / Status Updates” - you can now add manual status updates for your visitors “Delay alerts” is temporary disabled and removed from user interface.

Today we published AppBeat 1.3.6 with following features: “Account / API Access” - possible to call first AppBeat REST method which returns status overview of your system. This allows you to create your own simple client. We will add more useful methods in future. security improvement: same application session can not be used from multiple IP addresses we are now displaying question dialog when new web client is available (you can also postpone version upgrade) –> this will be visible first time when next version arrives back-end upgraded to .

Today we published AppBeat 1.3.5 with following features: added context menus for services, checks and contacts for more clean user interface when you right click on check in “Service & Checks / Checks”, there is new “Failure/success notes…” option. This allows you to include additional instructions for your support staff for each check and is included in sent notifications. “Account / Personalization” - possible to customize notification subject and short message (SMS) template “Account / Integrations” - added dynamic webhook provider which supports request customization - can be used with any notification provider that supports JSON payload check name is now included by default in notification subject and short message “Account / Security” - current password must be entered before changing to new password other minor improvements Context menu support: !