Madison Internet eXchange Peering Point - MadIX

UW-Madison DoIT Network Services established the MADison Internet eXchange (MadIX) in early 2000 as a means for local network providers to peer in Madison, WI.

Getting Connected

A provider can peer at MadIX at the following exchange points:
  1. Network222 Suite 12
    222 W. Washington Street
    Madison, WI

    There is no UW rack space available at this location, however, there is building managed colo and other space. Click here for info.


  2. University of Wisconin-Madison Computer Sciences building (DoIT)
    1210 W. Dayton Street
    Madison, WI 53706

    Limited rack space may be available at this location.
You can get connected to the exchange via the following institutions which have high speed circuit capability at 222 West Washington (preferred) or the UW Data Center:
  • Wisconsin Independent Network (WIN)
  • Ameritech/SBC/AT&T
  • Charter Business Networks
  • TDS Telecom
  • City of Madison fiber
  • Mad City Broadband

Requirements

In order to join one of the MadIX locations for peering, the following is required of the ISP:
  1. A registered BGP Autonomous System number.
  2. Ethernet Connectivity into one of the locations listed above.
  3. Commitment to provide and update technical contact information.

Our v4 subnet is 144.92.233.224/27
Our v6 subnet is 2607:f388:0:2200::/64

Requesting Peering

Contact Network Services to become a MadIX member via Email. You will need to provide your AS Number, ISP name, Contact Phone Number and indicate which of the locations in the Overview section you want to peer at.

Email Notifications

A mailing list has been set up for supporting NOC notifications, and populated with the support information below. Only the addresses subscribed to the list may post to the list. Usage of the list is restricted to outage and related notifications. This list is not for peering coordination nor general-purpose discussion.
  • Mailing list: madix-notifications at lists.wisc.edu
  • To subscribe: join-madix-notifications at lists.wisc.edu
  • To email the list maintainer: owner-madix-notifications at lists.wisc.edu

Traffic Statistics:


Current Members

The following Table shows the current members and how to contact them to arrange peering:

Name BGP AS V4 V4 mcast V6 Peering Email Peering Phone Support Email Support Phone
UW Madison 59 144.92.233.230 YES ::1 peering-uw@lists.wisc.edu 608-263-4188 noc@doit.wisc.edu 608-263-4188
WiscNet 2381 144.92.233.232 YES ::2 peering@wiscnet.net 608-263-4188 noc@wiscnet.net 608-263-4188
Badger Internet 26284 144.92.233.226

jfunk@farin.com 608.661.4240 jfunk@farin.com 608.661.4240
US Signal 26554 144.92.233.227

peering@ussignalcom.com 888.663.1700 noc@ussignalcom.com 888.663.1700
Sonic Foundry 22986 144.92.233.228

peering@sonicfoundry.com 608.443.1600 peering@sonicfoundry.com 608.443.1600
5NinesData 16842 144.92.233.229 YES ::6 tk@5ninesdata.com 608-512-1007 support@5ninesdata.com 608-512-1000
CDW (formerly Berbee) 3599 144.92.233.231
::9
hostmaster@berbee.com 608-288-3000 help@berbee.com 608-288-3000
TDS Telecom 4181 144.92.233.233
::7 ispadmin@tdstelecom.com Kevin Roberts 608-664-4690 or Brad Fick 608-664-4667 ispadmin@tdstelecom.com 608-664-4200
Charter 20115 144.92.233.234

cbnoc@chartercom.com 866-603-3199 cbnoc@chartercom.com 866-603-3199
SupraNet 4150 144.92.233.235 YES
::5 chrisw@supranet.net (608) 836-0282 support@supranet.net (608) 836-0282
ResTechServices 46262 144.92.233.236

peering@restechservices.net 608-237-1113 info@restechservices.net 608-663-3868


144.92.233.237
::3




AirStream Communications 11796 144.92.233.238

