re: Apparently a lot of people having cloudfare issues this morning.

quote:

---

Anyone starting to think this is not a coincidence? This is the third major cloud type outage.

China, Russia, N Korea probing?

---

As somebody who knows little about this stuff other than as a user, my uneducated guess would be something having to do with all the shite they have to pile on their service to try to weed out bots.

The amount of extra Cloudflare clicks and captchas it takes just to surf the web has gone up exponentially in the last few years.

quote:

---

As somebody who knows little about this stuff other than as a user, my uneducated guess would be something having to do with all the shite they have to pile on their service to try to weed out bots.

The amount of extra Cloudflare clicks and captchas it takes just to surf the web has gone up exponentially in the last few years.

---

Toronto and Dallas hubs both affected intermittently. Could be a denial-of-service type of attack. Or a software updated that unexpectedly limited their capacity. Just speculation on my part.

quote:

---

Apparently a lot of people having cloudfare issues this morning.

---

Not be because I have no idea WTF that is.

Yep, several porn sites wouldn't load

Not even the thumbnails?

You can go a long way with a thumbnail and a title

quote:

---

A Cloudflare spokesperson told The Register that the incident began at 1120 UTC and was fully resolved at 1430. They said: "The root cause of the outage was a configuration file that is automatically generated to manage threat traffic. The file grew beyond an expected size of entries and triggered a crash in the software system that handles traffic for a number of Cloudflare's services.

"To be clear, there is no evidence that this was the result of an attack or caused by malicious activity.

---

When I was a UNIX sysadmin I recall there were files that would periodically consume all of the space in the file system and cause it to lock up.

If the file grew "beyond an expected size", either their monitoring system was not operating, the people responsible for reacting to the notifications were asleep at the wheel, or it grew too fast for them to respond.

The latter suggests an attack.

Again, just speculation on my part.

I don't expect them to ever admit the truth publicly. They aren't required to.

quote:

---

I don't expect them to ever admit the truth publicly. They aren't required to.

---

Something generic will end up in an SEC filing next quarter, since it may have a material impact on their financials.

But also take into account that they have to give the engineers of their customers enough information to be satisfied, and whatever message they convey has a 0.0% chance of not being leaked to the press.