OV - Notice history

All systems operational

Operational

VFNL Profile - Operational

99.779% uptime
Jun 2026 · 99.845%Jul · 99.500%Aug · 100.00%
Jun 2026
Jul 2026
Aug 2026

MANX Profile - Operational

99.830% uptime
Jun 2026 · 100.00%Jul · 99.500%Aug · 100.00%
Jun 2026
Jul 2026
Aug 2026
Operational
100.00% uptime

Dallas Packet Core - Operational

100.00% uptime
Jun 2026 · 100.00%Jul · 100.00%Aug · 100.00%
Jun 2026
Jul 2026
Aug 2026

OV Isle of Man Packet Core - Operational

100.00% uptime
Jun 2026 · 100.00%Jul · 100.00%Aug · 100.00%
Jun 2026
Jul 2026
Aug 2026

MT Isle of Man Packet Core - Operational

100.00% uptime
Jun 2026 · 100.00%Jul · 100.00%Aug · 100.00%
Jun 2026
Jul 2026
Aug 2026

Voice - Operational

100.00% uptime
Jun 2026 · 100.00%Jul · 100.00%Aug · 100.00%
Jun 2026
Jul 2026
Aug 2026

SMS - Operational

99.830% uptime
Jun 2026 · 100.00%Jul · 99.500%Aug · 100.00%
Jun 2026
Jul 2026
Aug 2026
Operational
100.00% uptime

MAP Platform Availability - Operational

100.00% uptime
Jun 2026 · 100.00%Jul · 100.00%Aug · 100.00%
Jun 2026
Jul 2026
Aug 2026
100.00% uptime

PIP Platform Availability - Operational

100.00% uptime
Jun 2026 · 100.00%Jul · 100.00%Aug · 100.00%
Jun 2026
Jul 2026
Aug 2026

eSIM - Operational

100.00% uptime
Jun 2026 · 100.00%Jul · 100.00%Aug · 100.00%
Jun 2026
Jul 2026
Aug 2026

OTA - Operational

100.00% uptime
Jun 2026 · 100.00%Jul · 100.00%Aug · 100.00%
Jun 2026
Jul 2026
Aug 2026

vVLR - Operational

100.00% uptime
Jun 2026 · 100.00%Jul · 100.00%Aug · 100.00%
Jun 2026
Jul 2026
Aug 2026

OTT - Operational

100.00% uptime
Jun 2026 · 100.00%Jul · 100.00%Aug · 100.00%
Jun 2026
Jul 2026
Aug 2026

Notice history

View current status

Aug 2026

Jul 2026

Jun 2026

JUN29
OVOne New Release: Data Caps API Breaking Changes (Schema, Units) & Tag Update
CompletedMaintenance2520 hours 13 minutes
  • Completed12 10 2026 at 10:13 AMUTC

    Maintenance has completed successfully.

  • In progress29 06 2026 at 10:00 AMUTC
    Maintenance is now in progress
  • Planned19 06 2026 at 9:05 AMUTC

    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.

Previous

Jun 2026 to Aug 2026

Next