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 Wisconsin-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


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
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
  • To subscribe: join-madix-notifications at
  • To email the list maintainer: owner-madix-notifications at

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  V4 BFDV6 V6 BFD Peering Email Peering Phone Support Email Support Phone
US Signal 26554
 ::E 888.663.1700 888.663.1700
MN VoIP32621144.92.233.228
 ::F  peering@mnvoip.com612.392.6814service@mnvoip.com612.355.7740
5NinesData 16842 YES  ::6  support@5nines.com608-512-1007 608-512-1000
UW Madison
note: serviced by AS3128.
Please peer with AS3128.
 59144.92.233.230  YES  ::1 YESpeering-uw@lists.wisc.edu608-263-4188noc@doit.wisc.edu608-263-4188
CDW (formerly Berbee) 3599   ::9 hostmaster@berbee.com608-288-3000help@berbee.com608-288-3000
WiscNet2381144.92.233.232YES YES::2 608-442-6761
TDS Telecom 4181
 ::7 Kevin Roberts 608-664-4690
Brad Fick 608-664-4667 608-664-4200
Charter 20115 866-603-3199 866-603-3199
SupraNet 4150 YES
 YES::5  YES (608) 836-0282 (608) 836-0282
ResTechServices 46262 608-237-1113 608-663-3868
UW System Network  3128144.92.233.237   YES  ::3 YESpeering@uwsys.net608-263-4188 noc@uwsys.net608-263-4188
AirStream Communications 11796
 ::D 866-206-2027 866-206-2027
Netwurx 26785 YES  ::4  Adam St. George
David Roller
414-831-3465 (Adam)
414-831-3475 (Dave)
Mad City Broadband
 YES::8  YES (608) 836-0282 (608) 836-0282
Vernon Telecom
53849 YES
 Reggie Nelson <> 608 634 7442 608-634-3136 Ext: 264
Bug Tussel Wireless
[was: Spiralight]
 ::A  Andrew Hoyos
Brian Sagrillo
(608) 320-2000 (920) 940-0001
Multicast Monitoring Port        David Treptow
608-634-7437 608-634-3136 Ext: 264
Hurricane Electric
(510) 580-4100 (510) 580-4100
Hoyos Consulting
608-616-9950 608-616-9950
UPNetWI398310144.92.233.246   ::10  upnetwi@gmail.com608-234-5980upnetwi@gmail.com608-234-5980                
 Akamai via 2381     Contact for details   
 Netflix via 2381     Contact for details    

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 portsAvailable!
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 equipment (our a demarc panel you provide) and we will take it from there.
non-oversubscribed switching backplane4500x
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 directoryWe are on PeeringDB here.