Correct, Waves are very transparent to errors and the carrier selling them cannot oversubscribe them, as well as the path is known and not easily changed. Most IXes are quite transparent, and require extension uplink upgrades at 66% as well as path diversity. You get a lot of stability/predictability since most of those things you do not get if you are just buying transit.
From: Ben Wiechman via mice-discuss <mice-discuss@lists.micemn.net>
Sent: Friday, April 25, 2025 4:51 PM
To: Jeremy Lumby <jlumby@mnvoip.com>
Cc: mice-discuss@lists.micemn.net
Subject: Re: Non-MICE/perhaps dumb question
So your solution is to provide transport to a location closer to the AWS region, and then the customer establishes a private connection to AWS from there?
Megaport may provide a similar transport concept. They have transport to many different DC in the US, and also had a cloud router product designed to allow remote routing for public cloud traffic w/o installing hardware the remote DC. I haven't looked at their solution in a long time to give a better judgement call regarding its viability for this use case, or whether it would only be useful on a customer by customer basis where each customer would need to have their own instance of the cloud switching in relevant data centers. This may also only be useful if direct connectivity would provide a benefit or if the customer has a lot of E/W traffic that could route remotely between public cloud applications.
Ben Wiechman
Director of Network Strategy and Engineering
320.247.3224 | ben.wiechman@arvig.com
Arvig | 224 East Main Street | Melrose, MN 56352 | arvig.com
On Fri, Apr 25, 2025 at 4:23 PM Jeremy Lumby <jlumby@mnvoip.com> wrote:
I do have customers that utilize my extension switches to other IXes so that they can connect to Amazon directly in other regions. Unfortunately I have a west coast option, and you are looking for an east coast option.
From: Frank Bulk <fbulk@mypremieronline.com>
Sent: Friday, April 25, 2025 3:53 PM
To: mice-discuss@lists.micemn.net
Subject: Non-MICE/perhaps dumb question
I’ve been reviewing some of AWS’s connectivity products, but it seems like none of them are designed to improve the AWS experience for all of an ISP’s customers across AWS’s various regions.
The background here is that we have a business customer using a key application hosted in AWS’s East Coast region. The applications’ document upload performance has been less than ideal, and their external consultant is blaming their ISP — us. As you know, once traffic leaves our network and hits upstream providers, our influence on the experience is very limited. My initial thought was to explore whether we could bring AWS closer to all of our customers through some kind of direct peering or other arrangement with AWS.
However, from what I’m seeing, AWS’s connectivity options are mostly targeted at connecting a single enterprise to AWS, not enhancing general public access to AWS services.
Is that just the reality of it, or is there a broader product (other than direct peering with Amazon) that would improve AWS performance for all our customers?
Frank
Frank Bulk
Chief Technology Officer / Chief Operating Officer
339 1st Ave NE | Sioux Center, IA 51250 | Find us on Facebook
phone: 712.722.3451 web: mypremieronline.com
direct: (712) 722-7152 cell: (712) 441-6049
_______________________________________________
mice-discuss mailing list -- mice-discuss@lists.micemn.net
To unsubscribe send an email to mice-discuss-leave@lists.micemn.net
