Skip to main content
​
  • Terms on VXC — Terms on VXC is now available for both Direct and Partner customers. This feature allows customers to order VXCs at a discounted rate and lock in the price for the length of the term, in line with the terms available for Ports, MCRs, and MVEs. When creating a new VXC or updating an existing VXC, customers now have the option to select a term (or subscription). Available term options are No Minimum Term (default), 12, 24, and 36 months. Longer terms result in a lower monthly rate. Key points:
    • An early termination fee (ETF) equal to 50% of the remaining contract value applies if a VXC is canceled before the minimum term is complete.
    • While the VXC is on term, speed changes are not allowed (all other changes that won’t affect the price are allowed, including shutting down and moving the VXC).
    • Speed changes are allowed only when re-terming and only if increasing the speed.
    • When re-terming, you can select a term that is >= current term AND you can also increase speed.
    • Customers can re-term at any time and will be notified in the last month of term to renew their term.
    For more information, see VXC Pricing and Contract Terms.
  • Issue fixed — When creating an untagged VXC between two MVEs, the Summary page was showing preferred VLAN as -1 when not specified.
  • Megaport Internet — You can now order Megaport Internet connections from Ports and MCRs within a metro (rate from 20 Mbps to several Gbps). Megaport Internet connections for Ports and MCRs can only be ordered from three countries (Australia / US / UK) and cannot leave a metro (A-End and B-End must be within the same metro).
    For more information, see Megaport Internet Overview.
​
  • Large VXCs — Large VXCs are now available to order in the Megaport Portal. Many locations will now support large VXCs up to 25 Gbps. As network upgrades occur, this will increase to supporting VXCs up to 100 Gbps in the future. For metro VXCs, pricing is the same from 10 Gbps to 100 Gbps. For long haul VXCs, pricing will be more linear depending on the network route and pricing zones.
    If you create a VXC greater than the speed supported, you will see an error “Invalid Rate Limit” displayed in the Portal.
  • Improved Portal A-End / B-End Display — When ordering a VXC to and from an MCR in combination with any product, it is now highlighted more obviously to indicate which End is being changed.
  • Move VXC / IX - Improved Services Page — Tooltips have been added to advise why a VXC cannot be moved under certain conditions.
  • Megaport Internet — Updated the logo for Megaport Internet connections.
  • Issues fixed:
    • A promo code wasn’t applying if a Port went live after the next billing cycle.
    • Canceling an expiring Port was applying 30 days notice charge.
    • When viewing a Port in the design state, the Port Configuration page wasn’t being displayed if attached to a VXC with an invalid rate limit.
​
  • Cancellation Reasons — When canceling services, customers will now be asked to provide a reason for terminating the service. A new drop-down field has been added to the Terminate Services window that allows you to select from a predefined list, or select Other and enter a description in the free text field provided. Multiple help topics where service cancellation is described have been updated for this new field.
  • Reverse DNS for IX Connections — Enabled the ability to add and edit reverse DNS for IX connections.
    • Added a new field called Reverse DNS to the Megaport Portal for customers to specify a reverse DNS when editing an IX. For more information, see Editing an IX.
    • Updated the Validate, Buy, and Update IX APIs to support the specifying of reverse DNS. For more information, see PUT Update IX (API Documentation).
  • Move VXC / IX — The Megaport Portal now allows you to move a single or multiple VXCs / IXs across Ports, MCRs, and MVEs. There are rules as to when a VXC or IX can be moved, including:
    • The source and destination Port service must be the same. That is, both Ports must be the same type (Port, MCR, or MVE).
    • Source and destination Ports must be owned by the same customer account.
    • Source and destination Ports must be located within the same metro.
    • Must be a normal customer Port or supported Cloud Service Provider port. Currently supported CSP ports are: AMS-IX, AWS, AWSHC, and Oracle.
    • The VXC or IX service being moved must not have a VLAN conflict with any existing service on the destination Port.
    • The VXC or IX service being moved must have a speed less than or equal to the destination Port maximum. For more information, see Moving VXCs and Moving IXs.
  • IP Transit Renamed — The Transit VXC service that was previously ordered with an MVE to communicate with the SD-WAN overlay network has been renamed to Megaport Internet. You will now create a Megaport Internet connection when creating an MVE. All references to the following in the Megaport Portal and documentation have been changed to Megaport Internet:
    • Transit VXC
    • IP Transit VXC
    • Megaport IP Transit
  • Palo Alto MVE — Updated the Licence Data field to allow alphanumeric characters a-z, A-Z, 0-9 (min. 8 characters).
  • Return Key Confirms MFA Token — You can now press Enter on a keyboard to submit the form for enabling MFA, rather than having to use a mouse click to submit.
  • New IX Location - Charlotte NC — MegaIX is now available in Charlotte, NC and available for ordering in the Megaport Portal. Megaport’s MegaIX is your high-speed express lane to the most in-demand global networks.
  • Dashboard — Added a new interactive map view of services to the Dashboard. Partner accounts can switch between partner / managed accounts views. For more information about using the new Megaport Portal interactive globe dashboard, see Megaport Portal Dashboard.