nmc@wins.net 715.832.3750 nmc@wins.net 715.832.3750
Netwurx 26785 144.92.233.239 YES ::4 jauer@netwurx.net 262-224-8732 jauer@netwurx.net 262-224-8732
Mad City Broadband
5683 144.92.233.240
::8 Andrew Hoyos <andrew@hoyosconsulting.com>
608-320-2000 MCBB Support <support@madcitybroadband.com> 608-237-6152
Vernon Telecom
53849 144.92.233.241 YES
Reggie Nelson <rnelson@vernontel.com> 608 634 7442 noc@vernontel.com 608-634-3136 Ext: 264
Spiralight
33125 144.92.233.242
::A Andrew Hoyos <andrew@hoyosconsulting.com>
(608) 320-2000 noc@spiralightnetwork.com (920) 940-0001
Multicast Monitoring Port
  144.92.233.243      David Treptow <dtreptow@vernontel.com> 608-634-7437 noc@vernontel.com 608-634-3136 Ext: 264
Akamai
via 2381    
  Contact peering-uw@lists.wisc.edu for details      
Hurricane Electric
6939 144.92.233.244
::B peering@he.net
(510) 580-4100 noc@he.net (510) 580-4100
Hoyos Consulting
53597 144.92.233.245
::C andrew@hoyosconsulting.com
608-616-9950 info@hoyosconsulting.com 608-616-9950

Updating Your Information

To update your contact information send email to Network Services Here. <>

Evaluation of Open-IX Technical Requirements

The Open-IX Association has put together a list of technical requirements to standardize IXP offerings.
The below table outlines a comparison of MadIX with these requirements.
Open-IX Requirement MadIX
Public exchange vlanAvailable!
Private vlanAvailable! (just ask)
1G portsAvailable!
10G portsCurrently limited. Please let us know if this is an issue, as we do have plans to replace the switches soon.
ethertype 0x0800Yes, we allow legacy ethertypes.
ethertype 0x86ddNo problem.
ethertype 0x8606Yes, we allow legacy ethertypes.
ipv4 multicast filteringWe can support v4 multicast, and we do IGMP & PIM snooping.
ipv6 multicast filteringNot supported (yet). MLD snooping is not currently enabled.
customer demarcThe port on our switch at 222. The cabling is yours, but we prefer minimally to help dress the cables in the common area and into our cage. At the CS datacenter, the demarc is on your equipent (our a demarc panel you provide) and we will take it from there.
non-oversubscribed switching backplaneThe current switches at 222 and at the UW CS building are cisco cat6k/sup720 with 6704 and 6516 linecards. However, our traffic levels are monitored and we are very much well within the fabric capability of the existing switches. We do have plans to replace the switches soon.
inter-switch congestionThere is a 20G etherchannel between the two switches which is congestion free.
inter-switch path diversityThe 20G etherchannel between the two switches is provisioned as a 10G on each side of UW's metro ring.
redundant power feedsThe switch at 222 has a minimum 4 hour of battery runtime, backed by a generator circuit provided from 5nines, and a building power source from Fiore. The UW CS datacenter has multiple power feeds backed by 30min of battery, n+1 natural gas generators with 2 days of diesel reserves on-site.
Measures implemented to overcome single component failuresSee above. Let us know if you have any questions & we can try to clarify.
PI address space from an RIRUW-Madison address space is currently in use. UW does not have plans to change this, but if you want to help MadIX acquire new space, then by all means let's get in touch.
Route serverNone. You're on your own.
NOC contact informationSee above contact info table. UW-Madison runs the IXP operations.
Service-affecting maintenance announcementsSee above info on email notifications. UW-Madison's internal procedures call for a minimum of 2 business day notification on service affecting maintenance. In reality, we typically announce this much further in advance (plus we can negotiate the window).
MonitoringThe UW NOC monitors MadIX for performance degradation and service affecting events.
Procedure for performance degradation event notificationsIn most cases the NOC typically will use the email list above. If something affects only one participant, then only they may be notified.
Participants & AS numbersSee above table.
Traffic statistics.See above links. We have a total bit/sec summary as well as per-participant stats for various metrics.
Website where the Open-IX standards are addressed.You are looking at it.
Entry in a direcotryWe are on PeeringDB here.




Keywords: madison peering MadIX BGP   Doc ID: 6636
Owner: Paul N.Group: Network Services
Created: 2007-10-23 19:00 CDTUpdated: 2013-11-15 18:43 CDT
Sites: Network Services, WiscNet