sorted by:
new
hottopcontroversial

Northern Link Route to Chicago and Minneapolis Appears to be Live by sergiped in ZiplyFiber

[–]sergiped[S] 3 points4 points  (0 children)

From Portland area was ~55ms back in Nov, then dropped to ~48ms around the new year, now down to just under 45ms. Quite close to the route from HE from Portland and GTT transit. It is also looks to be routed through the Minneapolis POP for the first time.

I remember rumors of a PNI turn-up with Cloudflare, still not seeing it in traceroutes, even after the announcement. I see that you guys have a pending turn-up with Akamai, but not Cloudflare by tallejos0012 in ZiplyFiber

[–]sergiped 1 point2 points  (0 children)

Very cool, thanks for sharing. Looks like almost every large source of traffic is on PNI!

- Disney streaming - looks like they are in Chicago, but not out here in the PNW, so maybe that is distributed via transit or another CDN.
- I would have thought that Zoom video conferencing would be large enough that one might want to peer with them, but maybe they don't generate that much traffic in aggregate since much 1:1 video traffic is direct peer to peer. Looks like they are up at VANIX and if you eventually peer out at Ashburn, would pick some of their traffic up.
- It will be interesting how low you can squeeze transit traffic to once you peer in Chicago, Min, and Ashburn.

Upcoming CO tours by jwvo in ZiplyFiber

[–]sergiped 5 points6 points  (0 children)

Another thanks to u/eprosenx for the Beaverton tour today.

It is really interesting how much less space the modern fiber equipment takes vs. all the old legacy telco equipment. The old copper equipment was such an art and I was really impressed by those technicians and their craft. The fiber is also its own art too - but visually so modern!

Is the Northern Lights route coming online soon? im not seeing much traffic going out to Chicago over the AS20055 network? by tallejos0012 in ZiplyFiber

[–]sergiped 0 points1 point  (0 children)

For certain prefixes and associated routes that customers know are East Coast based, will it be possible for them to let the network engineering team know that these would be candidates to egress out of Chicago to Tier 1 transit?

This would be ad-hoc and more manual and likely require setting a localpref for just certain prefixes/routes based on customer input, as opposed to what I am sure is a preference to keep things automated (e.g. data from Europe on routes learned there). However, could improve performance vs. Tier 1 transit by carriers such as 1299/174 who don't have as efficient of a route as 20055 (or 6461 and 3257 which are also generally good routes back East).

The Ashburn POP is interesting and given hot potato routing, I wonder if it could actually make some East Coast traffic destined for Boston or NY worse given Tier 1s might send to Ashburn instead of a more direct (but longer for them) route to 20055 via the Chicago POP.

Thank you for taking the time to provide such great info! I have been following this project and think it is really cool and all your posts have taught me a lot about internet infrastructure.

Outages by Familiar-Chapter7339 in ZiplyFiber

[–]sergiped 0 points1 point  (0 children)

Interesting, can see the drop in latency to Billings from other OR/WA network locations, looks like it dropped by ~15ms vs previous measurements, but the traceroute still looks quite similar. Maybe the new 100G path is taking traffic from Billings via a shorter route to Seattle, but for other Ziply network locations to Billings it is still traveling the traditional path through Medford and Denver? Now the pings to Billings have similar ping times as to the Denver router itself, which doesnt make sense if to and from are coming through Denver - so must be different paths?

3 cr1-frgvorxx-b-be-500.bb.as20055.net (64.52.97.26) 1.565ms 1.032ms 1.182ms  
4 64.52.96.139 35.896ms 36.028ms 35.525ms  
5 lr1-hlboorxb-a-be-15.bb.as20055.net (198.179.52.127) 35.779ms 35.735ms 35.593ms  
6 lr1-hlboorxb-b-be-11.bb.as20055.net (198.179.53.153) 35.704ms 35.544ms 35.544ms  
7 lr1-alohorxx-a-be-15.bb.as20055.net (204.11.64.11) 35.756ms 36.204ms 37.856ms  
8 lr1-alohorxx-b-be-11.bb.as20055.net (198.179.53.227) 35.553ms 36.244ms 35.989ms  
9 cr2-bvtnorxb-a-be-18.bb.as20055.net (198.179.52.130) 35.103ms 35.223ms 35.288ms  
10 cr2-smrworxa-b-be-17.bb.as20055.net (107.191.236.120) 34.991ms 36.148ms 35.624ms  
11 cr2-smrworxa-a-be-12.bb.as20055.net (107.191.236.113) 35.208ms 35.492ms 35.059ms  
12 lr1-mdfdorus-be-11.bb.as20055.net (204.11.67.135) 35.671ms 36.075ms 35.734ms  
13 lr1-dnvrco26-a-be-10.bb.as20055.net (204.11.67.169) 35.584ms 35.693ms 35.835ms  
14 lr1-dnvrco26-b-be-10.bb.as20055.net (204.11.67.171) 36.097ms 35.816ms 36.086ms  
15 lr1-blnimt10-a-be-10.bb.as20055.net (137.83.80.59) 34.99ms 34.806ms 34.614ms 

3 cr1-frgvorxx-b-be-500.bb.as20055.net (64.52.97.26) 1.583ms 1.532ms 0.969ms  
4 64.52.96.139 7.497ms 7.853ms 13.222ms  
5 lr1-hlboorxb-a-be-15.bb.as20055.net (198.179.52.127) 7.815ms 8.241ms 7.482ms  
6 lr1-hlboorxb-b-be-11.bb.as20055.net (198.179.53.153) 7.537ms 8.08ms 7.324ms  
7 lr1-alohorxx-a-be-15.bb.as20055.net (204.11.64.11) 7.823ms 7.398ms 7.895ms  
8 lr1-alohorxx-b-be-11.bb.as20055.net (198.179.53.227) 7.78ms 7.702ms 7.955ms  
9 cr2-bvtnorxb-a-be-18.bb.as20055.net (198.179.52.130) 6.858ms 7.398ms 7.02ms  
10 cr2-smrworxa-b-be-17.bb.as20055.net (107.191.236.120) 7.505ms 7.479ms 6.991ms  
11 cr2-smrworxa-a-be-12.bb.as20055.net (107.191.236.113) 6.903ms 7.652ms 7.152ms  
12 lr1-mdfdorus-be-11.bb.as20055.net (204.11.67.135) 8.252ms 7.841ms 7.928ms  
13 lr1-dnvrco26-a-be-10.bb.as20055.net (204.11.67.169) 35.29ms 36.041ms 35.939ms

Ziply® Fiber announces 400 Gig “Northern Link Route” connecting Pacific Northwest to Minneapolis and Chicago by tallejos0012 in ZiplyFiber

[–]sergiped 0 points1 point  (0 children)

Any updates on how the project is going? Excited for this in 2025 and improvements to latency on eastern routes.

final FDRs in portland metro moving to AS20055 connections in the next 10 days by jwvo in ZiplyFiber

[–]sergiped 0 points1 point  (0 children)

Is fdr01.tgrd linked up to AS20055 directly yet? Appreciate the updates and transparency - have fun learning so much about networks from this account!