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:
  • 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.
You can get connected to the exchange via the following institutions which have high speed circuit capability at 222 West Washington:
  • 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 notfor peering coordination nor general-purpose discussion.
  • Mailing list: madix-notifications at
  • To subscribe: email notices at

Traffic Statistics:


As of 2023/09/06, MadIX statistics are hosted by AS3128.  We considered an attempt at keeping ifOctets history but ran into difficulties as AS59 and AS3128 use different CF, RRA defs and polling cadences.   As of 2023/05/01 AS59 administration required us to remove public access to AS59 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 BFD V6 V6 BFD  Peering Email Peering Phone Support Email Support Phone    
US Signal 26554   ::E 888.663.1700 888.663.1700
MN VoIP 32621   ::F 612.392.6814 612.355.7740
5NinesData 16842 YES   ::6 608-512-1007 608-512-1000
UW Madison
note: serviced by AS3128.
Please peer with AS3128.
 59    YES  ::1  YES 608-263-4188 608-263-4188
CDW 3599      ::9 608-288-3000 608-288-3000
WiscNet 2381 YES  YES ::2  YES 608-442-6761 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   3128     YES  ::3  YES 608-263-4188 608-263-4188
Win Technology 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) 800-638-9879
Mad City Broadband 5683  YES ::8  YES (608) 836-0282 (608) 836-0282
Vernon Telecom
Bug Tussel Wireless
[was: Spiralight]
33125   ::A   Andrew Hoyos
(608) 320-2000 (920) 940-0001
Multicast Monitoring Port          David Treptow
608-634-7437 608-634-3136 Ext: 264
Hurricane Electric 6939   ::B (510) 580-4100 (510) 580-4100
Hoyos Consulting 53597  YES ::C  YES 608-616-9950 608-616-9950
UPNetWI 398310      ::10 608-234-5980 608-234-5980
 LiteWire 32003     YES  ::11  YES 608-882-4728 608-882-4278
 20C 35848    YES  ::12 YES                                                                       
 Akamai  via 2381           Contact for details      
 Apple  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 vlan Available!
Private vlan Available! (just ask)
1G ports Available!
10G ports Available!
ethertype 0x0800 Yes, we allow legacy ethertypes.
ethertype 0x86dd No problem.
ethertype 0x8606 Yes, we allow legacy ethertypes.
ipv4 multicast filtering We can support v4 multicast, and we do IGMP & PIM snooping.
ipv6 multicast filtering Not supported (yet). MLD snooping is not currently enabled.
BPDU filtering You send us BPDUs, your port goes into errdisable for 30s with auto recovery
customer demarc The 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 backplane 4500x
inter-switch congestion There is a 20G etherchannel between the two switches which is congestion free.
inter-switch path diversity The 20G etherchannel between the two switches is provisioned as a 10G on each side of UW's metro ring.
redundant power feeds The 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 failures See above. Let us know if you have any questions & we can try to clarify.
PI address space from an RIR UW-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 server None. You're on your own.
NOC contact information See above contact info table. UW-Madison runs the IXP operations.
Service-affecting maintenance announcements See 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).
Monitoring The UW NOC monitors MadIX for performance degradation and service affecting events.
Procedure for performance degradation event notifications In 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 numbers See 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 directory We are on PeeringDB here.

Keywordsmadison UWSysNet peering MadIX BGP   Doc ID6636
OwnerPaul N.GroupNetwork Services
Created2007-10-23 19:00:00Updated2023-12-01 09:25:36
SitesNetwork Services, Systems & Network Control Center
Feedback  4   0