Use case · BGP assurance

Know why the path changed — and when.

When traffic silently shifts to a backup provider, the cause is almost always a BGP attribute change. Phantom captures both directions of every session with the full attribute set and history.

How Phantom does it

The full decision context, tracked over time.

Example

A customer's traffic suddenly egresses via the backup ISP. Phantom shows the local-pref on the primary path dropped and the AS-path lengthened after a peer reset — pinpointing the attribute change and its timestamp in minutes.

BGP · prefixesRoute-flap & stabilityAsymmetric routing

See your BGP paths and attribute history.

Book a demo