<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Users with Geolocation Issues - Services reporting as Singapore in Integration and Testing</title>
    <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Users-with-Geolocation-Issues-Services-reporting-as-Singapore/m-p/73870#M45814</link>
    <description>&lt;P&gt;On Friday (10/30), our relay responses stopped processing as our server's firewall has geolocation filters on.&amp;nbsp; Apparently, (at least) the &lt;A href="https://support.authorize.net/s/article/Authorize-Net-Domains-and-IP-Addresses" target="_self"&gt;Relay IPs&lt;/A&gt; are now being tagged as Singapore in at least a couple geolocation databases.&amp;nbsp; We got those white-listed.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We're also aware of at least one client user who couldn't reach the hosted payment gateway.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Support wasn't able to give much more to go on other than they're aware of the issue and investigating; turn off geolocation filtering.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Obviously, independent end-users outside of our network we can't help so much.&amp;nbsp; Outside of corporate environments, hopefully the amount of end users affected by geolocation will be low.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I didn't see anything logged, so&amp;nbsp; thought I'd start something.&amp;nbsp; If anyone has any experiences to add, please share!&lt;/P&gt;</description>
    <pubDate>Thu, 05 Nov 2020 13:44:21 GMT</pubDate>
    <dc:creator>jhoven</dc:creator>
    <dc:date>2020-11-05T13:44:21Z</dc:date>
    <item>
      <title>Users with Geolocation Issues - Services reporting as Singapore</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Users-with-Geolocation-Issues-Services-reporting-as-Singapore/m-p/73870#M45814</link>
      <description>&lt;P&gt;On Friday (10/30), our relay responses stopped processing as our server's firewall has geolocation filters on.&amp;nbsp; Apparently, (at least) the &lt;A href="https://support.authorize.net/s/article/Authorize-Net-Domains-and-IP-Addresses" target="_self"&gt;Relay IPs&lt;/A&gt; are now being tagged as Singapore in at least a couple geolocation databases.&amp;nbsp; We got those white-listed.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We're also aware of at least one client user who couldn't reach the hosted payment gateway.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Support wasn't able to give much more to go on other than they're aware of the issue and investigating; turn off geolocation filtering.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Obviously, independent end-users outside of our network we can't help so much.&amp;nbsp; Outside of corporate environments, hopefully the amount of end users affected by geolocation will be low.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I didn't see anything logged, so&amp;nbsp; thought I'd start something.&amp;nbsp; If anyone has any experiences to add, please share!&lt;/P&gt;</description>
      <pubDate>Thu, 05 Nov 2020 13:44:21 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/Users-with-Geolocation-Issues-Services-reporting-as-Singapore/m-p/73870#M45814</guid>
      <dc:creator>jhoven</dc:creator>
      <dc:date>2020-11-05T13:44:21Z</dc:date>
    </item>
  </channel>
</rss>

