Reviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
120 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Cloud Connect
What do you like best about the product?
Easy to configure, fast delivery, quicklook billing regions, network relationship
What do you dislike about the product?
ther is not much to not like about Megaport
What problems is the product solving and how is that benefiting you?
Helping our customer connect to other regions and cloud providers
100% Uptime and great services
What do you like best about the product?
We've been using Megaport for several years and have never experienced any service disruptions. Their platform is reliable, easy to set up, and the flexibility of their service contracts adds real convenience.
Our account manager, Luke Dale, is always quick to respond to any questions and proactively looks for ways to help us save money and get more value from the service.
We're extremely satisfied and couldn’t be happier with the experience!
Our account manager, Luke Dale, is always quick to respond to any questions and proactively looks for ways to help us save money and get more value from the service.
We're extremely satisfied and couldn’t be happier with the experience!
What do you dislike about the product?
nothing .
What problems is the product solving and how is that benefiting you?
interfacing with various cloud environments and providing highly available link redundancy between our datacentres.
Great support and products diversity
What do you like best about the product?
Support from local staff and marketplace
What do you dislike about the product?
Portal configurations can take longer than expected, like 2 to 3 minutes to change a configuration
What problems is the product solving and how is that benefiting you?
Facility to integrate different cloud providers and cost effective solutions
The most boring service you can buy
What do you like best about the product?
Boring? Who wants the excitement of your global network melting down anyway, just like your home internet the more boring your services are the better job the provider is doing
Datacenter neutral, blue/red zones, elastic billing, L2/L3 design options, terraform module and customer centric team that helps you stay unblocked and it all "just works"
Datacenter neutral, blue/red zones, elastic billing, L2/L3 design options, terraform module and customer centric team that helps you stay unblocked and it all "just works"
What do you dislike about the product?
A little extra reach in those developing markets and further out places might round out the offering nicely.
What problems is the product solving and how is that benefiting you?
Time to market establishing global connectivity to the internet and hyperscalers to serve our app to our users!
Megaport makes cloud on ramp very easy to configure.
What do you like best about the product?
The integration with various vendors. API, for example.
What do you dislike about the product?
It would be nice to have more control over the workflow using vManage to configure the MVE.
What problems is the product solving and how is that benefiting you?
All cloud connectivity in one provider.
A Simple, yet Powerful Tool for Connecting Your Organization
What do you like best about the product?
Megapoprt makes it easy to build connections between an organization's resources and to connect to external resources.
What do you dislike about the product?
There are two areas that Megaport could improve. One such area is contracts. For a company that promotes automation, their contracts tie to specific network resource ID's that are generated at resource creation. Some activities, require regeneration of a resource, and that would trigger an early-termination fee, even though the customer is still trying to spend the money with Megaport. Instead, make the contracts based on a monetary value versus specific resources. This gives a lot more flexibility to organizations who want to change things quickly without potentially causing additional costs from unintended ETFs.
The other area where Megaport can improve is how clouds can direct-connect. For example, to connect Azure to IBM Cloud using a dedicated 10 Gbps link to IBM, there are a couple of options, one of which is much simpler. The more complex option is to set up a Mega Cloud Router (MCR) and plumb an Azure ExpressRoute (and Megaport VXC) to the router, followed by buying a Megaport "port" in a datacenter IBM is colocated in and extending a VXC to that.
The simpler option is to eliminate the MCR from the complex option and extend the Azure ExpressRoute/Megaport VXC to the Megaport "Port" in the IBM-colocated data center. Because the BGP peering can now happen directly between Azure and IBM, this saves compute resources in the Megaport network by reducing the load on the routing infrastructure (it's all switching at that point).
To improve this further, allow Azure (or any cloud) to connect natively to the other clouds without needing to buy a "port". The purchasing process and required minimum contract length for a "port" (specific to this kind of use-case) detracts from agility and the ability to dynamically test/update configurations. Let the clouds peer with each other. While this does cause a loss of MCR revenue, it would allow an organization to afford additional simultaneous connections. Alternatively, find a way to make this model more "valuable" with additional features (such as an included second connection) and then make this a more "premiunm" connection type (with a _reasonable_ increase in cost). However, don't make this more expensive than implementing an MCR in the middle. Both architectures have value for different scenarios.
The other area where Megaport can improve is how clouds can direct-connect. For example, to connect Azure to IBM Cloud using a dedicated 10 Gbps link to IBM, there are a couple of options, one of which is much simpler. The more complex option is to set up a Mega Cloud Router (MCR) and plumb an Azure ExpressRoute (and Megaport VXC) to the router, followed by buying a Megaport "port" in a datacenter IBM is colocated in and extending a VXC to that.
The simpler option is to eliminate the MCR from the complex option and extend the Azure ExpressRoute/Megaport VXC to the Megaport "Port" in the IBM-colocated data center. Because the BGP peering can now happen directly between Azure and IBM, this saves compute resources in the Megaport network by reducing the load on the routing infrastructure (it's all switching at that point).
To improve this further, allow Azure (or any cloud) to connect natively to the other clouds without needing to buy a "port". The purchasing process and required minimum contract length for a "port" (specific to this kind of use-case) detracts from agility and the ability to dynamically test/update configurations. Let the clouds peer with each other. While this does cause a loss of MCR revenue, it would allow an organization to afford additional simultaneous connections. Alternatively, find a way to make this model more "valuable" with additional features (such as an included second connection) and then make this a more "premiunm" connection type (with a _reasonable_ increase in cost). However, don't make this more expensive than implementing an MCR in the middle. Both architectures have value for different scenarios.
What problems is the product solving and how is that benefiting you?
Megaport initially was our primary connectivitiy for internal WAN. After moving exclusively to the "cloud", we leverage Megaport for strategic connections between cloud service providers.
excellent
What do you like best about the product?
I like about megaport portal is easy and faster
What do you dislike about the product?
I don't dislike e about Megaport Portal
What problems is the product solving and how is that benefiting you?
connectivity and global presence
Megaport Review - Great product - easy to work with
What do you like best about the product?
I can't believe how easy it is to use. Plus, whenever I have a question, my rep responds within minutes and jumps on a zoom call. Generally there are 3 Megaport folks on there, my rep and 2 engineers. They lead me through the procedure to order and set up new connections and virtual cross connections.
What do you dislike about the product?
So far, nothing. Even their pricing is very reasonable.
What problems is the product solving and how is that benefiting you?
They allow me to connect my datacenter with AWS. Before, I was setting up a VPN that worked for the most part, but occasionally it would fail. I have yet to have a failure with Megaport. It's nice to have something so reliable.
The service, dashboard and support are reliable, efficient and responsive
What do you like best about the product?
The dashboard is easy to navigate and if there are any issues, support team is very responsive.
What do you dislike about the product?
There is nothing that I dislike, but I'm hoping there is a way to remove inactive users in the dashboard, in which I was told there is no option for now.
What problems is the product solving and how is that benefiting you?
Fast provisioning of circuit
No fuss. Just highly customisable services and great people to look after us. What more do you want?
What do you like best about the product?
The fact we can get what we need when we need it. You can scale up, down and add or remove services as business demands require.
What do you dislike about the product?
Megaport are available in lots of locations but there are some we would like to use that they are not present in.
What problems is the product solving and how is that benefiting you?
Megaport is allowing our connectivity to be dynamic in ways that the old telcos did not. They allow us to connect our various locations in a dynamic way that wasn't ever previously possible.
showing 31 - 40