Site changelog
What changed on IX Report, day by day, newest first. Looking for networks joining and leaving exchanges? That's the change log.
Nov 6, 2026
- PeeringDB read every hour. PeeringDB's changes are now read every hour, between the full reads every 6 hours, so new networks, connections and corrections show within the hour. Exchanges' own member lists are still read every 6 hours.
- PeeringDB network log. A new page, the PeeringDB network log (linked from the Networks list), lists every network created or deleted in PeeringDB at PeeringDB's own times, including networks that came and went between two updates. It goes back to September 7, and log.csv has all of it.
- Network maps show without a click. The map on each network's page now draws by itself as you scroll to it; there's no button to press first.
Nov 4, 2026
- More columns on the Networks list. The Networks list shows each network's country and, from its page, the exchanges where it's in PeeringDB but not on the exchange's own list, the exchanges where it uses the route servers, its total port capacity and the number of items on its PeeringDB fix list (linked to the list). Every column sorts, and all of them are in the CSV download. Netnod's IX-F export gives port speeds in kbit/s rather than the Mbit/s the format calls for, so its speeds showed 1,000 times too high (a 100G port as 100T). Exports like that are now read in kbit/s: network capacity totals and the speed checks at Netnod's exchanges are right again.
- A map on every network page. Each network's page has a map: the exchanges it's on, colored by whether PeeringDB and the exchange's own list agree, and the buildings it lists in PeeringDB, marked where it's on an exchange there, where there are exchanges it isn't on yet, and where there's no exchange. It opens zoomed to where the network is. The network files in the API say how PeeringDB and each exchange's list compare (comparison).
Nov 3, 2026
- Growing networks. A Growing networks page: which networks joined the most exchanges in the last 30 days and which left the most, with the exchanges, the dates and whether each was seen on the exchange's own list or only in PeeringDB; filters for type, country and region, and a CSV download. 90-day and yearly views appear once the change log goes back that far. A Top 10 list of the networks that joined the most exchanges, and a line on each network's page with the exchanges it joined and left in the last 30 days.
Oct 31, 2026
- Download the Networks list. The Networks list can be downloaded as a CSV file: every network that matches the filters, not only the ones shown, in the table's order, with its type, policy, country, region, exchange count, how many of those exchanges it's missing from PeeringDB at, whether it's in PeeringDB, and its page.
Oct 30, 2026
- Networks filters, sortable tables, port capacity. The Networks list has four more filters: the country the network's organisation is registered in (PeeringDB), its region, whether it's missing from PeeringDB at an exchange or not in PeeringDB at all, and the networks on one exchange. Each goes in the address, so a filtered list can be linked to. Network pages: the table of exchanges sorts by any column, and above it is the network's total port capacity across its exchanges. The tables on the ghosts page sort by their column headers again.
- Fix lists as spreadsheets. Every network's PeeringDB fix list can now be downloaded as a CSV file, from the fix list on its network page or its printable page: one row per change to make in PeeringDB (add, change, remove or check), with the exchange, the addresses and speed, what PeeringDB has and what the exchange publishes.
Oct 29, 2026
- The Randy Report. Virtual IX (VIX): an exchange where more than half of the members connect through tunnels over the internet rather than a physical port is marked VIX. A member reaching a physical port over layer-2 transport counts as physical, and member size or type plays no part. The answer comes from the exchange itself: its IX-F export, when it says how members connect, or its own description, read by a person. How it's decided is on the About page. Virtual IXs aren't ranked in the Top 10s, as ghost exchanges aren't; they stay in every other list, marked VIX. Every exchange page has a "How members connect" box: the connection types in its IX-F export, the facilities it lists, how many members list a building in its country, and how many countries its members come from. The same is in the exchange's API file, and exchanges.csv has vix and vix_source columns.
- Compare two networks. A new tool, Compare two networks (/netcompare/): pick two networks and see the exchanges both are on (with how each one is listed, its port speed and whether it uses the route servers), the exchanges only one of them is on (noting when the other is on a different exchange in the same city), and the buildings both list in PeeringDB, with the exchanges in each. Every network page links to it. A network's API file (/api/net/<asn>.json) also lists the buildings it lists in PeeringDB, with the exchanges in each. Accessibility: text and link colours meet WCAG AA contrast in light and dark, links inside text are underlined, and the maps read as one labelled group to screen readers.
- Links to RIR Tracker on network pages. A network's page links to its registry history on RIR Tracker (rirtracker.com): when the regional internet registries issued, transferred or took back its AS number. The link is shown only when RIR Tracker has a page for that AS number, checked on every update. The footer lists the sister sites: IX Report and RIR Tracker.
Oct 22, 2026
- A site that's down no longer holds up the update. When an exchange's website fails twice in a row during an update (no connection, no answer, or server errors after every retry), its other pages and traffic graphs aren't asked for until the next update, and show as unavailable with the site's error. On 22 October AMS-IX's website answered with errors for half an hour, and asking each of its ten pages in turn held the update past its time limit, so the 00:17 UTC update wasn't published. Waiting to ask DE-CIX again for traffic it refused is now skipped when the update has already run long, so the update always finishes.
Oct 14, 2026
- Sitemap in parts. The sitemap has grown to over 45,000 pages, close to the 50,000 a search engine reads from one file. /sitemap.xml now lists sitemap files of up to 40,000 pages each, so it can keep growing.
Oct 12, 2026
- Feeds that stay current. The change feeds (all changes, and each exchange's and network's feed) and the sitemap could be kept for a very long time by browsers and feed readers. They're now refreshed every few minutes, like the pages.
- Monthly prices for Extreme IX and BCIX. Extreme IX's ports now show their monthly fees (1G ₹10,000, 10G ₹50,000, 100G ₹250,000) rather than their installation fees. Its price table is drawn without a standard table, and is now read like one. BCIX's ports now show their monthly fees (10G €400, 100G €1,950, 400G €3,950) rather than their setup fees. Its table lists the speeds across the top with a row for each charge, and is now read that way round; its 400G port had wrongly shown €400. The “Updated” time at the bottom of every page, and the warning shown when the site is more than 7 hours behind, now give when the data was last fetched, even when the pages themselves were rebuilt later.
- Current price lists, not last year's. When an exchange's pricing page shows more than one dated price list, such as last year's fees next to this year's, the list in force today is the one read. LONAP's page keeps its April 2025 fees beside the fees in force since 1 April 2026, and the older ones had been read: LONAP now shows £125 for 10G, £500 for 40G and £900 for 100G, rather than £150, £550 and £1,000. A price list that hasn't taken effect yet isn't read until its start date. Prices in long tables under a single “Monthly Fee” or “Monthly prices” heading now show as monthly all the way down the table (LONAP, LINX, NAMEX and BIX.BG). Extreme IX's and BCIX's 100G prices are now marked as one-time setup fees, as their pages label them.
Oct 9, 2026
- Free ports, waived fees and offers told apart. Ports an exchange says are free, with no conditions, now count as free on the cheapest lists: GLV-IX, IIX Estonia, Free-IX Greece, NSIX Amsterdam, Nell-IX NoVA, Chameleon-NAP, IXMidlands, DFW-IX and KeFF-IX, alongside IndyIX. Fees that are waived for now (DINX and NMBINX), ports free “while supplies last” (Chicago Open Pipes) and ports “currently free” (CXIX's 10G) are shown as exactly that on the exchange's page, and aren't counted as free ports. KeFF-IX's prices are now read from its port price list rather than its IX Transit price list. NSIX Amsterdam's 40G and 100G ports now show their monthly prices (€29 and €49) rather than their one-time charges.
- Ghost exchanges left off the Top 10. Ghost exchanges are no longer ranked or counted on any Top 10 list, worldwide or for a country: not among the largest, busiest, cheapest or newest, and not in the counts of exchanges per metro, per operator or per country. Only the list of ghost exchange operators is about them. IndyIX now counts as free: its page gives every port at $0 without saying per month, and a price of zero is free whatever the period. It's on the United States' cheapest list, where three ghost exchanges had taken the last places.
- ChIX's monthly prices. United IX's ChIX page lists its one-time charges under “NRC” and then its monthly charges under “MRC”, and the one-time charges were taken. ChIX now shows its monthly prices: 10G at $500 a month.
Oct 8, 2026
- Better search in the header. Picking a city in the search now opens its metro area's page (Ashburn opens Washington's), instead of a list of its exchanges. Every word typed is looked for, in any order, and words like “street” or “st” are left out, so “1530 Swift St” finds the 1530 Swift building. A number finds the network with that AS number and also buildings and exchanges with it in their name or street address.
- Remote peering estimate taken off. The remote peering estimate added earlier today is gone from exchange pages, Top 10, the About page, exchanges.csv and the API: it depends on networks listing their buildings in PeeringDB, and those lists aren't complete enough for it.
- Port prices read more carefully. TorIX's prices were misread: a 10G port capped at 1G was taken for a 1G port, and the $500 installation charge for a yearly price. Ports capped below their speed (“10GE sub 1G rate”) are now skipped, and where a price table has a monthly or yearly column, that column's price is used rather than the installation charge. TorIX now shows 10G at $1,750 a year (CAD). STHIX's 100G port now shows its monthly price (28,000 SEK) rather than its installation charge. Ohio IX's prices were shifted by a line: its page gives each price before the port speeds it covers (“$1,500 for senior members, includes use of single port (1G, 10G, 25G)”), and an extra 400G port's $6,000 was taken for the membership fee. It now shows 10G at $1,500 a year, membership and port together. ER-IX's 10G and 100G prices, written the same way, are read correctly too.
- IX.br's prices. IX.br's port prices for São Paulo, Rio de Janeiro and Fortaleza (10G: R$ 690 a month, taxes included) are now read from the price list IX.br publishes as a PDF on its documentation page; the current link is looked up there on every update. IX.br São Paulo is now the best value 10G port on Top 10. IX.br's other locations don't charge through IX.br, though the building's operator may, so they still show no price. When an exchange's price list is a PDF with a table, the monthly-total column is read (not its parts, such as maintenance and operation).
- HKIX's prices and members list. HKIX's port fees (10G: HKD 7,800 a month) and its participants list are now read. Its website's links are relative to another folder (a <base> tag), which the website search didn't follow; it now does for every exchange. Price tables with more than one heading row (one naming the billing, NRC and MRC, above one naming the currency) are now read, and a port written just “GE” counts as 1G.
- Traffic graphs: idle exchanges and missing pages. Some exchanges' traffic graphs show almost nothing (BBIX Chicago, Dallas and London: a few hundred bits per second at most), printed without a unit, so they couldn't be read. Their pages now say so under the graph, with the numbers the graph gives, and the files and API carry them. A graph whose address now leads somewhere else (BBIX Miami's goes to BBIX's site map) says where, instead of just 'not an image'. DE-CIX's Oslo, Kristiansand, Copenhagen, Helsinki, Esbjerg and Stockholm pages now say DE-CIX publishes no traffic statistics there (PeeringDB links statistics pages that don't exist), instead of an error code.
- Networks list links every network page. The Networks list now links the name of every network that has a page, including the networks that are on no exchange but list buildings in PeeringDB: their pages show the exchanges in those buildings.
- Badges and a read-only API. Every exchange has a badge to embed on its own website, a wiki or a README (for example “903 members · 94% in PeeringDB”): the code is under Embed this badge on its page. The share is of the networks on the exchange's own member lists that PeeringDB lists there, and it's left off when there's no list to compare. The site's data is now also available as JSON, one file per exchange (/api/ix/<id>.json) and per network (/api/net/<asn>.json), plus an index of every exchange. They're static files rebuilt every 6 hours, with no key needed; the Downloads page explains the fields.
- Route server activity. Where an exchange's route servers have a public looking glass (about 190 exchanges, including DE-CIX, LINX, AMS-IX, IX.br, Netnod and many on IXP Manager), the site reads it once a day: the exchange's page has a Route servers panel (sessions up, networks sending routes, routes accepted), and the networks table's RS column shows how many routes each network sends. Network pages show the same per exchange. The Largest exchanges list adds how many networks send routes to each exchange's route servers; the ranking itself doesn't change. Networks with a session on an exchange's route servers now count in the ghost test. exchanges.csv has two new columns, and each exchange's Data status shows whether its looking glass could be read. The About page explains how.
- Value for money: 10G cost per network. Exchange pages with a comparable 10G price now say what it costs a month for each network you can reach (the monthly price, membership included, divided by the peers). Top 10 has a new list, Best value 10G ports: the lowest cost per network, for exchanges with at least 50 peers that charge for ports. It only covers exchanges whose websites publish a price this site can read; free exchanges are on the cheapest list. exchanges.csv has two new columns: the 10G monthly price in US dollars and the cost per network.
- A page for every metro area without an exchange. Every metro area of 500,000 people or more without an exchange (in the US, the Census Bureau's metropolitan statistical areas) now has a page: its population, the three nearest exchanges and the building each is measured to, any ghost exchanges there, exchanges Euro-IX's IXPDB lists there that PeeringDB doesn't have, and the networks already in its buildings that would be likely first members. Top 10 > Places has a new list, Largest US metro areas without an exchange, next to the US states list. The rows of the metro area lists now open these pages, and metro-gaps.csv has a page column. US metro areas are now measured from their first principal city instead of the middle of their counties (Riverside, CA was 175 km from an exchange; it's 50 km from MegaIX Los Angeles). Fixed: CM-IX in Mount Pleasant, Michigan was placed in Mount Pleasant, South Carolina, on the map and in distances, because its building has no coordinates; buildings like it are now placed by their ZIP code. And Shenzhen was listed as having no exchange because CNIX Qianhai's building sits just inside the Hong Kong urban area on the map; it now counts for Shenzhen.
- Monthly reports. A report for every month at /report/ (October 2026 so far): new and removed exchanges, new ghosts and exchanges that came back, the exchanges that gained or lost the most members, joins and departures by the 100 networks on the most exchanges, member lists that broke, were fixed or were read for the first time, and the month's totals. Comings and goings that undo themselves within the month (a network that left and rejoined, an exchange removed from PeeringDB and added back) are left out, and an exchange removed from PeeringDB isn't counted as a ghost coming back. Each report has a plain-text version for operator mailing lists, with a Copy button, and there's a feed with one entry when each month ends.
- Traffic over time. Exchange pages with a traffic graph now also show the daily peak over time: the highest point each day on the graph the exchange publishes, for every complete day read. It started with the days in each exchange's current graph and grows by a day at a time; exchanges that only publish a picture, or a year-long graph, aren't included. Charts that cover fewer than 14 days say when collecting began.
- Feeds for every network and country; broken member lists. Every network now has a feed of its own (Follow changes on its page), so you can follow, say, one network joining and leaving exchanges in a feed reader. Every country with an exchange has a changes page and a feed too (/changes/country/<code>/), linked from the Changes page, and from the exchange list and Top 10 when a country is picked. New in the change log: a member list (IX-F export or website list) that read before and then can't be read on 4 updates in a row is noted as broken, with the reason, and again when it reads. These appear on the exchange's page and in its feed. Feed entries now carry a one-line summary with the place and the update they were seen in, for feed readers that only show summaries. Network and country pages announce their feeds to browsers and feed readers (autodiscovery), like exchange pages already did.
- Operator reports for every exchange. Each exchange whose own member list could be read has a printable operator report at /ix/<id>/report/: members on its lists but missing from PeeringDB, members whose addresses or port speeds differ from its IX-F export, and members in PeeringDB that aren't on its lists, each with the network's public PeeringDB contact (the peering contact first, then technical, then NOC). The same list downloads as a spreadsheet (report.csv). The exchange page links to the report from its header, its fix list and its address checks. Only contacts the networks made public on PeeringDB are used. On the page, addresses are filled in by the browser so simple address harvesters don't pick them up.
- A PeeringDB fix list for every network. Each network's page now has a PeeringDB fix list: exchanges whose own member list (IX-F export or website) has the network but PeeringDB doesn't, addresses and port speeds that differ from the exchange's IX-F export, PeeringDB entries that none of the exchange's own lists include, and entries at exchanges that look shut down. Each item gives the values to enter in PeeringDB (peering LAN, IPv4, IPv6, speed in Mbps, route server peering), one entry per connection, and links to the network's PeeringDB page. Where the exchange has PeeringDB's IX-F import switched on, it says so: PeeringDB then suggests the change itself, or makes it for networks that allow automatic updates. Networks with anything to fix also get a printable page at /net/<AS number>/fix/. Tools has a new box, "Find your network's fix list": type an AS number or a name. Exchanges whose lists couldn't be read on this update are left out of every fix list rather than reported from an older copy.
Oct 7, 2026
- BBIX Tokyo and Singapore back on the Busiest list. BBIX's graphs for Tokyo and Singapore are measured again: the tick mark beside an axis label was being read as an extra digit, and a legend number that lost its decimal point ("544 T" for "5.44 T") is now tried with the point restored. As before, at least two of the graph's own numbers have to match the curve.
- Network pages for every network in a building. Networks listed in a building in PeeringDB but on no exchange now have their own page, with the exchanges in their buildings they could join. Links to them from facility pages, metro pages and the tools used to say "That page isn't here". The Facility reach comparison now shows every network's name, including networks that aren't on an exchange. Network lists on facility and metro pages, and in the comparison tools, line up on the left again; the name and type were spread across the line. Change log lines for a network that has left its last exchange no longer link to a page that doesn't exist.
- Ghost exchanges: clearer dates and sources. The Ghosts page now says plainly that networks count wherever they're listed: PeeringDB, the exchange's IX-F export or the members list on its website. Each network on a ghost's row carries PDB, IXF or WEB badges for where it was seen. Exchanges that were already ghosts when tracking began (October 2, 2026) say "Already a ghost when tracking began" instead of that date, on the Ghosts page, on their exchange page and in ghosts.csv (new already_when_tracking_began column). When a ghost's member list couldn't be read, its row and exchange page say why, so its members aren't known. Monitoring networks such as DE-CIX Monitoring no longer count as an outside network.
- Metros: old addresses kept, clearer table. Metro pages that merged into a bigger metro area or changed address now send visitors on to the right page (/metro/campo-limpo-paulista-br/ goes to São Paulo); a page with no successor goes to its country's metros. The Metros table reads properly when copied or read aloud ("50, of which 20 based here"), and its headings no longer run together on phones. US metro areas are centred on their own counties, and Census names like "Louisville/Jefferson County" show as Louisville.
- Metro areas without an exchange: real metro areas. The Top 10's "Largest metro areas without an exchange" and "Most isolated big cities" now use the same metro areas as the metro pages (functional urban areas outside the US, Census metropolitan areas in it). A metro area counts as covered only when a real exchange has a building inside it, not when one is within 50 km of its centre: the US list now has 51 metro areas of 500,000+ people, up from 19. The list notes say what isn't counted: exchanges missing from PeeringDB (Nagoya has a JPIX switch PeeringDB doesn't list). metro-gaps.csv gives each population's year.
- Metros: US Census metro areas. US metro pages now follow the Census Bureau's metropolitan statistical areas: a building is placed by its county (from its ZIP code), so San Francisco–Oakland and San Jose are separate metros, and each page names its Census area and 2024 population. Towns just outside a metro join it; elsewhere a town keeps its own page, named with its state (Buffalo, NY and Buffalo, WY). An exchange now always sits in the same metro as its home building.
- Metros: real metro areas outside the US. Metro pages and the Metros list now place exchanges and facilities in real metro areas: the city and its commuting zone, as the European Commission's Global Human Settlement Layer maps them (functional urban areas), rather than within 60 km of a city. Campo Limpo Paulista is now part of São Paulo; Düsseldorf is its own metro, apart from the Ruhr; Slough's data centres count in London. City names are matched with or without accents (Zürich, Düsseldorf) and in PeeringDB's other spellings (Kiev, Kharkov, Odessa), so one city no longer appears as two metros (Frankfurt, Zürich, Kyiv). Metro page addresses spell accented names in plain letters (/metro/sao-paulo-br/).
- Port fees: more accurate, and clearer about what's compared. The port-fee reader was checked against every price page this site reads, and many misreadings are fixed: quantities, coordinates and BGP communities taken for prices (SGIX, LOCIX, NetIX), setup fees taken for monthly ones (Manama-IX, UIXP, Hopus, STHIX), quarterly billing notes taken for the price period (AMS-IX Eastern Caribbean is $2,500 a month, not a quarter), and billing periods in French, Spanish, Turkish and Polish. Tables are read row by row: a "Monthly fee" column is preferred over a setup fee, ports rated below their size ("2 Gb on a 10 GE port") aren't counted as full ports, and a table with a column per exchange (INX-ZA: JINX, CINX, DINX, NMBINX) is read for each exchange's own column. Membership fees are read too: the price lists compare what a new member pays for one 10G port, membership included (MIX-IT: €600 a month plus €500 a year). Exchanges that charge for the port plus a separate fee for the bandwidth or service on it (LINX, Netnod, France-IX), and a few price lists this site can't read reliably, aren't compared; their pages say why and link the price list. DE-CIX's exchanges now say their prices are on request, as DE-CIX's site does. NAPAfrica, INX-ZA and MIX-IT price pages are now read. The Most expensive and Cheapest lists now say how many exchanges they cover.
- Member lists: Netnod's VLANs, clearer failures. Netnod lists one exchange per VLAN in PeeringDB (Stockholm BLUE and GREEN, at three MTUs) but one per city in its IX-F export. Each is now read from its own VLAN's members, so nine Netnod exchanges that failed have their lists, and the others count only their own VLAN. ixFabric's export addresses (listed in Euro-IX's IXPDB) now send visitors to an unrelated site, and ixFabric publishes no list elsewhere. Their pages and the Checks page say so, and no longer link to it. Checks page: an export that doesn't include an exchange now says what it does list ("it lists only GNM Internet Exchange"), and an export with no members says "Lists no members". The Data status box on exchange pages is readable on phones again.
- Any2 member lists from CoreSite. Any2West, Any2East, Any2Chicago, Any2Denver and Any2Florida now have a members list beside PeeringDB: CoreSite, which runs Any2, publishes one participants table for all five, and each exchange's page reads its own rows (Any2West: 284 networks, 47 of them not in PeeringDB). Members pages that list several exchanges in one table can now be read for one exchange at a time.
- IPv6 list: lowest adoption instead of highest. The Top 10's IPv6 list now shows the exchanges with the lowest IPv6 adoption. The highest were all at 100%, so that ranking said nothing; the note now says how many exchanges have every member on IPv6. Adoption counts only members whose addresses are known (from PeeringDB or the exchange's IX-F export): members known only from a website list, which gives no addresses, no longer count as having no IPv6. Exchanges that list no IPv6 peering LAN in PeeringDB aren't ranked, and the note says how many.
- BBIX, JPIX and more traffic measured from graph pictures. BBIX and JPIX publish a traffic graph for each location as a picture. This site now measures them, so BBIX Tokyo, Osaka, Singapore, Hong Kong, Bangkok, Amsterdam and Fukuoka, JPIX Tokyo, Osaka and Fukuoka, and YYCIX have their traffic on their pages and on the Busiest list. JPIX shows only its last 24 hours, so this site builds up a week from successive reads. Before, every BBIX exchange showed BBIX's company-wide graph, and every JPIX exchange showed Tokyo's. Locations without a graph of their own (BBIX US-West and Manila, JPIX Hokkaido) now show no traffic instead of another location's. The measuring now reads each graph's axis labels as well as the numbers under it, and works for graphs whose axis doesn't start at zero. A picture that can't be measured with confidence is still shown as a picture. A news picture ("exceeds 150 Gbps") is no longer shown as SNS-IX's traffic graph.
- IX.br traffic on the Busiest list. IX.br's traffic is now read for all 40 of its exchanges, so IX.br São Paulo (33 Tbps) tops the Busiest list, with Fortaleza and Rio de Janeiro in the top 10 and every IX.br location ranked in Brazil. IX.br publishes its traffic only as pictures of graphs. This site measures each curve from the picture, on the graph's own scale, and checks it against the maximum, average and current numbers printed under the graph; if they don't agree, the traffic is shown as unavailable rather than guessed. Exchange pages say when their traffic was measured this way.
- AMS-IX traffic on the Busiest list. AMS-IX's traffic is now read for 11 of its 12 exchanges: Amsterdam is second worldwide on the Busiest list, and AMS-IX Lagos, Singapore, Mumbai, Kolkata, Hong Kong, Bangkok, Manila, Djibouti, Hyderabad and Eastern Caribbean have traffic on their pages. Like DE-CIX, AMS-IX publishes its last 2 days, so this site builds up a week from successive reads. AMS-IX Caribbean's statistics link leads to Amsterdam's page, so its traffic shows as unavailable rather than as Amsterdam's.
- DE-CIX traffic on the Busiest list. DE-CIX's traffic is now read for each of its locations that publishes it (18 of 24), so DE-CIX Frankfurt, Dallas, New York, Chicago, Madrid and others are on the Busiest list. DE-CIX publishes only its last 2 days, so this site keeps each read and builds up a week from them; until the week is there, the exchange page says how many days its graph covers. DE-CIX's Nordic locations (Oslo, Copenhagen, Helsinki, Stockholm, Kristiansand and Esbjerg) have no statistics page, so their pages show their traffic as unavailable.
- Busiest list: clearer about what it covers. The Busiest list now says it ranks peak traffic in one direction (the way exchanges quote it), and how many exchanges' traffic this site can read. Exchanges that show traffic only to members, such as LINX, aren't ranked. Exchanges whose IX-F export puts their switches in many cities across several countries are marked: their traffic is the whole network's, though PeeringDB lists them under one city (GNM-IX: 30 cities in 17 countries). A traffic graph that stops updating and reports zeros no longer counts the zeros as traffic; the exchange page says when the graph's data ends.
- Port tables count physical ports. The "Ports and fees" table on exchange pages now counts each physical port in the exchange's IX-F export. Before, a member with several ports bundled together (say 2 × 100G) was counted as one port at the combined speed, so exchanges showed 200G or 400G ports they don't offer.
Oct 6, 2026
- Network pages: facilities, exchanges in reach, and route servers. Each network's page now lists the facilities it has in PeeringDB, with how many of the exchanges in each building it's on. New list on each network's page: exchanges with a switch in one of its buildings that it isn't on yet, biggest first, with the buildings they share. Joining one of these is usually just a cross-connect. Ghost exchanges are left out. The exchanges table on network pages has a route server column, and the counts show how many exchanges' route servers the network uses. Route server use now also comes from each exchange's IX-F export, not only PeeringDB, on exchange pages too (AMS-IX and LINX show many more route server users). Network pages link to the tools, already filled in: Where can I peer with this network? and Where should it peer next? On the Networks list, a network's name and its exchange count now open its page (the name wasn't a link before, and the count opened the front page's exchange list). Removed the "On the exchange list" link from network pages: it opened the front page's exchange list filtered to the network, which looked like the unfiltered list and repeated the network page's own exchange table.
- Traffic that can't be read now says so. When an exchange's traffic graph can't be read on an update, its page now shows the traffic section as unavailable, with the reason in plain words (for example, the server refuses the request, doesn't answer, or the graph is a flat line all week) and a link to what was tried. Before, the section just disappeared. As always, no old copy is shown in its place.
- Traffic from IXP Manager for many more exchanges, and IX.NET's traffic. Exchanges that run IXP Manager now show their own traffic, read from its graphs: 36 more exchanges, including FL-IX, JKT-IX, CIX-ATL, Extreme IX, TRUE-IX and KIXP. Their statistics pages draw the graphs inline, so the IXP Manager logo had been taken for a traffic graph. Four CANIX exchanges that only had a picture of their graph now have the numbers too. Where one IXP Manager runs several exchanges (INX: JINX, CINX, DINX), each exchange gets its own infrastructure's graph instead of the operator's total. Graphs that aren't real traffic are no longer shown: IXP Manager's built-in sample data (a week from February 2016, peaking at 96 Gbps, which some exchanges served), graphs that show no traffic at all, and graphs that are a flat line all week (a stuck reading). KCIX, STLIX and SpringIX now publish their traffic as data from the IX.NET portal instead of a picture of a graph, so they're ranked with everyone else.
- Operators, countries without an exchange, a more detailed map, and every port speed. New Operators page in the top menu: every organization that runs an exchange, ranked by how many it runs, with its countries, markets and unique networks. Each has its own report page, including operators with a single exchange. Filter by name or country, and sort by any column. Top 10: new lists for the operators with the most exchanges and the largest countries without an exchange. Map: country borders are clearer, and state and province borders now show: they had stopped drawing after the first few lines because of a fault in the map file. The large countries' borders are always on, and every country's appear as you zoom in. Countries with no exchange (or only ghost exchanges) are shaded, with a switch to turn the shading off and a full list under the map. Exchange pages: the fees section is now Ports and fees. It lists every port speed the exchange publishes and every speed its members are connected at, with how many connections use each, so speeds missing from the price list still show. Metros: an area's exchanges now include the ones based elsewhere that list one of its buildings in PeeringDB (an extension switch or remote site). Kansas City now shows 16 exchanges, 6 of them based there. Areas with networks in their buildings but no exchange get their own pages. An exchange whose only PeeringDB facility is far from its own city is now placed at its city (SIOUIX was shown in Kansas City). Busiest exchanges: a traffic graph published for several exchanges is counted once. SIX Seattle and its Jumbo LAN share one graph, which had put SIX in the list twice. A few IXP Manager logos and member-count graphs that had been read as traffic graphs are ignored. Long tables keep their column headings in view as you scroll, just under the filter bar. Fixed: exchanges whose addresses and speeds all match PeeringDB said "0 have differences" and offered a CSV that didn't exist; ports listed at $0 were sometimes labelled one-time; links to metro pages that didn't exist.
- IX-F export list says whether PeeringDB imports it. The IX-F exports download (ixf-exports.csv) has a new last column, peeringdb_import: whether PeeringDB's IX-F import is switched on for the exchange, as the Checks page already shows.
Oct 5, 2026
- Checks link moves to the footer. The Checks link moved from the top menu to the footer, between About and Changelog. It's also on the Tools page.
- Map: facilities switch off again. Map: unticking Show facilities now hides the facility dots again (they stayed on the map once shown), after a visitor reported it. Where facility dots overlap, a click now lists them all to pick from, as it does for exchanges.
- Checks: IX-F exports, addresses and port speeds. New Checks page (/checks/): every IX-F export that couldn't be read on the last update, what goes wrong in plain words (the name doesn't resolve, the certificate expired, the server refuses us or times out, the file isn't an export or doesn't include the exchange), since when, and when it was last read. Exports that are read get warnings for an old timestamp, a missing PeeringDB id, or no IP addresses or port speeds. Also: every export that was read, with its schema version and date, the exchanges with no export, and how to publish one. Addresses and port speeds: for every network in both PeeringDB and the exchange's IX-F export, its IPv4 and IPv6 addresses and total port speed are compared, and an address the export gives one network but PeeringDB lists for another is flagged. Each exchange page has the list (with a CSV file), network pages tag the exchanges with differences, and /checks/ ranks exchanges by them. An exchange's Data status box says in plain words why its IX-F export couldn't be read. Downloads: address-checks.csv and ixf-exports.csv; exchanges.csv gains the number of networks with address or speed differences.
- 4IXP members list. 4IXP: its members page is read (1,007 connected networks), after a visitor suggested it. Its server refused our requests until the collector's name carried a version number, and it sends a first visit to its home page to set a language cookie, so the page is now asked for again once the cookie is set. Members marked "Installing" (also "ordered", "reserved", "onboarding") are no longer counted until they're connected.
Oct 4, 2026
- IX.br: 39 of 40 locations. IX.br: participant lists for 39 of its 40 locations (Macapá's page lists none yet). A location's page that fails to load during the search is asked for again instead of being skipped until the next week's search. A members page that the exchange's own menu labels with its city is used even when it lists many more networks than PeeringDB does (IX.br Ribeirão Preto: 30, against 15 in PeeringDB). A network's name with a number in it ("L3 Networks") is no longer read as the exchange's stated member count.
- AMS-IX and LINX members lists. AMS-IX: its connected-networks page is read from the data the page carries for its scripts (898 networks), after a visitor suggested it. LINX: its members list is read from LINX's public member data, which covers all of its exchanges: LON1, LON2, Manchester, Scotland, Wales, NoVA, Nairobi, Mombasa and Accra, plus center3 IX Jeddah and Riyadh, which LINX runs. Each exchange gets only its own networks. A suggested list that covers several exchanges is used for each one it names, once each has passed the same checks.
- Prices compared, and every Top 10 by country. Every Top 10 list can be filtered by country. Metros with the most exchanges replaces Cities with the most exchanges: exchanges are counted per metro area (a city and everything within 60 km), so a metro's suburbs count with it. Top 10: the cheapest exchanges, free ones first, alongside the most expensive. Metro reports show what a 10G port costs at each of the area's exchanges. The change log notes when an exchange changes its published port fees, with a FEES badge. The Ghosts page lists exchanges whose website is gone (down at two weekly checks a week apart), and the websites that were down at the latest check. IX.br: every location's participant list is read from IX.br's own participants pages (São Paulo alone lists 2,704 networks); the website search now follows a members page's menu of locations, and looks behind "Localidades"-style links.
- Prices in pictures, Metros, FD-IX. Port fees that an exchange publishes as an image (IX-Denver's price table, for one) are now read with text recognition, re-read every update, and the exchange page links to the image they came from. A price list's "effective" date no longer makes it look like a dated note. Metro interconnection reports have their own Metros link in the top bar; About moved to the bottom of every page, next to the Changelog. Top 10: the most expensive exchanges, by the monthly price of a 10G port in US dollars (converted at the European Central Bank's daily rates). Members lists that a page carries in its own data for its scripts (FD-IX's location pages) are read in full, not just the first page of the table. When one exchange's members page is known, the same address pattern is tried for its sister exchanges' cities (FD-IX St. Louis, Cleveland, Houston, Amarillo and Chicago).
- Fixes after the big update. Exchanges that say they charge nothing for ports ("$0 monthly port fees", "zero port fees") now show that in Port fees, as the IX.NET exchanges do. The Not found boxes on exchange pages accept addresses again. A few dozen changes wrongly logged as networks leaving, the day the stricter list reading started, were removed. Every change has a source badge; changes from before sources were tracked have a –.
- Port fees, three-source comparison, new tools. Port fees: each exchange page has a Port fees section, read from the pricing or join page on the exchange's own website, with the sentence each price was read from. Where none has been found, the page says so, with a button to add the page. A fees.csv download lists them all. Not found buttons: where no members list or fees page has been found, the exchange page has a Not found button that turns into a box for the address. Suggestions are checked automatically at the next update, with the same checks as the website search, and used only if they pass. Peers: the exchange list is sorted by peers, the highest of each exchange's three counts (its website's members list, its IX-F list, PeeringDB), and the number used is highlighted. Match bar: it now compares all three sources. Green networks are in every source; the other colours are networks not in PeeringDB, networks only in PeeringDB, and networks on only one of the IX-F and website lists. Exchange pages show the same bar, and their members chart shows all three sources. Members column: "Not found" instead of a dash, linking to an email to tell us where the list is. Change log: every change has a badge for where it was seen: PDB (PeeringDB), IXF (the IX-F list), WEB (the exchange's website). Networks added to or dropped from just one source, while another still lists them, are noted too. Changes from before this update have a – badge, since their source wasn't recorded. Map: more detailed outlines, state and province borders, and city names that appear as you zoom in. Click a dot to open its exchange (where dots overlap, a click lists them all), and switch on the facility layer to see data centers with an exchange. Facilities: three measures, for different questions: total peers (the members of every exchange in the building added up), unique reach (each network counted once), and networks listed in the building. Each facility also shows how many listed networks don't peer on its exchanges, and which ones. New tools: an exchange recruitment report (networks in its buildings, its metro, neighbouring exchanges and comparable markets that aren't members yet, with the evidence); What does my next exchange add?; metro reports, one page per market; facility reach comparison; operator reports, each operator's exchanges as one portfolio. Exchanges that aren't in PeeringDB can now be added; their pages say so. Members lists found on exchange websites are always used, even when the page shows the exchange's IX-F export, so a change on either side shows up (FL-IX, CIX-ATL and CIX-NoVA among them). DE-CIX: members lists for 31 of its 38 locations, up from 6. Powered by IX.NET at the bottom of every page, and this changelog. The text on every page was checked against how the site works now.
- More accurate members lists. The exchange list always loads fresh data: browsers could keep an old copy of it. Members pages are read more carefully: the AS-number column is taken only from the members table (dates and data-center tables elsewhere on the page were being read as AS numbers), tables are found even without a header row, and a status column is used only when it holds statuses. Lists read by network name are used only when most of their entries are recognised, and lists far below the count an exchange states (a page of highlighted members, say) aren't used. A page listing the members of several exchanges is used only for the one it matches. The member count an exchange states is used when it fits what the lists show, including on websites shared by several exchanges (SIX Seattle) and on each location's own page (DE-CIX). DE-CIX: members lists read from its location pages, the first six locations.
Oct 3, 2026
- Never out of date. Nothing old is shown: if a list, members page, traffic graph or stated count can't be read, it shows as unavailable, with the reason, until it can be read again. If the whole site hasn't updated for more than 7 hours, every page says so at the top. The member count an exchange states on its website ("371 members") is shown as The exchange says, re-read every update. Members lists in data files behind a page (CSV and JSON, or a page's non-JavaScript version) are found and read, counting each network once and only rows marked connected. Traffic from exchanges' statistics pages, including SIX Seattle's 12-month chart from its daily figures.
- Three sources and traffic. Exchange pages show three sources side by side: PeeringDB, the IX-F export and the members list on the exchange's website, with a badge per network. The exchanges table shows Members, IX-F and PeeringDB, in that order. Traffic charts for exchanges that publish their traffic, and a Busiest exchanges list. The website search goes two clicks deep and recognises members lists by network name. Change logs and news pages are no longer mistaken for members lists (SIX Seattle's list of updates was).
- Change archive and tools. The change log is kept forever, with a monthly archive and a search by exchange, network or facility. Site search, Where should I peer?, Compare two exchanges, and CSV downloads. A Report a correction link on every exchange page. The map zooms and pans. Metro areas without an exchange, one per country with the nearest exchange, and the most isolated big cities. Feeds open as a readable page in a browser.
- Network, facility and map pages. A page for every network and every facility with an exchange. A world map of exchanges, and a US map of the states and metro areas without one. Growth charts, fix lists (as CSV), and a feed of changes for every exchange. A Data status box on each exchange page, saying what the last update found. Ghost exchanges get a badge, country filters and a list of their operators. Top 10 lists for the largest US metro areas and states without an exchange.
Oct 2, 2026
- Changes, ghosts and the website search. A Networks page: every network in PeeringDB, with how many exchanges it's on. Member lists from Euro-IX's IX-F database where PeeringDB has none. A log of networks joining and leaving exchanges, and the latest changes on the front page. Ghost exchanges: exchanges with fewer than two outside networks. Top 10 facilities and cities, with a country filter; flags you can click to filter by country. A weekly search of exchange websites for their members lists.
- IX Report launches. Every internet exchange in PeeringDB, with the member list each exchange publishes compared against PeeringDB. Exchange pages with every network, its addresses and its port speeds, and a Top 10 page. Updated every 6 hours.