Fun Stuff

On The Map with J Root

We’re on the map with J Root. Yep, that’s us in Reno.

j-root

Access to J root is available through peering at TahoeIX and automatically to Roller Network customers since Rollernet already peers.

Improvements Through IX Peering

Roller Network is one of the first participants of the Tahoe Internet Exchange, or TahoeIX. We announce our routes and our customer’s routes to the exchange, and accept all routes from the exchange. This morning TahoeIX welcomed Packet Clearing House to the peering fabric. While we’re still working turning up some direct peering sessions with PCH, their peering with the TahoeIX IPv4 route server is already up. We’ll receive routes directly and through the common route server.

Why peering? Here’s a perfect example of an improvement.

Traffic to a peered DNS root now looks like this:

$ mtr e.root-servers.net -4 -c 2 -r
HOST: whiskers                    Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- office-gw.rollernet.net    0.0%     2    0.7   0.6   0.6   0.7   0.1
  2.|-- as42.tahoeix.net           0.0%     2    0.6   0.6   0.5   0.6   0.1
  3.|-- e.root-servers.net         0.0%     2    0.9   0.8   0.7   0.9   0.1

While traffic to a DNS root without peering takes the long, scenic route:

$ mtr b.root-servers.net -4 -c 2 -r
HOST: whiskers                    Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- office-gw.rollernet.net    0.0%     2    0.4   0.4   0.4   0.5   0.1
  2.|-- core1-gi3-3.rollernet.net  0.0%     2    0.6   0.6   0.6   0.6   0.0
  3.|-- border0-gi0-1.rollernet.n  0.0%     2    1.2   1.2   1.2   1.2   0.0
  4.|-- 12.116.94.237              0.0%     2   15.1  31.5  15.1  47.9  23.2
  5.|-- 12.122.160.30              0.0%     2   12.4  12.2  12.0  12.4   0.3
  6.|-- cr2.sffca.ip.att.net       0.0%     2   11.7  12.6  11.7  13.4   1.1
  7.|-- 12.122.149.137             0.0%     2   13.7  13.7  13.6  13.7   0.1
  8.|-- 192.205.37.58              0.0%     2   12.0  12.1  12.0  12.3   0.3
  9.|-- ae-9.r22.snjsca04.us.bb.g  0.0%     2   12.2  11.9  11.6  12.2   0.4
 10.|-- ae-7.r21.lsanca03.us.bb.g  0.0%     2   23.2  23.4  23.2  23.6   0.3
 11.|-- ae-2.r05.lsanca03.us.bb.g  0.0%     2   24.4  23.7  23.0  24.4   1.0
 12.|-- ntt-los-nettos-usc.ln.net  0.0%     2   23.9  23.6  23.3  23.9   0.4
 13.|-- isi-vlan2009.ln.net        0.0%     2   24.0  23.9  23.8  24.0   0.1
 14.|-- b.root-servers.net         0.0%     2   24.4  25.7  24.4  27.0   1.9

The improvement should be quite obvious.

UPDATE: More prefixes from Afilias were added this morning.

$ mtr -c 1 -r b2.org.afilias-nst.org -6
HOST: whiskers                    Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- 2607:fe70:0:beef::1        0.0%     1    0.5   0.5   0.5   0.5   0.0
  2.|-- as42.tahoeix.net           0.0%     1    0.8   0.8   0.8   0.8   0.0
  3.|-- b2.org.afilias-nst.org     0.0%     1    0.7   0.7   0.7   0.7   0.0

$ mtr -c 1 -r b2.org.afilias-nst.org -4
HOST: whiskers                    Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- office-gw.rollernet.net    0.0%     1    0.4   0.4   0.4   0.4   0.0
  2.|-- as42.tahoeix.net           0.0%     1    0.6   0.6   0.6   0.6   0.0
  3.|-- b2.org.afilias-nst.org     0.0%     1    1.0   1.0   1.0   1.0   0.0

Akamai is Coming to Reno

This isn’t entirely Roller Network related, but we felt compelled to mention that Akamai  (AS20940) will be peering with Northern Nevada’s first (and currently only) internet exchange: TahoeIX. It’s sort of related to Rollernet since we’re also peering and offering free GigE cross connects into the TahoeIX peering fabric to all colocation customers. This is an exciting time for us here in Reno, NV.

For more on the exchange visit www.tahoeix.org

Updated Facility Pictures

Did you know that the pictures we use on our website are real pictures from our facility, not stock photos? A couple of them were out of date so here’s the updated versions for the colocation services page.

Telco/MMR

telco2

STE1 UPS Room

upsroom2

 

Long Live Uptime

We sadly had to move the plug on this device to a new PDU this afternoon:

Lucent PortMaster PM-25 ComOS 3.9
System uptime is 1546 days 5 hours 55 minutes

This old PM25 is still used to provide some serial console services, but prior to replacing the PDU for the rack it’s in (and we did try to re-plug it as fast as we could on the off chance it would hold up briefly) it was the last thing that hadn’t been restarted for any reason since we opened our original colocation floor 1546 days ago, about 4.2 years.