OV - Status Page

Dear Partner,

We’re writing to inform you that we will no longer have a roaming agreement with the following networks on the VFNL profile as of 26th January 2026, today.

Serbia

Network: Yettel Serbia

MCC/MNC: 220 01

TADIG: YUGMT

We apologise for the shorter than usual notice but, the decision from the MNO was not received in the usual timeframe.

We advise moving any traffic away from the network over the coming week to ensure as little service disruption as possible when access is blocked.

If you have an urgent requirement to retain access to the network, please contact your account manager for assistance.

Many thanks for your support.

Team OV/Smartroam

A new release will be deployed with no downtime but we are introducing breaking changes to our Data Caps APIs and default SIM tagging behaviour. We are making these updates to improve consistency and align our data formats.

Please review the changes below to ensure your integrations are updated before the release.

1. Data Caps API Updates

We are updating field names and payload units across the following endpoints:

• GET /v1/data_caps/sim/{iccid}

• POST /v1/data_caps/sim/{iccid}

• PUT /v1/data_caps/sim/{iccid}

• POST /v1/provisioning/batch

Field & Unit Changes:

• byte_limit is changing to data_limit

• byte_alert_thresholds is changing to alert_thresholds

• Unit Shift: All data cap values will now be represented in megabytes (MB) instead of bytes.

2. Default SIM Tag Naming

To make identifying resources easier, the default tag applied to SIM cards will now dynamically reflect your partner name instead of using a generic string.

• Old behavior: All partners received the tag "Default"

• New behavior: Partner A receives "Partner A", Partner B receives "Partner B", etc.

Required Action Items

To avoid runtime errors or broken workflows, please update your codebases and systems to account for the following before the deployment date:

• Update API Payloads: Modify your JSON deserialization and parsing logic to use the new data_limit and alert_thresholds fields.

• Adjust Data Calculations: Convert any application logic handling these endpoints from bytes to MB.

• Update Tag Filters: If you have any automated workflows, scripts, or UI filters that look specifically for the literal string "Default", update them to look for your specific partner tag name.

If you have any questions or need support please reach out to us through your usual support channel.

Maintenance is required on the Signalling Firewall infrastructure. No service disruption is anticipated but there is an increase risk during the maintenance window.