All evals
Megaport

Eval directory

Evals for Megaport

Eval coverage for Megaport, mapped from its public product surface.

About Megaport

Megaport is a platform for provisioning compute, network, and storage infrastructure on demand across a global private network. Its building blocks include Ports, Virtual Cross Connects, Megaport Cloud Router, Megaport Virtual Edge, Megaport Internet, NAT Gateway, and DDoS Protection, used for data center to cloud, cloud to cloud, and global WAN connectivity. Services are billed per connection with published monthly starting prices and can be deployed in minutes through a self-service portal.

Industry

on-demand cloud connectivity and infrastructure platform (Network-as-a-Service)

Use the eval library for Megaport

We'll build out the full library — runnable test cases with inputs, expected behavior, and pass/fail checks — in your Corsac workspace.

Generate your own →

Coverage map

What would you measure for Megaport?

6 scoring areas · 24 capabilities mapped · grounded in 8 cited pages

Every eval set is graded on

  • Adversarial robustness
  • Workflow quality
  • Safety gates
  • Operator quality

Pass/Fail + LLM judge 1–5 · critical severity flags · negative controls

01

Connectivity Building Blocks

Core interconnection products and their stated mechanics: physical Ports as 802.1Q VLAN trunks, Layer 2 Virtual Cross Connects, the managed Megaport Cloud Router, and Megaport Virtual Edge for NFV workloads. Covers what each product is, how they interoperate, and the limits published for them.

configured as an 802.1Q VLAN trunk to support up to 100 Virtual Cross Connects www.megaport.com

Mapped capabilities

4 capabilities

  • Port and VXC fundamentals

    Port as a high-speed Ethernet NNI configured as an 802.1Q VLAN trunk; VXC as a Layer 2 circuit presented as a unique VLAN; the published ceiling of up to 100 VXCs per Port.

  • Megaport Cloud Router (MCR)

    Managed virtual router service for direct networking between endpoints on the Megaport network, including when MCR is the right building block versus a point-to-point VXC.

  • Megaport Virtual Edge (MVE)

    On-demand Network Function Virtualization: deploying SD-WAN gateways, virtual routers, and virtual firewalls in minutes rather than shipping hardware.

  • Product interoperability

    How the building blocks combine — the stated claim that all products are interoperable and can be assembled into core or custom solutions.

Illustrative example

Input
How many separate connections can we run over a single Megaport Port, and how are they separated?
Expected behavior
States that a Port is configured as an 802.1Q VLAN trunk supporting up to 100 Virtual Cross Connects, each presented as a unique VLAN. Does not raise, lower, or hedge the 100 figure or describe unlisted separation mechanisms.

02

Cloud and WAN Topology Solutions

The named connectivity outcomes Megaport packages on top of its building blocks. Tests whether the right topology is recommended for a stated workload — replication, migration, multicloud egress, or regional expansion — and whether the described traffic path matches the documented solution.

Mapped capabilities

4 capabilities

  • Data center to cloud

    Private connectivity from a data center to cloud regions for hybrid cloud, migrations, and steady production traffic, versus public internet paths.

  • Cloud to cloud and Virtual Connectivity Hub

    Direct cloud-to-cloud paths and hub-and-spoke centralization of routing and control for many-to-many environments.

  • Global WAN and on-ramp as a service

    Connecting physical and virtual PoPs, localizing traffic flows, and reaching cloud from existing data center and edge locations.

  • Data center to data center

    Private Layer 2 links between facilities for replication, disaster recovery, and shared platforms.

03

Compute, Storage, and AI Infrastructure

The non-network side of the platform: on-demand CPU and GPU compute, storage, and AI-oriented bare-metal GPU deployments, all described as connected through the Megaport backbone. Tests whether these are described within their stated scope and correctly tied back to the private connectivity story.

Build on private infrastructure and deploy connections on an ISO/IEC 27001-certified network. www.megaport.com

Mapped capabilities

4 capabilities

  • Compute as a service

    High-performance CPU and GPU infrastructure provisioned in minutes and connected through the global network backbone.

  • Bare-metal GPUs for AI

    GPU deployment for AI training and inference with private connectivity to an ecosystem of GPU providers and AI models.

  • Storage

    Storing, accessing, and moving data under the stated positioning of no hidden fees and no performance trade-offs.

  • Advanced Services

    Managed provisioning, management, and maintenance handled by Megaport's team rather than the customer.

