ixreport

John Carlo Olideles

AS200879 · JCOlideles

6Exchanges, of which 1 VIX
1On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Educational/ResearchType
OpenPeering policy
6Using the route servers
2To fix in PeeringDB
0Facilities in PeeringDB

Tools: Where can I peer with John Carlo Olideles? · Where should John Carlo Olideles peer next? · Compare John Carlo Olideles with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

2 things to fix in John Carlo Olideles's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-11-19 12:40 UTC.

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

Add these exchanges (1)

On the exchange's own member list, but not in John Carlo Olideles's PeeringDB record. Add one entry per connection with these values.

  1. Switzerland 4b42 Internet Exchange Point Zurich, Switzerland · PeeringDB 2447From its IX-F export and website members list
    IPv4–
    IPv62001:7f8:d0::3:10af:1
    SpeedNot published
    RS peerYes

Correct these entries (1)

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. Netherlands INTERIX Amsterdam, Netherlands · PeeringDB 3990
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDBnone185.1.184.238
    • In the entry with IPv6 2001:7f8:134::ee: set IPv4 to 185.1.184.238 (now empty).

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

Exchanges over time

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

In the last 30 days John Carlo Olideles joined 0 exchanges and left 1. Growing networks

Left

Map

Where John Carlo Olideles'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 104G, at the 5 of 6 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Switzerland 4b42 Internet Exchange Point Zurich, Switzerland 2001:7f8:d0::3:10af:1 Yes Not in PeeringDB
United States EVIXVIX Fremont, United States 2602:fed2:fff:ffff::46 1G 1 routes Both
United States F4IX MCI Kansas City, United States 2602:fa3d:f4:1::a9 1G Yes Both
Switzerland FogIXP Avers, Switzerland 2001:7f8:ca:1:0:20:879:1 1G Yes Both
Netherlands INTERIX Amsterdam, Netherlands 2001:7f8:134::ee 100G 2 routes Both IPv4 not in PeeringDB
Canada ONIX Toronto, Canada 2001:504:125:e1::aae 1G Yes Both

John Carlo Olideles lists no facilities in PeeringDB.

Recent changes Search them

  • Nov 8, 2026 [PDB] AS200879 John Carlo Olideles left Protocol 7 IX - Hong Kong