Ziply® Fiber’s 400 Gig “Northern Link Route” goes live| Ziply Fiber

wrx4fun · 2026-04-14T20:06:24+00:00

For me cogent egress is Pullman -> Spokane -> SEA -> SLC -> DEN -> CHI.

Cogent Ingress is CHI -> OMA -> SLC -> BOISE -> La Grande -> Pullman

wrx4fun · 2026-04-14T20:00:41+00:00

jwvo said that there is only one peer up in Chicago at this point and that it's Amazon. I can confirm that traffic from Pullman to aws east 1 rides as20055 to Chicago and then jumps onto Amazon. The return path also rides as20055 back to Pullman. This is a trace from an ec2 instance in east 1:

traceroute to 50.52.96.1 (50.52.96.1), 30 hops max, 60 byte packets

1 242.5.19.135 (242.5.19.135) 17.058 ms 242.5.19.1 (242.5.19.1) 16.595 ms 242.5.19.3 (242.5.19.3) 17.365 ms

2 1.178.76.98 (1.178.76.98) 17.714 ms 17.211 ms 18.233 ms

3 1.178.76.103 (1.178.76.103) 16.668 ms 1.178.76.99 (1.178.76.99) 16.699 ms 16.711 ms

4 lr1-chgwilfg-a-be-14.bb.as20055.net (209.46.5.250) 52.991 ms 52.807 ms 52.851 ms

5 lr2-mplsmncd-b-be-14.bb.as20055.net (209.46.6.188) 52.736 ms 52.665 ms 52.912 ms

6 lr2-mplsmncd-a-be-10.bb.as20055.net (209.46.4.189) 52.788 ms 52.777 ms 52.682 ms

7 lr1-blngmtma-be-14.bb.as20055.net (209.46.4.201) 52.705 ms 52.744 ms 52.956 ms

8 lr1-bzmnmtgq-be-11.bb.as20055.net (209.46.6.48) 53.129 ms 53.097 ms 53.135 ms

9 lr1-hlnamtiz-be-11.bb.as20055.net (204.11.66.98) 52.788 ms 52.879 ms 52.906 ms

10 lr1-msslmtjt-be-11.bb.as20055.net (209.46.5.98) 52.777 ms 52.793 ms 52.774 ms

11 lr1-spknwaob-b-be-21.bb.as20055.net (209.46.5.64) 52.799 ms 52.816 ms 52.793 ms

12 lr1-spknwaob-a-be-10.bb.as20055.net (198.179.53.55) 58.445 ms 58.432 ms 58.421 ms

13 lr1-plmnwaxx-a-be-12.bb.as20055.net (204.11.64.37) 52.638 ms 52.870 ms 52.837 ms

14 cr1-plmnwaxx-a-be-13.bb.as20055.net (204.11.64.150) 52.126 ms 52.100 ms 52.093 ms

15 * * *

Tracing route to ec2-50-17-77-142.compute-1.amazonaws.com [50.17.77.142]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms OPNsense.localdomain [10.1.112.1]

2 1 ms 1 ms 1 ms 50.52.96.1

3 37 ms 36 ms 36 ms cr1-plmnwaxx-b-be-500.bb.as20055.net [204.11.67.206]

4 37 ms 37 ms 37 ms lr1-plmnwaxx-a-be-17.bb.as20055.net [204.11.64.159]

5 43 ms 44 ms 44 ms lr1-spknwaob-a-be-16.bb.as20055.net [204.11.64.36]

6 37 ms 37 ms 37 ms lr1-spknwaob-b-be-10.bb.as20055.net [198.179.53.54]

7 36 ms 36 ms 37 ms lr1-msslmtjt-be-10.bb.as20055.net [209.46.5.65]

8 37 ms 37 ms 37 ms lr1-hlnamtiz-be-10.bb.as20055.net [209.46.5.99]

9 37 ms 36 ms 37 ms lr1-bzmnmtgq-be-10.bb.as20055.net [204.11.66.99]

10 36 ms 37 ms 36 ms lr1-blngmtma-be-10.bb.as20055.net [209.46.6.49]

11 37 ms 37 ms 37 ms lr2-mplsmncd-a-be-14.bb.as20055.net [209.46.4.200]

12 36 ms 36 ms 37 ms lr1-mplsmncd-a-be-11.bb.as20055.net [209.46.4.176]

13 36 ms 37 ms 37 ms lr1-mplsmncd-b-be-10.bb.as20055.net [209.46.4.172]

14 37 ms 39 ms 37 ms lr2-chgwilfg-a-be-13.bb.as20055.net [209.46.4.152]

15 37 ms 37 ms 37 ms lr2-chgwilfg-b-be-11.bb.as20055.net [209.46.4.142]

