Fastly Geolocation based Syslog



I wanted to get my syslog messages delivered to a geographically closer syslog server. Hence i configured route 53 with multiple geolocations with same name to multiple IP mapping. I have verified nslookup from different regions to see it gives me region specific ip for same domain.

But, then i realize that Fastly is not using geographically separate addresses in source IP of syslog messages. All my traffic is hitting US syslog server though my X-Served-By shows “SIN” in the response. Just wanted to know if i am missing something or is there a solution for it.



Hi Michael

You’re correct, in that our logging servers aren’t globally distributed. They’re currently only in a few places around the globe, so what you’re seeing is expected.