<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: arial,helvetica,sans-serif; font-size: 10pt; color: #000000'>For an industry (online gaming) with the most "sensitive" customers to latency, packet loss, throughput, etc., the online gaming industry is terrible at peering. There are a few shining examples of what you should do, but then the rest is just content with buying transit from one, two, three players and calling it a day.<br><br><div><span name="x"></span><br><br>-----<br>Mike Hammett<br>Intelligent Computing Solutions<br>http://www.ics-il.com<br><br>Midwest-IX<br>http://www.midwest-ix.com<span name="x"></span><br></div><br><hr id="zwchr"><div style="color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: </b>"Jose Luis Rodriguez" <jlrodriguez@gmail.com><br><b>To: </b>nanog@nanog.org<br><b>Sent: </b>Monday, March 22, 2021 9:13:46 PM<br><b>Subject: </b>Peering and Caching for Epic Games, Fortnite, et al<br><br><div dir="ltr">We run a healthy-sized ISP (say, 2.5M households, plus enterprise, etc ) and we really, REALLY want to make sure our users have an amazing experience when downloading the neverending Fortnite/Spacequest/Blizzard/DigDug updates that run down our pipes. Would love to hear from others about how they're peering and caching -- not having the level of success I'd want with the typical "aggregators" (they know who they are ) and would really like to link to the source even if it means trenching through the core of the Earth...<div><br></div><div>Would love pointers, names, or any leads, on or off list. </div><div><br></div><div>Thanks</div><div><br></div><div>Jose L. Rodriguez</div><div>CTO, Totalplay</div></div>
</div><br></div></body></html>