Ask AI

• Service-based filtering: Allow or deny specific services from a curated catalog (e.g., Netflix, WhatsApp, YouTube). Query GET /services for the full list.
• URL/domain filtering: Allow or deny traffic by domain name (SNI-based for HTTPS — no path-level inspection).
• IP filtering: Allow or deny by CIDR range. Each Traffic Profile supports either an allowlist or a denylist (not both).

How It Works

1. Create a Traffic Profile (POST /traffic_profiles) with your speed limits and/or filtering rules.
2. Assign the Traffic Profile to a SIM group.
3. Traffic enforcement propagates automatically (typically seconds).
4. One active Traffic Profile per SIM group.
5. The same profile can be reused across multiple groups.

Pricing

A monthly recurring feature fee of $200 is applied when you create your first Traffic Profile. The line item appears as wireless-portal-access-paywall-basic on your invoice. This is a flat monthly fee per account, not per SIM. The MRC kicks in when the first Traffic Profile is created and drops off when all profiles are deleted.

Limitations

• API-only — Portal UI coming soon.
• Requires Private PGW and data.net APN (see Prerequisites).
• Traffic enforcement component is currently available in the EU DC only. PGWs in other regions will have the latency overhead when using this feature until regional infrastructure is deployed (ETA end of March).
• HTTPS filtering is SNI/domain-based only (no URL path inspection).
• Service catalog accuracy depends on IP/domain sets; some services with CDN-heavy architectures may have gaps.
• Speed limiting does not alter data rating/charging - QoS only.

Traffic Profiles provide a flexible, API-driven way to optimize connectivity performance, control costs, and enforce network policies at scale across your SIM groups.