04

Security and Internet Edge

Platform-native security and internet-facing services, including their eligibility boundaries. Several of these are add-ons rather than standalone products, so scoping accuracy matters more than feature breadth.

Choose how you want to access the Megaport platform and deploy globally in 60 seconds. www.megaport.com

Mapped capabilities

4 capabilities

  • DDoS Protection

    Add-on to Megaport Internet covering eligible traffic against Layer 3 and Layer 4 attacks; not positioned as protection for all traffic or all layers.

  • Megaport Internet

    Dedicated internet access delivered over the Megaport fabric with the stated 60-second provisioning claim.

  • Firewall as a Service hosting

    Hosting a customer's chosen firewall vendor across the stated 100+ locations, distinguishing hosting from a Megaport-supplied firewall.

  • NAT Gateway and platform assurances

    NAT Gateway cost positioning and the ISO/IEC 27001-certified network claim, kept to what is published.

05

Pricing and Commercial Guidance

How pricing questions are answered given that some prices are published as monthly starting points, some are portal-gated, and some require contacting the team. The central risk is stating a firm quote where only a floor or a login-gated path exists.

Mapped capabilities

4 capabilities

  • Published starting prices

    Monthly from-prices for Data Center to Cloud, Cloud to Cloud, Virtual Connectivity Hub, and MegaIX, always framed as starting points.

  • Portal-gated pricing

    VXC and Data Center Interconnect pricing that requires an account and portal login rather than a public figure.

  • Contact-sales paths

    Global WAN and other builds routed to the Megaport team instead of a self-serve number.

  • Per-connection billing model

    Billing tied to connections and chosen bandwidth — paying only for the bandwidth needed.

Illustrative example

Input
We want to connect our AWS and Azure environments through Megaport. What will that cost us per month?
Expected behavior
Gives the published Cloud to Cloud figure of US$780 per month explicitly as a starting price, notes that exact point-to-point VXC pricing requires logging into the Megaport Portal, and does not present a firm total or invent bandwidth-tiered rates.

06

Self-Service Provisioning Workflow

The portal-driven path from account creation to a live service, plus the ecosystem and coverage lookups a buyer runs before committing. Tests the accuracy of provisioning-speed claims, coverage figures, and the terms a user accepts along the way.

Mapped capabilities

4 capabilities

  • Account creation and terms

    Signing up through the portal and the accompanying agreement to the Terms of Service and Privacy Policy.

  • Deploy and scale on demand

    The stated ability to configure and connect services in 60 seconds and adjust capacity on demand.

  • Ecosystem and location lookup

    Finding among the stated 410+ service providers and enabled locations before designing a connection.

  • Coverage and scale claims

    Countries, enabled locations, and network capacity figures reported only as published.

Coverage is mapped from Megaport's public pages (8 crawled). Examples are illustrative, not real test cases. The runnable eval library — graded inputs, expected behavior, and pass/fail checks — is built when you request it above.

Frequently asked questions

What do the Corsac evals for Megaport test?+

The coverage map is generated from Megaport's own public product surface (on-demand cloud connectivity and infrastructure platform (Network-as-a-Service)): 6 scoring areas — Connectivity Building Blocks, Cloud and WAN Topology Solutions, and Compute, Storage, and AI Infrastructure, and more — spanning 24 mapped capabilities, each graded on adversarial robustness, workflow quality, safety gates, and operator quality once the library is built.

How are the Megaport evals scored?+

Every case generated for Megaport — across Connectivity Building Blocks and Cloud and WAN Topology Solutions and the other mapped areas — is graded with pass/fail checks plus an LLM judge scoring 1–5 against its expected behavior, with critical-severity flags and negative controls. Only judge-passed evals are published.

How many test cases does the Megaport library include?+

The full Megaport library is built on request. The coverage map spans 6 areas and 24 capabilities (for example, Port and VXC fundamentals and Megaport Cloud Router (MCR) under Connectivity Building Blocks); each becomes graded test cases — inputs, expected behavior, pass/fail checks — in your Corsac workspace.

How do I run these evals against Megaport or my own agent?+

Request the library with your work email above. We'll build out all 6 mapped Megaport areas and set them up in a Corsac workspace, where you can run every test case against Megaport or your own agent with your own data.