Midwest Internet Exchange

Cloudflare’s Argo

Learn how one of our members, Cloudflare, is using a technology called Argo to speed up the Internet.


PeeringDB Tutorial

The folks over at PeeringDB have a presentation on setting up an account and adding your network.

Member Spotlight: Brad from Beck’s talks about technology

Brad from Beck’s Hybrids talks on the InterVison podcast about the role technology has played in agriculture.

Podcast | Tech-Powered Agriculture

Follow us on LinkedIN


Understanding FISMA and FedRamp

MidWest is in the LifeLine facilities.  Rich Banta gives a talk on understanding FISMA and FedRamp

RFC 8327 – Mitigating the Negative Impact of Maintenance through BGP Session Culling

Some light reading.


  This document outlines an approach to mitigate the negative impact on
   networks resulting from maintenance activities.  It includes guidance
   for both IP networks and Internet Exchange Points (IXPs).  The
   approach is to ensure BGP-4 sessions that will be affected by
   maintenance are forcefully torn down before the actual maintenance
   activities commence.

January News from MidWest-IX/FD-IX

We have many exciting things going on here at MidWest-IX.

Switch and Router Upgrades
MidWest-IX has been hard at work upgrading our Indianapolis Infrastructure to all 40 GIG interconnects.  Recently we completed a cache fill router upgrade.  This will allow extra capacity to our Netflix, Google, and other caches. At the same time, this simplifies our network design on the cache network.  Simpler means more reliable and better performance.

FD-IX brand
We will be transitioning more and more to the FD-IX brand as our new sites in Texas, Cleveland, and other locations come online.  We have expanded outside the Midwest and feel it is time to embrace the brand we introduced about a year ago. This will be the same people, same network, just a different name.

Indy IXP Manager upgrade
Mike has been busy upgrading our IXP manager installation for Indianapolis. This will allow many new features as well as sFlow for traffic reporting to the software.  This is a very complex upgrade, so it is taking some time.  We will have an announcement for it soon.

Transport Ring
Many of you may have already seen this, but we have been working on a 10 GIG transport ring to connect many of our markets together.  If you are looking for transport between any of the cities, please reach out to us.

Ft. Wayne
St. Louis

PeeringDB Entries
Just a reminder to keep your peering DB entries up to date.  The future IXP manager upgrade will be more tightly integrated with PeeringDB. We have been running the new version on our St. Louis fabric for a while, and the PeeringDB integration relies on your information is up-to-date.  More and more companies are integrating their peering automation with PeeringDB.  We recommend a yearly review of your data or anytime you receive new IP space, co-lo at a new facility, or staff changes.

City Specific news
Look for some exciting news regarding St. Louis, Cleveland and a few others coming soon.

Updated St. Louis peers

Check out our updated peer list for our St. Louis Fabric.

Why you need an IX, even if you have your own cache boxes

We’ve had networks on our IXes that have had a gigabit/s or more of traffic going to our cache boxes when they had their own on-net cache boxes that were working as designed.

Many Content Delivery Networks (CDNs) have programs where you can get a node of theirs in your network to maximize performance, minimize costs, etc. Netflix has their Open Connect program. Google has their Google Global Cache nodes. Akamai has their Akamai Accelerated Network Partner program. Cloudflare, Facebook and others have programs as well, but I can’t readily find links to them.

If you have one of those nodes, why do you need to connect to them over an Internet exchange? Simply put, not all content a given CDN has is stored on every node. They all have algorithms they use to determine what content users of that box are likely to access. Those boxes are then loaded with that content. If something your customers want to watch isn’t on your local box, the CDN must direct you somewhere else to get it. It could be a different show, it could be a show you have, but at a different bit rate. Either way, it doesn’t exist on your cache box. If you aren’t peered with other boxes on an IX, guess where that goes. Yup, it goes out your transit. You’re now paying more for your customer to have a worse experience.

Maybe you’re concerned about traffic preferring the boxes you’re peered with over your own. While they all have a secret sauce that they won’t reveal to the public, they have documentation available on how to influence your use of them. Netflix explains here about half-way down the page how they do it. Google has a page that is all about how to configure your BGP environment. They all support some methods such as BGP communities, Local Pref, MED, AS-Path, etc. to influence how that traffic gets to you. Needing some help on how to set those and what they mean? We did a post last month that should provide some assistance on that.

Most important of all, don’t let misconceptions, misunderstandings, doubt, etc. get in the way of maximizing your use of what’s available to you. Reach out to support and we can have a conversation with whatever CDNs you like to make sure you’re comfortable with how everything is being used.

MidWest-IX / FD-IX welcomes RoutViews to Indy

The RouteViews project now is now on our Indy IX. Their data is used by many projects, so contribute by peering with them! Check out http://ow.ly/FQ8v30n3ao3. Archival data will be at http://ow.ly/1gDO30n3ap9. Access the collector via telnet://rviews@route-views.mwix.routeviews.org.

%d bloggers like this: