Skip to article
Case study · MSP Southeast Networks

Southeast Networks deployed Fivenines on 100+ servers in 40 minutes

How a US-based MSP, ISP, and VoIP provider unified monitoring across servers, voice systems, and ISP backbone with Fivenines.

Published May 2026 · 4 min read · By the Fivenines team

40 min
to deploy on 100+ servers
300+
instances now supervised
5 min
to create the account

A US-based MSP, ISP and VoIP provider

Southeast Networks is a US-based MSP, ISP, and VoIP provider. The team runs a mixed production fleet hosting PBX systems and websites for its clients, built on KVM virtualization with its own ISP backbone equipment. Monitoring was fragmented across three native tools, one for the virtualization layer, one for the voice systems, and one for the network. None of them gave a unified picture.

Three tools, three blind spots

The native monitoring offered limited visibility into VMs, and the voice platform added its own blind spots. When VoIP incidents hit, root cause analysis was painful, the team often couldn't tell whether the problem was the VM, the host, the network, or the PBX itself. Daniel evaluated Zabbix and CheckMK but came to the same conclusion on both: powerful, but built for teams with someone running them full-time. As Daniel puts it, he's also cautious by default about installing unknown agents on production servers.

“

Zabbix and CheckMK are powerful, but they're built for teams with someone running them full-time.

D Daniel Preni Systems Engineer, Southeast Networks

Five minutes to sign up. Forty to deploy.

Daniel tested Fivenines in a lab environment first. The result was immediate: simple deployment, fast configuration, straightforward alerting. He then rolled it out across the production fleet: account created in 5 minutes, Fivenines deployed on 100+ instances in 40 minutes.

0:00

Lab test

Tested in a lab environment first

0:05

Account created

The setup was ready for production rollout

0:45

100+ servers monitored

Metrics and alerts were flowing across the fleet

The proof

The service disruption that proved it

A few weeks after the rollout, Southeast Networks hit a service disruption that affected a portion of their customer base. An edge router was dropping traffic intermittently. The voice platform monitoring still showed every system online: green dashboard, no alerts. But on Fivenines, agents across the server infrastructure powering the voice services were flapping up and down, the kind of signal pattern that only emerges when something upstream is misbehaving. The pattern pointed straight to the actual cause.

Voice platform monitoring

All systems operational

What it showed during the incident.

Edge router

No alerts triggered

Where the issue actually was.

Fivenines agents

Flapping pattern detected

Root cause

Edge router dropping traffic intermittently

“

During a recent service disruption, Fivenines was the only platform that actually pointed us to the root cause.

D Daniel Preni Systems Engineer, Southeast Networks

Zabbix and CheckMK are powerful, but they're built for teams with someone running them full-time. Fivenines was up on 100+ of our servers in 40 minutes, and during a recent service disruption it was the only platform that actually pointed us to the root cause.

Where they are now

  • Fleet-wide deployment in under an hour

    5 min to create the account, 40 min to deploy across 100+ production instances

  • 300+ instances now under unified monitoring

    300+ instances now supervised on Fivenines, including SBC infrastructure

  • Significantly lower cost than CheckMK or Zabbix cloud

    Significantly lower cost than the cloud offerings of CheckMK and Zabbix

  • Now part of customer onboarding

    Fivenines now integrated into the onboarding and sales process with new customers

Ready to monitor like Southeast Networks?

Start a 14-day free trial, using the same setup flow Daniel used to deploy across 100+ servers. Or see how Fivenines fits your MSP workflow.

Start free trial See MSP monitoring solution →

No credit card · 2-minute setup