Port forwarding has boosted daily development workflows and improves production testing speed
What is our primary use case?
I generally use Megaport for port forwarding, so whenever I have to make a project in my own local environment and test that it would work in production, then I use Megaport for forwarding the port of my local. And then I integrate that with my company's product and see if it's hitting Megaport requests.
Whenever I open Megaport in the terminal, I start with the HTTP port number, which helps me connect that with my local Visual Studio code editor, so whatever goes through that port will be transported to Megaport terminal. Then I connect the Megaport URL address with my company's product to test it, so whenever I run the code, an ideal request should hit Megaport server.
Everyone uses Megaport in my company, but I also use it solo. I have used Megaport.
What is most valuable?
Megaport was given to me by my mentors as a tool to use for our use case, so I didn't have any decision play into this.
I think port forwarding is the most highly used feature of Megaport, and since I've used that, all my fellow seniors and teammates have also used that feature only. I think the free tier we are using is free, and it's very easily integratable with no setup guide needed for using it.
There might be other features that came up during implementation, but we didn't have any use case for those; the only concern for us was the port forwarding, and that's why we were using Megaport.
It is actually pretty important for us; our day starts with Megaport. I think it has contributed significantly because without it, if we had used some other local code editor and then tested manually every time, it would have taken a lot more time. I think it has improved our efficiency almost by fifty percent, and obviously, our productivity has increased so much.
What needs improvement?
My suggestion would be for Megaport to make the terminal more user-friendly; I use Windows, so it's not a problem, but I'm not sure how it would work in Linux or Ubuntu-based systems. Also, it works more efficiently on a Mac system versus a Windows one, so I think they should improve the Windows experience. Other than that, I don't have any suggestions for now; it's a good product.
What do I think about the stability of the solution?
When I first implemented Megaport, the first issue I faced was that I had a problem with the terminal not opening, which was an issue on my PC since I had not put the correct address. After that, I haven't faced any Megaport issues, and it's pretty stable.
What do I think about the scalability of the solution?
I think everyone in our company working in the tech domain, especially the full stack developers, uses Megaport in the same way for port transforming, and I don't think anyone is a super user; everyone is using it in a casual way.
How was the initial setup?
There was no training needed for Megaport; it was very easy to use, actually. We just had to download it and use it as we use our local Studio Code editor.
What other advice do I have?
I think everyone in our company working in the tech domain, especially the full stack developers, uses Megaport in the same way for port transforming, and I don't think anyone is a super user; everyone is using it in a casual way. I would rate this product nine out of ten.
ADr
What do you like best about the product?
New to Megaport so need time to use the system.
What do you dislike about the product?
Unsure at the moment as this is first time logging into system
What problems is the product solving and how is that benefiting you?
What problems is Megaport solving and how is that benefiting you
Megaport has improved data center interconnect and simplifies virtual cross connects for my work
What is our primary use case?
My main use case for Megaport is data center interconnect.
What is most valuable?
The best features of Megaport for my work mainly involve the scalable bandwidth, as we have multiple data centers across India, which means my internet bandwidth and internal communication bandwidth will be higher.
When I use Megaport for my data centers, what I personally find most helpful is that it reduces the complexity and is used for virtual cross connect between Layer 2 and Layer 3 routing.
Megaport impacts my organization by not necessarily lowering cost, but it reduces a lot of time and increases the bandwidth, which increases the performance, especially in terms of overall company performance and network performance.
What needs improvement?
If I could improve Megaport, I would say the missing feature is difficult to identify because we have used it mostly on Megaport. However, the part that can improve is that it should be a little bit easier to use and more user-friendly. The number of features and ease of features can be improved.
For how long have I used the solution?
I have been familiar with Megaport for the last two years.
What other advice do I have?
I would definitely recommend Megaport to someone considering it.
Easy UI, Clear Pricing, and Reliable Cloud Connectivity
What do you like best about the product?
Easy to use UI, excellent range of services with clear pricing structure. Excellent uptime/performance, with good tech support and account teams. Makes it quick and easy to deploy cloud connectivity.
What do you dislike about the product?
UI can be a bit too simplistic at times, would be good to be able to access telemetry from the services
What problems is the product solving and how is that benefiting you?
Short and long term connectivity requirements can be met over existing connections, with fast roll out due to the self service portal
excellent
What do you like best about the product?
stability , scalability , security , AWS presence
What do you dislike about the product?
There are no downsides of using megaport
What problems is the product solving and how is that benefiting you?
data center migration , replication
Intuitive Portal, Fast Setup, and Great Value for Virtual Services
What do you like best about the product?
I like how easy and intuitive it is to navigate their portals and order services. Our initial setup was smooth. I was impressed by how quickly the service came up after placing the order, with most connections being active in under an hour. Pricing was also very reasonable for virtual services.
What do you dislike about the product?
The map view is a little annoying to navigate, but honestly its more just for show than functionality. So far I don't have any issues that I can say I dislike about Megaport.
What problems is the product solving and how is that benefiting you?
Megaport is allowing us to transition from high-cost dedicated circuits with cloud vendors to a pay as you go model with bandwidth that you can scale up and down, while still giving you a dedicated on-ramp via their physical cross connects.
Lead Network Engineer
What do you like best about the product?
Using the portal access for on-ramping circuits
What do you dislike about the product?
At this point there is noting I dislike about it
What problems is the product solving and how is that benefiting you?
Cutting over a circuit for our AW cloud
Flexible, Scalable Platform with Fantastic Megaport Support and Terraform Automation
What do you like best about the product?
The flexibility of the platform stands out most — Megaport offers a wide range of services that accommodate diverse architectural needs, with the ability to scale bandwidth up or down on demand. Additionally, services are fully configurable through Terraform, enabling consistent, repeatable deployments with minimal manual effort.
The support from Megaport has been fantastic. The account team meets with me regularly for ongoing guidance, a dedicated architect helps align decisions with our business strategy, and their developers have been collaborative in enabling new features on the Terraform provider when needed.
What do you dislike about the product?
One ongoing challenge is that the staging portal doesn't always reflect the same configurable services as production — for example, red/blue diversity services may be limited to a single diversity option at a given location. Since Terraform code is developed and tested in lower-tier environments like staging, the inability to fully validate configurations before a production rollout is a meaningful gap in the deployment workflow.
What problems is the product solving and how is that benefiting you?
Megaport is solving our connectivity needs as our environment expands in ways that wouldn't have been anticipated five years ago. We now operate across all three major cloud providers, and Megaport bridges the gap in connectivity between locations and data centers, delivering the bandwidth required to support that growth with swift delivery.
simple, straight forward, easy to use
What do you like best about the product?
how easy it easy, like the cost calculator
What do you dislike about the product?
this field is required.. and it doesn't accept short feedback.
What problems is the product solving and how is that benefiting you?
high bandwdith connections to cloud provider
It works
What do you like best about the product?
Easily stand up capacity between served locations / ports
What do you dislike about the product?
Just now found it a bit fiddle to get price estimates, as there isn't an apparant "rate card" that can be used to get an initial idea for simple cases, other than building in the staging portal
What problems is the product solving and how is that benefiting you?
Connecting locations together, and providing peering and customer connectivity options.
