Firebind Cloud - Continuous Network Performance Testing

(Note: This page is about Firebind Cloud, Firebind’s first offering that has been in production since 2016 and focuses on continuous network performance testing. Firebind Cloud is a completely separate SaaS platform than Firebind’s new Recon security offering)

Continuously test network quality to the cloud with 10 times the visibility of open source solutions and at a fraction of the cost and complexity of other enterprise solutions.

Configure

Configure four simple parameters for an agent in just 30 seconds

Set Alarm Thresholds

Adjust thresholds to provide alarm notifications when quality issues arise

Deploy Agent

Deploy an agent to virtually any machine

Monitor

Monitor the agent dashboard or simply wait for alerts to arrive in your inbox

Simple Agent Configuration

A Firebind agent can be configured and deployed in less than 2 minutes. Just provide a name, pick one of Firebind’s regional test targets, enter several user configurable options, and select a test interval.

Set Alarm Thresholds

Configure alarm thresholds for packet loss, UDP latency and jitter, Ping round-trip-time, HTTP response time and DNS response time. Choose different email recipients for each agent.

Multiple Graphs Show Detailed Trends

Each agent has 6 graphs representing a total of 11 different measurements. At 5-minute test intervals Firebind collects over 3,100 data points per day per agent, allowing the spotting of trends that indicate network quality performance issues.

Receive Email Alarms When Thresholds Crossed

Firebind’s policy engine evaluates every data point against the user provided alarm thresholds and emails a distribution list of recipients with the specific values of those threshold violations.

A Comprehensive Set of Features

  • Rapidly configure and deploy an agent in 2 minutes or less
  • Deploy to virtually any system, including Linux, PCs, Macs, Virtual Private Servers, and even Raspberry Pis
  • Execute tests around-the-clock, every 5 minutes, 365 days a year
  • Simulate VoIP calls and measure UDP packet loss in both directions as well as UDP latency and jitter
  • Measure Ping Round-trip-time and HTTP and DNS response times to customer configured destinations
  • Set custom alarm thresholds on a per agent basis
  • Send email alerts to per-agent email recipients when alarm thresholds are violated
  • Add your own user accounts to share read-only access on a per-agent basis

Firebind Cloud Monthly Per Agent Pricing

$ 50 Monthly
  • Testing at 5 minute intervals
  • Alarming when performance thresholds crossed
  • 30 days of performance history
Free Trial

Firebind Cloud Instructional Videos

Firebind Cloud FAQ

Your 14-day trial is 100% free and your card won’t be charged if you cancel before the trial expires. We require a credit card to reduce fraud and abuse and to ensure that when the free trial is over your account can be converted to a subscription without any service interruption. If it’s not possible to provide a credit card in advance, please email us at sales@firebind.com.

After signing up for the free trial, you’ll have 14 days to use Firebind. The trial includes a license for 3 agents that can be deployed anywhere.

Since an agent performs 11 unique measurements every 5 minutes, each agent generates 3,168 data points per day, or over 133,000 measurements for the 3 agents during the 14-day trial.

Before the trial is over you’ll have the option to cancel the trial and close your account, or subscribe to any number of agents on a monthly or annual basis.

To avoid any service interruptions if you don’t cancel your trial or actively convert your trial to a paid subscription, Firebind will automatically convert you to a monthly paid plan for a single agent.

All monthly plans are paid by credit card. We accept Visa, MasterCard, American Express, and Discover. For other forms of payment, please contact support@firebind.com.
The number of licenses corresponds to the number of “enabled” agents. An agent has 3 primary states:
  • unregistered or registered
  • enabled or disabled
  • active or inactive

When an agent is first created via the Firebind web console, it is put into an unregistered state. Once the agent is deployed and starts for the first time, the agent enters a registered state and stays registered until it is deleted.

Upon registration, the agent is automatically enabled and will begin testing according to its scheduled interval (e.g. every 5 minutes.) The one exception to this is that if a user account already has the maximum number of agents enabled, the new agent will register and be left in a disabled state.

For every enabled agent license, Firebind permits 2 agents to be created. For example, if a user had a license for 5 agents, a total of 10 agents could be created, however only 5 of the 10 could be in an enabled (testing) state at any given time. If agents 1 through 5 were enabled, then the user could, for example, disable agent 3 and then enable agent 7, leaving the user with agents 1,2,4,5 and 7 in an enabled state.

All agents will “check-in” (poll) the Firebind web console every 10 seconds. If the console hasn’t received an agent poll within 30 seconds, it will declare the agent inactive. The most common reasons for inactivity are [1] the remote site where the agent is deployed is experiencing connectivity issues or [2] the host machine where the agent is deployed was no longer online (due to manual shutdown, inactivity timeout, sleep mode, etc.)

When an agent is created, Firebind automatically assigns an Agent ID. This Agent ID uniquely identifies each agent and it is the single configuration parameter that needs to be supplied during the agent installation process.

Agents are not required to remain assigned to a single machine or location. For example, a customer with a single agent license could deploy that agent to one site in the morning, another site in the afternoon, and yet a third site in the evening. The only requirement would be that the same agent ID couldn’t be actively used from more than a single site at any given time.

Click here for more information about the individual Firebind Cloud performance tests.