Live data from Hacker News

Cloudflare Traffic Manager

cloudflare.com

21–28 of 28 posts

Re: Cloudflare Traffic Manager

#21
It is shocking how many sites now use CloudFlare, I have recently switched ISPs and aparently my new ISP is SPAMMER and BOT heaven so almost every site I go to asks me to complete the Im Not A Robot Cloudflare reCapture. Really makes the experience suck.

Re: Cloudflare Traffic Manager

#22
post #14
post #8

Earlier quoted context omitted.

Because Cloudflare uses Anycast there is no change in the public IP address for a request that hits us. It will be routed to the nearest data center (of which we now have 100 cities covered globally). The Traffic Manager product controls how that traffic is the routed to the origin server (if the request could not be served from cache). As the active monitoring is performed from each location separately the Traffic M…

Somewhat off topic, but since CloudFlare keeps mentioning "routing the nearest data center" as one of its benefits... I have a number of clients near ICN (Seoul) who have been happy with CloudFlare for some time, but now the vast majority of their users are being routed through LAX. Not Tokyo, nor Osaka, nor any of your other locations throughout East Asia, but LAX all the way across the Pacific Ocean! This detour ad…

It doesn't have anything to do with how much they're paying (if Cloudflare uses the same network for all customers). Most likely, an Asian IP transit provider found a peer in an IX in LA and decided it was better to "cold potato" the data over there than deliver it to a nearby connection. Or it decided to de-peer for some stupid reason, or a route became "AS best path" to LA despite being actually worse in a way BGP can't figure out, et cetera.

Sometimes you can fix this with BGP communities, sometimes you have no control over it and are basically screwed unless you find another transit option that works better for everyone.

I've been building an Anycast network all week. Right now my problem is Australia. I make Sydney work better by peering and half the world starts best path routing to it. Debugging these problems is really tricky, particularly in Asia/Pacific, which is full of expensive submarine cables and, frankly, crappy communication monopolies that love to fight with eachother over peering.

Basically you need to get a contact to their NOC team and get them to check the BGP routes for those customers. I have no idea how they diagnose, but I myself would ask for some traceroute -A yoursite.com outputs from the people with the weird routing and go from there. Don't expect overnight results, the fix may require another transit hookup or peering agreement.

Re: Cloudflare Traffic Manager

#23

It is shocking how many sites now use CloudFlare, I have recently switched ISPs and aparently my new ISP is SPAMMER and BOT heaven so almost every site I go to asks me to complete the Im Not A Robot Cloudflare reCapture. Really makes the experience suck.

what else would you use instead of CloudFlare?

Re: Cloudflare Traffic Manager

#24

It is shocking how many sites now use CloudFlare, I have recently switched ISPs and aparently my new ISP is SPAMMER and BOT heaven so almost every site I go to asks me to complete the Im Not A Robot Cloudflare reCapture. Really makes the experience suck.

what else would you use instead of CloudFlare?

If I was operating a site? I dont think there is anything comparable at the free cost. But what you can do is turn the sensitivity if the captcha challenge down to 'Essentially Off' as detailed here https://support.cloudflare.com/hc/en-us/articles/200170096-H... the default setting seems to be way too quick to throw up a captcha.

Re: Cloudflare Traffic Manager

#25
post #14

Earlier quoted context omitted.

Somewhat off topic, but since CloudFlare keeps mentioning "routing the nearest data center" as one of its benefits... I have a number of clients near ICN (Seoul) who have been happy with CloudFlare for some time, but now the vast majority of their users are being routed through LAX. Not Tokyo, nor Osaka, nor any of your other locations throughout East Asia, but LAX all the way across the Pacific Ocean! This detour ad…

That experience with support doesn't sound right at all. Please email jgc @ cloudflare so I can follow up with you on this.

This is definitely correct. Every Cloudflare pro plan site I know of now routes to LAX for South Korean users. For business sites, going over a certain amount of traffic, they also route to LAX for South Korean users.

I also have confirmed with Cloudflare support, that sites going over a certain amount of traffic have to upgrade to Business -> Enterprise plan to keep South Korean users to route to ICN (Seoul). This is causing huge continous performance problems for nearly all Cloudflare sites in South Korea.

http://www.todayhumor.co.kr/cdn-cgi/trace http://www.ilbe.com/cdn-cgi/trace http://www.issuein.com/cdn-cgi/trace

All show loc=KR, while using a slow LAX colocation. The first two from what I know, are business plan sites.

Re: Cloudflare Traffic Manager

#26
post #14

Earlier quoted context omitted.

Somewhat off topic, but since CloudFlare keeps mentioning "routing the nearest data center" as one of its benefits... I have a number of clients near ICN (Seoul) who have been happy with CloudFlare for some time, but now the vast majority of their users are being routed through LAX. Not Tokyo, nor Osaka, nor any of your other locations throughout East Asia, but LAX all the way across the Pacific Ocean! This detour ad…

It doesn't have anything to do with how much they're paying (if Cloudflare uses the same network for all customers). Most likely, an Asian IP transit provider found a peer in an IX in LA and decided it was better to "cold potato" the data over there than deliver it to a nearby connection. Or it decided to de-peer for some stupid reason, or a route became "AS best path" to LA despite being actually worse in a way BGP…

Yep, I understand the difficulties. It's bad enough trying to get decent international transit in these parts as a local customer.

But if the matter really is beyond CloudFlare's control, their support should not be encouraging people to upgrade to a plan that costs 10x as much.

Re: Cloudflare Traffic Manager

#27

It is shocking how many sites now use CloudFlare, I have recently switched ISPs and aparently my new ISP is SPAMMER and BOT heaven so almost every site I go to asks me to complete the Im Not A Robot Cloudflare reCapture. Really makes the experience suck.

what else would you use instead of CloudFlare?

The main competitor is Akamai. Have fun with the sales team.

Re: Cloudflare Traffic Manager

#28
post #14
post #8

Earlier quoted context omitted.

Because Cloudflare uses Anycast there is no change in the public IP address for a request that hits us. It will be routed to the nearest data center (of which we now have 100 cities covered globally). The Traffic Manager product controls how that traffic is the routed to the origin server (if the request could not be served from cache). As the active monitoring is performed from each location separately the Traffic M…

Somewhat off topic, but since CloudFlare keeps mentioning "routing the nearest data center" as one of its benefits... I have a number of clients near ICN (Seoul) who have been happy with CloudFlare for some time, but now the vast majority of their users are being routed through LAX. Not Tokyo, nor Osaka, nor any of your other locations throughout East Asia, but LAX all the way across the Pacific Ocean! This detour ad…

I saw the same thing with China. We have something hosted on IBM Softlayer in HKG that takes a detour through LA. Apparently all China traffic for Cloudflare must go through LA and that's just now China works, we were told.
Post reply on HN