{"__v":0,"_id":"581c5696bb096b0f002e6140","category":{"__v":3,"_id":"564621e10c30fb2100ba3818","pages":["564621e20c30fb2100ba381a","5646251ebb7ad50d00e9c5a3","56781253efb5ea0d005bbb1c"],"project":"564621e00c30fb2100ba3814","version":"564621e10c30fb2100ba3817","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2015-11-13T17:46:09.878Z","from_sync":false,"order":0,"slug":"documentation","title":"Documentation"},"parentDoc":null,"project":"564621e00c30fb2100ba3814","user":"564621d275c83f0d00e9d52d","version":{"__v":14,"_id":"564621e10c30fb2100ba3817","project":"564621e00c30fb2100ba3814","createdAt":"2015-11-13T17:46:09.275Z","releaseDate":"2015-11-13T17:46:09.275Z","categories":["564621e10c30fb2100ba3818","564624cf0c30fb2100ba3822","564628d69f3f550d00fa3db6","564dafeeda00e82b00ed601d","564daff8fc36dc3700882b95","564db0ccda00e82b00ed601f","564dcf87d3320b0d0028ca10","5661a6e436398e0d00f79566","568585153703ed1700e420b0","56858767d96a760d00545da6","56858d693703ed1700e420b2","56858d8d22c41b0d00e4666c","56859e9c009a8d0d00797130","5685a6453703ed1700e420d3"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2016-11-04T09:36:22.805Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":2,"body":"MobFox has data centers in multiple strategic locations in order to be near to demand sources to reduce latency to the minimum possible.\n\nThis means that MobFox is able to serve you ads from US, Europe and Asia with the lowest timeouts available per region.\n\nWhat this means for you as a **Publisher** or **DSP** is described below.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Available MobFox SSP locations\"\n}\n[/block]\n**Endpoints of our physical locations:**\n* **Virginia/US**: http://nvirginia-my.mobfox.com\n* **Tokyo/Japan**: http://tokyo-my.mobfox.com\n\nUse the above URLs for requesting ads from a specific data center in case you know that using that endpoint is the fastet option for you - do latency tests from your production servers to determine which endpoint to use.\n\nIn case you want MobFox to decide which data center to route to simply use: **http://my.mobfox.com**\nMobFox uses GeoDNS for routing you to the nearest data center.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Multi-location for Publishers\"\n}\n[/block]\n**Publishers integrating the MobFox SDK**\nNo special changes in your integration required. Geo based DNS will take care of routing your users to the nearest MobFox data center.\n\n**Publishers using their own server to make ad requests**\nYou should choose the endpoint with the lowest latency to your own server(s) in case the automatic routing is not in your interest. Please choose one of the endpoints from above.\n\nIn case you have multiple locations it might make sense to use different MobFox endpoints on your server(s) depending on your latency test results.\n\n**Publishers using client side mediation**\nPublishers using 3rd party SDKs should set the MobFox endpoint to http://my.mobfox.com to automatically get routed to the best data center.\n\n**Publishers using server side mediation on 3rd party ad networks**\nMake sure your 3rd party ad networks follow the recommendations in this document.\nIn case of doubt please use http://my.mobfox.com as the MobFox endpoint.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Multi-location for Demand Partners\"\n}\n[/block]\nPlease provide the **URLs of your endpoints** and state where they are physically located. MobFox will measure your latency from each data center and set you up in all date centers from which latency is good enough for productive use.\n\nMobFox endpoints: [see above](#available-mobfox-ssp-locations)\n\nMobFox does not provide IPs for whitelisting as MobFox server setup is hosted in a cloud environment and the IPs are changing constantly.","excerpt":"MobFox has data centers in multiple locations - what this means for you","slug":"multi-located-ssp","type":"basic","title":"Multi-located SSP"}

Multi-located SSP

MobFox has data centers in multiple locations - what this means for you

MobFox has data centers in multiple strategic locations in order to be near to demand sources to reduce latency to the minimum possible. This means that MobFox is able to serve you ads from US, Europe and Asia with the lowest timeouts available per region. What this means for you as a **Publisher** or **DSP** is described below. [block:api-header] { "type": "basic", "title": "Available MobFox SSP locations" } [/block] **Endpoints of our physical locations:** * **Virginia/US**: http://nvirginia-my.mobfox.com * **Tokyo/Japan**: http://tokyo-my.mobfox.com Use the above URLs for requesting ads from a specific data center in case you know that using that endpoint is the fastet option for you - do latency tests from your production servers to determine which endpoint to use. In case you want MobFox to decide which data center to route to simply use: **http://my.mobfox.com** MobFox uses GeoDNS for routing you to the nearest data center. [block:api-header] { "type": "basic", "title": "Multi-location for Publishers" } [/block] **Publishers integrating the MobFox SDK** No special changes in your integration required. Geo based DNS will take care of routing your users to the nearest MobFox data center. **Publishers using their own server to make ad requests** You should choose the endpoint with the lowest latency to your own server(s) in case the automatic routing is not in your interest. Please choose one of the endpoints from above. In case you have multiple locations it might make sense to use different MobFox endpoints on your server(s) depending on your latency test results. **Publishers using client side mediation** Publishers using 3rd party SDKs should set the MobFox endpoint to http://my.mobfox.com to automatically get routed to the best data center. **Publishers using server side mediation on 3rd party ad networks** Make sure your 3rd party ad networks follow the recommendations in this document. In case of doubt please use http://my.mobfox.com as the MobFox endpoint. [block:api-header] { "type": "basic", "title": "Multi-location for Demand Partners" } [/block] Please provide the **URLs of your endpoints** and state where they are physically located. MobFox will measure your latency from each data center and set you up in all date centers from which latency is good enough for productive use. MobFox endpoints: [see above](#available-mobfox-ssp-locations) MobFox does not provide IPs for whitelisting as MobFox server setup is hosted in a cloud environment and the IPs are changing constantly.