Skip to main content

pops

points of presence

Toronto

  • you can expect 2602:fc26:6::/48, 2602:fc26:7::/48, and 2602:fc26:a::/48 to be announced to the dfz from toronto, with 2602:fc26::/48 and 45.41.37.0/24 announced only to private or bilat peers.
  • i have a very open peering policy for my toronto pop and i am willing to peer through a mutual exchange or through a tunnel (vxlan preferred).
  • tor01 is located with the upstream, GoCodeIt hosted on the cloud provider, Xenyth at equinix tr2. tor02 is an oracle cloud vm with sub-ms latency to tor01.

New Jersey

  • you can expect 45.41.37.0/24, 2602:fc26::/48, 2602:fc26:1::/48, and 2602:fc26:a::/48 to be announced to the dfz from new jersey.
  • i do have a selective policy for who is able to peer with my new jersey/new york pop due to the fact that i run a production connection off of this.
  • my new jersey pop obtains transit over a gre tunnel to upstream Global Secure Layer, also featuring a backup link through GoCodeIt and connections to my other pops.
  • you can view a diagram of the network layout of this pop here.

London

  • you can expect 2602:fc26:14::/48 to be announced to the dfz from london.
  • i have a very open peering policy for my london pop and am willing to peer on Rapid-IX or through a tunnel (vxlan preferred).
  • my london peering router is located with the upstream, Inferno Communications, who i love very much.

Netherlands

  • you can expect 2602:fc26:4::/48 to be announced to the dfz from netherlands.
  • i have a very open peering policy for my netherlands pop and am willing to peer through a tunnel (vxlan preferred).
  • my netherlands peering router is located with the upstream, Bakker IT.

Fremont

  • you can expect 2602:fc26:2::/48 to be announced to the dfz from fremont.
  • i have a very open peering policy for my fremont pop and am willing to peer through a tunnel (vxlan preferred).
  • my fremont peering router is located with the upstream, Eric at hurricane electric's fmt2 data center.

Kansas City

  • you can expect 2602:fc26:8::/48 to be announced to the dfz from mci01 with 2602:fc26:12::/48 from mci02.
  • i have a very open peering policy for my kansas city pop and am willing to peer through a tunnel (vxlan preferred).
  • my mci01 peering router is located with the upstream, Fosshost. my mci02 peering router is located with the upstream, Misaka Network.