ProBee assurance dashboards

Pillar 01 Service Assurance

Your OSS knows that a KPI moved. It rarely knows which protocol dialogue moved it. Mobees closes that gap with two complementary sources of truth — passive protocol probes and active end-to-end tests — and publishes both into the assurance platform you already run.

  • Passive: ProBee probes decode live signalling and score Protocol Experience (PX) continuously, per service, per peer, per node.
  • Predictive: anomaly models flag the drift that precedes an incident, not the outage after it.
  • Active: BeeTest proves the subscriber-visible service from real and emulated terminals, on a schedule.
  • Open: Prometheus, Kafka, SNMP, syslog and REST out of the box. No proprietary collector, no forced console.
Talk to an assurance engineer
How it plugs into your stack

Protocol Experience (PX)

Predictive anomaly detection

Passive + active

Prometheus / Kafka / SNMP

Grafana-native

Kubernetes

SS7 · Diameter · SIP · SMPP · HTTP/2

The gap between “the network is up” and “the service works”

Element counters tell you a node is healthy. Service quality management tells you a KPI has crossed a threshold. Neither tells you that MAP dialogues to one roaming partner started retransmitting eleven minutes ago, which subscribers are affected, and which SCCP route is responsible.

That answer only exists in the packets. ProBee reads them at line rate, keeps the protocol state, and turns it into metrics — so your existing assurance and automation layer finally has a signal worth acting on automatically.

Two sources of truth, one timeline

Passive probing tells you what the network is really doing. Active testing tells you what the subscriber really experiences. Correlated, they tell you where the fault is.

ProBee — passive protocol probes

  • Line-rate decode of SS7/SIGTRAN, MAP, CAMEL, INAP, Diameter, SIP, SMPP, MM1–MM9 and 5G HTTP/2 service-based interfaces
  • Continuous PX scoring per service, peer, node and route
  • Heuristic and ML anomaly detection ahead of failure
  • Millions of packets per second, scaled horizontally
  • Inline tap, port mirror or virtual probe in the cluster

BeeTest — active service testing

  • Scheduled end-to-end journeys from real and emulated terminals
  • SMS, MMS, RCS, VoLTE, VoWiFi, data attach and entitlement flows
  • Regression packs for every release and every roaming partner
  • Results on the same timeline and in the same dashboards as probe data
  • Synthetic SLA evidence you can put in front of a customer
ProBee in detail
BeeTest in detail

Assurance is a service, not a shipment

A probe estate has to be baselined, tuned, upgraded and watched. Most operators would rather buy that outcome than staff it. Mobees sells the probes, the people, or both.

Probe as a Service

Hardware or virtual probes, deployment, lifecycle and licences on a monthly subscription. No capital project.

Managed Assurance

We run the assurance layer: model tuning, alert triage, weekly PX reporting and an on-call protocol expert.

PX Baselining

A fixed-scope engagement that establishes what “normal” looks like on your network, per service and per partner.

Protocol L3 Support

The escalation tier your NOC calls when a trace stops making sense — on your probes or someone else’s.

All assurance services

We generate KPIs. You keep the cockpit.

Mobees does not sell an assurance cockpit and has no ambition to. Our value is upstream: a data source that sees what element counters cannot, published through interfaces your platform already speaks.

  • Metrics: Prometheus scrape and remote-write, OpenMetrics, InfluxDB line protocol
  • Streams: Kafka topics with per-dialogue records, schema-registered
  • Faults: SNMP traps and syslog, mapped to your alarm dictionary
  • Service quality: REST feeds shaped for TM Forum-aligned performance, alarm and service-quality models
  • Closed loop: webhook and Kafka triggers your orchestrator can act on, with the protocol evidence attached
Integration interfaces
ProBee northbound interfaces

What our customers say

References are anonymised at the customer’s request. Named references and written reference letters are available under NDA.

Core network operations, Tier-1 MNO (DT group)

„We were finding signalling degradations from the complaint queue. ProBee moved that left by roughly forty minutes — we now see the retransmission pattern build before the first customer calls. It is the same Grafana our NOC already lives in, so nobody had to learn a new console.”

Head of Platforms, MVNE serving 300k+ subscribers

„Our BSS was complete and our network layer was not. Mobees dropped in the messaging core and the TS.43 entitlement server behind our existing provisioning, per tenant. We stopped referring those deals out.”

Delivery director, systems integrator, CEE

„They are the people we call when a transformation programme hits SS7 or CAMEL and the schedule is already tight. Small team, no layers, an answer the same week.”

Start with one link and one week.

A single tap point, a fixed-price pilot and a defined success criterion. If the PX signal is not useful, you stop there.

Contact us
See the case studies