ixreport

Bloomberg

AS10361

Bloomberg, LP

4Exchanges
0On an exchange's list, not in PeeringDB
1In PeeringDB, not on the exchange's list
EnterpriseType
SelectivePeering policy
3Using the route servers
3To fix in PeeringDB
2Facilities in PeeringDB

Tools: Where can I peer with Bloomberg? · Where should Bloomberg peer next? · Compare Bloomberg with another network

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

3 things to fix in Bloomberg's PeeringDB record, from what its exchanges publish: 2 to correct, 1 to check. As of 2026-11-19 18:41 UTC.

Make the changes on Bloomberg's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Correct these entries (2)

Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.

  1. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB195.66.227.137195.66.227.137 195.66.227.217
    IPv6 address missing from PeeringDBnone2001:7f8:4::2879:1 2001:7f8:4::2879:2
    Port speed differs100G2 × 10G
    • In the entry with IPv4 195.66.227.137: set IPv6 to 2001:7f8:4::2879:1 (now empty); set Speed to 10000 (10G) (now 100000).
    • Add an entry: IPv4 195.66.227.217, IPv6 2001:7f8:4::2879:2, speed 10000 (10G), RS peer yes.
  2. South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa · PeeringDB 592
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:43f8:6d0::11:65 2001:43f8:6d0::11:66
    • In the entry with IPv4 196.60.11.65: set IPv6 to 2001:43f8:6d0::11:65 (now empty).
    • In the entry with IPv4 196.60.11.66: set IPv6 to 2001:43f8:6d0::11:66 (now empty).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If Bloomberg has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. United States DE-CIX New York New York, United States · PeeringDB 804Not on its IX-F export or website members list
    IPv4206.82.104.159
    IPv6–
    Speed100000 Mbps (100G)
    IPv4206.82.104.200
    IPv6–
    Speed100000 Mbps (100G)

Exchanges over time

01234Oct 3, 2026Nov 19, 20264
Show as a table
DateExchanges
Nov 19, 20264
Nov 18, 20264
Nov 17, 20264
Nov 16, 20264
Nov 15, 20264
Nov 14, 20264
Nov 13, 20264
Nov 12, 20264
Nov 11, 20264
Nov 10, 20264
Nov 9, 20264
Nov 8, 20264
Nov 7, 20264
Nov 6, 20264
Nov 5, 20264
Nov 4, 20264
Nov 3, 20264
Nov 2, 20264
Nov 1, 20264
Oct 31, 20264
Oct 30, 20264
Oct 29, 20264
Oct 28, 20264
Oct 27, 20264
Oct 26, 20264
Oct 25, 20264
Oct 24, 20264
Oct 23, 20264
Oct 22, 20264
Oct 21, 20264
Oct 20, 20264
Oct 19, 20264
Oct 18, 20264
Oct 17, 20264
Oct 16, 20264
Oct 15, 20264
Oct 14, 20264
Oct 13, 20264
Oct 12, 20264
Oct 11, 20264
Oct 10, 20264
Oct 9, 20264
Oct 8, 20264
Oct 7, 20264
Oct 6, 20264
Oct 5, 20264
Oct 4, 20264
Oct 3, 20264

Map

Where Bloomberg's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 520G across 4 exchanges.

United States DE-CIX New York New York, United States 206.82.104.159
206.82.104.200
2 × 100G 2 routes PeeringDB only
United States Equinix New York New York, United States 198.32.118.36
198.32.118.43
2 × 100G PeeringDB
United Kingdom LINX LON1 London, United Kingdom 195.66.227.137 100G Up, 0 routes Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs
South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa 196.60.11.65
196.60.11.66
2 × 10G 1 routes Both IPv6 not in PeeringDB

Exchanges in its buildings that it isn't on (8)

These exchanges have a switch in a facility where Bloomberg lists itself in PeeringDB, but don't have Bloomberg as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.

Facilities (2)

The buildings Bloomberg lists in PeeringDB, and how many of the exchanges in each it's on.

United States Equinix NY2/NY4/NY5/NY6 - New York, SecaucusSecaucus 2 of 9
United States 165 Halsey Meet-Me RoomNewark 1 of 5