Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Route Leak Impacting Cloudflare

cloudflarestatus.com

Post reply on HN
Print view View original

91–100 of 164 posts

Re: Route Leak Impacting Cloudflare

#91

Post by veswdev »

lordelph wrote: post #69

We've been evaluating Cloudflare mainly for doing failovers faster than DNS. This morning I ran some tests to generate graphs to show the typical delay incurred in preparation for a show-and-tell with some key people. I started seeing delays of up to 300 seconds! At best there was a 1 second delay. I wondered if I was going to have present "Why we've decided not to go with Cloudflare!" Any longtime Cloudflare users c…

Longtime Cloudflare user. This isn't specific to Cloudflare, but common sense would be to always have a backup. For example, my sites I've got Cloudflare in front, but in the background I'm caching all my content and pushing to BunnyCDN, so if I need to fallover, I can safely fallover out of the network into a live cache (each request I re-populate cache in background job).

It's saved me lots of time and energy.

Re: Route Leak Impacting Cloudflare

#94

Post by nikisweeting »

shacharz wrote: post #84
shacharz wrote: post #78

Hi Shachar from Peer5 here, we're operating a MultiCDN. Cloudflare is actually one of the best performing CDNs. All CDNs encounter issues small to big - that's why using multiple providers and intelligently routing between them is critical for high resilience.

Right now we're seeing issues in the following ASNs: 9,541 . 59,257 . 38,264 . 132,165 . 23,888 . 55,714 . 45,773 . 45,669 . 9,260 . 58,895 . 17,557 . 38,547 . 38,193 . 135,407 . 23,966 . 7,590 . 136,525 .

Are you seeing ASN 396531 as the original leaker?

Re: Route Leak Impacting Cloudflare

#95

Post by jakejarvis »

has-ams wrote: post #79
srushtika wrote: post #12

Earlier quoted context omitted.

Doesn't seem so http://www.doesitusecloudflare.com/?url=https%3A%2F%2Fnews.y...

http://www.doesitusecloudflare.com/?url=cloudflare.com

I just put in my own Cloudflare-enabled website and it came back negative as well.

Re: Route Leak Impacting Cloudflare

#96

Post by CreepGin »

lordelph wrote: post #69

We've been evaluating Cloudflare mainly for doing failovers faster than DNS. This morning I ran some tests to generate graphs to show the typical delay incurred in preparation for a show-and-tell with some key people. I started seeing delays of up to 300 seconds! At best there was a 1 second delay. I wondered if I was going to have present "Why we've decided not to go with Cloudflare!" Any longtime Cloudflare users c…

> Any longtime Cloudflare users comment on how rare an event this sort of thing is?

I've been a Cloudflare user for 7+ years and a Cloudflare Enterprise user for 2 years. Before joining Enterprise, Cloudflare would suffer some kind of global or localized network outage (that impacted our operation) about once or twice a year. Most localized ones don't really get reflected on the status page properly. After joining Enterprise, this is actually the first observed incident we've encountered so far.

Though it might not be a Cloudflare-only thing because funny thing is... Verizon Fios is also down for everyone I've talked to this morning.

Re: Route Leak Impacting Cloudflare

#98

Post by nikisweeting »

There's one thing I don't understand about this all, it looks like Allegheny Technologies Incorporated (AS396531, a suspected original leaker) was originally announcing 192.92.159.0/24.

How the heck did their peers not manage to filter a sudden announcement for a range big enough that it managed to snag both 8.8.8.8 and 1.1.1.1. Do upstreams really allow a tiny /24 AS to randomly announce a /4 and get away with it? Or am I misunderstanding something fundamental about how BGP routes are allowed to propagate?

Re: Route Leak Impacting Cloudflare

#100

Post by toymachine »

nikisweeting wrote: post #67
jgrahamc wrote: post #56

Earlier quoted context omitted.

We're definitely still working on it. Sorry you're affected by this. We're talking with the network providers involved. If anyone from the Verizon NOC is online... call me!

Confirming widespread FiOS issues in NYC as well, not limited to CloudFlare IPs.

Same FIOS issues for me. Any idea how this is all related?
Post reply on HN