​
  • Megaport ONE — Launched the Beta version of Megaport ONE. Megaport’s new feature-rich networking, compute, and orchestration platform will take users through the cloud. For more information about the announcement, see Megaport Announces Public Availability of Megaport ONE Beta.
  • vNIC Connectivity — Megaport now allows you to add up to five Virtual Network Interface Cards (vNICs) to a Megaport Virtual Edge (MVE). You will have to specify which vNIC to use as an A-End or B-End when creating a connection to or from the MVE. Various topics relating to planning MVE deployments, creating MVEs, and connecting a VXC to an MVE have been updated to describe vNIC requirements. For more information, see Types of vNIC Connections.
    Consult your service provider to make sure that functionality won’t be affected if you add a vNIC.
  • Issues fixed:
    • Designed Services being removed on refresh: Partners were losing designed services when designing services for their Managed Accounts.
    • Sort and filter buttons on the Services Page alignment.
​
  • France-IX Connectivity — Megaport now supports connectivity to France-IX via VXC using the Service Key and Megaport Marketplace connectivity types. You can connect to France-IX by creating a VXC from a Port, MCR, and MVE. For more information, see France-IX Connectivity.
  • MCR Looking Glass Performance Improvements — MCR Looking Glass has been updated to support asynchronous requests for IP, BGP, and neighbor routes. A new endpoint called GET MCR IP / BGP / BGP Neighbor Routes in Async Mode has also been created to support retrieving these results. For more information, see MCR Looking Glass (API Documentation).
    Synchronous mode will be deprecated in the future so we recommend using asynchronous mode.
​
​
​
  • , , , and documentation has been updated with recent content. Updates include information on configuring AWS Outposts Rack with private connectivity, a new topic describing the LOA, new topics on diversity in Google and Azure connections, information on user authentication (including creating API keys), and a guide to creating connections to 3DS Outscale. For access from any page, use the menu in the upper-right corner to select a language.
  • Change BGP Password and ASN after Ordering IX Service — Various new or updated help topics relating to the ability to change the BGP password and ASN after you have ordered an IX service:
  • Allow Internet Traffic Exchange Between MVEs — This FAQ topic has been updated to explain that internet traffic between MVEs is now allowed. These partner topics were also updated:
​
  • Introducing MVE for Palo Alto Networks VM-Series — A full set of new topics that describe the Megaport and VM-Series Next Generation Firewall (NGFW) solution, including overview, deployment, cloud, and connection details.
  • New Package Sizes for MVE — Megaport Virtual Edge (MVE) instances are now consolidated into four new tiered package sizes. Each size now has 4 GB of RAM for every vCPU allocated. In addition, new Transit VXC functionality allows you to adjust the IP Transit bandwidth at any time. The sizing specifications are listed for each partner:
​
  • Megaport Support for Managed Account Users — We now offer direct technical support for managed account users. In this optional support model, customers managed by a partner contact the Megaport Support team directly with any support requests. Enrolling in the Megaport direct support model provides a way for partners to offer a self-service experience to their customers.
​
  • Multi-Factor Authentication (MFA) — Improvements have been made to the user experience and security of customers accessing the Megaport Portal, including having MFA enforced at an account level and admin visibility of which users have MFA set up. There are various new or updated help topics relating to the MFA improvements, including:
  • Autonomous Mode for Cisco MVE — Megaport Virtual Edge (MVE) integrated with Cisco now supports provisioning of the MVE NFV service as a virtualized standalone router, providing full control of the cloud provider to users with advanced routing expertise. This provisioning mode does not require SD-WAN. For more information, see Cisco with MVE.
Last modified on September 7, 2026