ixreport

zfs.rent

AS38439

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

Tools: Where can I peer with zfs.rent? · Where should zfs.rent peer next? · Compare zfs.rent with another network

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

PeeringDB fix list Printable page · CSV

One thing to fix in zfs.rent's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-11-19 12:40 UTC.

Make the changes on zfs.rent'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 zfs.rent's PeeringDB record. Add one entry per connection with these values.

  1. United States FCIX Fremont, United States · PeeringDB 2163From its website members list
    IPv4206.80.238.193
    IPv62001:504:91::193
    SpeedNot published
    RS peerNot published

Exchanges over time

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

Map

Where zfs.rent'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 11G, at the 2 of 3 exchanges with a speed in PeeringDB or the exchange's IX-F export.

United States FCIX Fremont, United States 206.80.238.193 2001:504:91::193 Not in PeeringDB
United States FREMIX Fremont, United States 149.112.29.134 2001:504:125:e0::134 1G Yes Both
United States SFMIX San Francisco, United States 206.197.187.102 2001:504:30::ba03:8439:1 10G Yes Both

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

These exchanges have a switch in a facility where zfs.rent lists itself in PeeringDB, but don't have zfs.rent 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.

United States EVIXFremont, United States 227 Hurricane Electric Fremont 2
Puerto Rico PR-IXSan Juan, Puerto Rico 33 Hurricane Electric Fremont 2
United States ARIXFremont, Portland, Flagstaff, United States 22 Hurricane Electric Fremont 2
United States Lambda-IXFremont, United States 22 Hurricane Electric Fremont 2
United States MegaIX Bay AreaSan Francisco, United States 21 Hurricane Electric Fremont 2
United States Zero Internet eXchange San JoseSan Jose, United States 15 Hurricane Electric Fremont 2
United States DACS-IX WestSilicon Valley, United States 14 Hurricane Electric Fremont 2
United States Ninja-IX Bay AreaNorthern California, United States 6 Hurricane Electric Fremont 2
Australia ixFabricGlobal, Australia 2 Hurricane Electric Fremont 2
Facilities (1)

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

United States Hurricane Electric Fremont 2Fremont 3 of 12