Looking for someone on the Fastly peering team to reach out regarding peering on a couple mutual IXPs - sent an email to the peering contact as listed on PeeringDB and never heard back, and also have a few colleagues who have experienced the same issue.
Hi Peter,
Sorry you didn’t get a response.
I only just started at Fastly, but I can look / nudge the right person if you drop me an e-mail off-list with details.
Ian
Me too. Fastly has been promising me peering every year for the past five years.
They are just a few cabinets over, so it has been pretty frustrating.
Tom
We have sent them some inquiries in markets we are with no reply. Just figured they weren’t interested.
Justin Wilson
j2sw@mtin.net
justin@fd-ix.com
Https://www.fdi-ix.com
The PeeringDB contact info was very useful for us. Granted, we were pulling a substantial amount from them over transit, over 20gb at peak, so they have a huge incentive to peer with us. 
Hi folks - former Fastly VP here.
I’ve flagged this thread to my past colleagues who may not be on the list. Generally speaking, most routes from AS54113 were always available on any given IXP route-servers. Some additional anycast routes can be announced selectively via communities. Respecting the selective peering policy - bi-lats are provided for somewhat bigger traffic peers, and then of course PNI’s for the really big stuff. Some of this depends on serving capacity at any given POP.
Certainly, “big” is subjective, as is “worth it”. Nevertheless, there was (and I’m sure still is) mutual performance and cost incentive to peer everywhere that it makes sense, and where technically feasible to do so.
Hope you all get a reply in short order.
Cheers,
Ryan
Disclaimer: things may have changed - my message here is not authoritative on current policy posture. I am not replying on Fastly’s behalf.