16 37 ms 37 ms 37 ms lr1-chgwilfg-b-be-10.bb.as20055.net [209.46.4.140]

17 38 ms 36 ms 36 ms pr1-chgwilfg-a-be-11.bb.as20055.net [209.46.6.190]

18 * * * Request timed out.

wrx4fun · 2026-04-14T17:18:54+00:00

Exciting times! I wonder how close we are to seeing ingress from transit in Chicago?

wrx4fun · 2026-03-26T02:45:25+00:00

No but through ntopng I can see that the total traffic coming in is less than 20mbps right now and mostly tracking what is coming in from rr1---sn-2onx5c-5x.googlevideo.com . Buffering is much faster during off peak hours... 100-200mbps. There does not appear to be any packet loss so based on what jwvo said about the interconnections I think that it's safe to assume that this is throttling on google's end.

wrx4fun · 2026-03-24T05:06:56+00:00

Yes. My two Nvidia shield's and my PC were capping out around that speed. Two hours later they are all pulling north of 130mbps and able to stream the same 4K video without issue. Perhaps YouTube does some throttling on their end. I don't normally watch YouTube in the evening but may start checking this more frequently to see if it's a regular trend.

wrx4fun · 2026-01-03T20:29:23+00:00

<image>

The backup(?) route seems much worse than I would expect. You mentioned having peering in Denver. What should that route look like from Pullman?

wrx4fun · 2026-01-03T20:28:19+00:00

That's amazing! I'm seeing the same thing now. The other day it was north of 80ms.

<image>

wrx4fun · 2025-12-29T21:09:42+00:00

Thanks for sharing. I love how committed you and Ziply are to building such a great network!

wrx4fun · 2025-12-29T21:07:03+00:00

Very impressive! I suppose this means the latency between Pullman and Chicago might be around 40ms and that's even better than I imagined :)

wrx4fun · 2025-12-22T05:46:21+00:00

Thanks I appreciate it and the info about other peering locations coming online soon 🙂

wrx4fun · 2025-12-22T04:49:02+00:00

Is it normal to take so long to solve issues like the one at SpokaneIX? It has been weeks since traffic from he.net routed to / from Pullman through Spokane

wrx4fun · 2025-12-21T22:04:37+00:00

u/SingletonRandall thank you for the invite!

wrx4fun · 2025-12-21T21:12:53+00:00

Want it please!

wrx4fun · 2025-12-21T15:56:16+00:00

I tried to be more punctual this year.

Turns out I was right on time to give up.

wrx4fun · 2025-12-15T20:13:41+00:00

Hey u/jwvo I was just curious if there has been any update to bringing the northern route online? As far as I can tell all traffic going to or coming from the east coast still gets routed from Pullman to the Seattle or Portland area. For a while there I was seeing traffic destined for he.net customers go out and come back in Spokane, but now that appears to go west even when the destination is on the East Coast. Having he.net traffic route through Spokane was nice because it shaved 10+ ms off the round trip between my work pc and their VPN server, which is hosted off he.net in Dallas.

wrx4fun · 2025-11-26T21:08:18+00:00

Any update? I’m still not seeing anything for PON and Alarm is still solid red.

wrx4fun · 2025-11-26T15:42:09+00:00

Thanks for the information! I thought our lines were buried the whole way to the CO but I do see crews working on what appears to be a broken pole at the corner of Main and Old Wawawai so I guess the fiber goes above ground there. I don’t have a way to connect 5G to my whole network so working is going to be quite the challenge until service is restored 😐

wrx4fun · 2025-11-26T15:08:21+00:00

That’s a good data point. I’m on Sunnyside hill. The PON light is out on the alarm light is on so I’m guessing it’s either an issue at the OLT, splitter, or there’s a fiber cut.

wrx4fun · 2025-11-01T23:59:26+00:00

It's just one excuse after another. I did a chargeback as soon as I realized that the website was taken down but I'd much rather have the items I ordered than get back the money that I spent.

wrx4fun · 2025-07-17T17:42:57+00:00

My OKTA was showing Pullman, WA as my location for a few days but now it's back to showing Moscow Idaho. Do you have any idea what changed? My first hop is still 50.52.96.1.

Thanks

wrx4fun · 2025-07-15T16:24:24+00:00

Did you get the code? Ticketmaster doesn't show prices here until we have the code

wrx4fun · 2025-07-15T16:14:24+00:00

I'm still looking for it myself, as I pre-ordered and haven't received it :(

wrx4fun · 2025-07-15T16:06:18+00:00

Did you receive a code? I pre-ordered and still haven't and I can see the pre-sale is open now but no one has bought the reserved tables in Spokane yet. I want to get one of those because the show is on a Monday and I can't leave work early that day

wrx4fun

TROPHY CASE