Radnex AI gives ISPs a searchable view of IPFIX flow records, traffic analytics, NAT context, BNG exports, storage, and reporting. Operators can review source and destination traffic, ports, protocols, flow timing, and application visibility where the network exports those fields.
Request a Demo →Built for billing, RADIUS, reporting, and ISP operations.
Capabilities
Benefits and workflow comparison
Flow fieldReporting value
Source and destinationReview traffic direction, IP context, and time-window behavior.
Ports and protocolInvestigate service-level patterns and connection context.
NAT, BNG, and application fieldsAnalyze richer flow data where exporters provide it.
IPFIX monitoring software for ISP
Collect and analyse ISP flow records
Source, destination, port, and protocol visibility
Source and destination traffic reporting is a core flow use case. Radnex AI lets teams search source IP, destination IP, source port, destination port, protocol, and time windows where those fields are available.
This gives operators a structured way to review network flow analytics without manually parsing raw exports.
NAT and CGNAT flow information
CGNAT flow records can help operators understand translated traffic and NAT context. Radnex AI can organize NAT information alongside other flow fields when the network source exports that data.
For subscriber-focused usage records and NAT correlation, the IPDR software for ISPs page provides a related view.
BNG integration and application visibility
BNG IPFIX integration and IPFIX application visibility depend on equipment capabilities and export templates. Radnex AI can organize and search those records when the deployment provides the right fields.
Operators should validate exporter templates and field availability before relying on a specific analytics view.
High-volume IPFIX storage
High-volume IPFIX storage requires retention, indexing, and query planning. Radnex AI is built for ISP traffic analytics workflows that need searchable records rather than ad hoc file review.
Storage design should be based on actual flow rate, retention policy, and reporting needs.
Search, analytics, and reporting
IPFIX search and reporting helps teams answer operational questions about traffic paths, protocols, NAT context, and flow times. Some operators evaluate IPFIX as an ISP NetFlow alternative depending on their equipment and reporting goals.
Radnex AI keeps the wording practical: flow analytics can support operations, but available visibility depends on exported data.
ISP flow monitoring gives network teams a traffic-level view that event logs alone cannot provide. Radnex AI supports IPFIX analytics for ISP environments where routers, BNGs, or collectors export suitable flow records.
These records can help with troubleshooting, capacity planning, traffic review, and authorised investigations.
Use cases
Where this page helps operators decide.
Network teams doing capacity and traffic analysis.
Answers for IPFIX monitoring software for ISP searches.
What is IPFIX monitoring?+
IPFIX monitoring collects and analyzes network flow records such as source, destination, ports, protocol, timing, NAT context, and application fields where available.
What is the difference between IPDR and IPFIX?+
IPDR is usually subscriber usage-record focused, while IPFIX is flow-record focused for traffic analytics. ISPs may use both together.
Can Radnex AI work with BNG IPFIX records?+
Yes, when the BNG exports suitable fields and the deployment is configured to collect them, Radnex AI can help teams search and analyze those IPFIX records.
Is IPFIX a NetFlow alternative?+
IPFIX is often used for standardized flow reporting and may be considered by operators evaluating NetFlow-style analytics.
Next step
Talk through your ISP requirements.
Share your subscriber count, RADIUS model, NAS devices, billing rules, reporting needs, and migration concerns with the Radnex AI team.