It is a large home with a large amount of devices

my hometown, Minneapolis, as 10G fiber to the home available from a local independent internet provider (ironically named "US Internet"). I am jealous.

I'm asking on their forum: https://discuss.newrelic.com/t/support-for-cloudflare-workers/125321

Any issues with workers currently? I've updated my script and the change works in the "Quick edit" only, it isn't propagated globally. I've waited a long time, so something seems wrong. Since it works in Quick edit, this isn't a settings based issue. (I've purged cache just in case, no change)

Ah, I see it on the status page now.

I am not totally sure here in Italy what it would cost. Vodafone I believe offers businesses FTTH services, it was listed at 12k€/month + tax. Not sure if it’s for 1Gbps or 10Gbps though. For sure it would be more expensive, at least upfront, if it were not available there already.

This worker downtime really shows that relying on a single service is dangerous 😕

😦

Seems to be a serious issue

Almost up...

Restored

Propagation is fast now too

On another news https://blog.cloudflare.com/cloudflare-acquires-linc/

FABulous 🙂

there are always critical services in the path, that is unavoidable. Ironically reducing the number is actually a good thing...

That's why I've chosen cloudflare, but that's not how clients see it.

Sorry about the downtime y'all. I'm not exactly clear what happened - but we generally have an engineer on call when issues like this arise. It looks like that person sorted this in the middle of the night

Hurray for that person 🥳

Would be interesting with a postmortem later

Idk if we will get one seems like it was a minor single person job. Most outages with a postmortem are resolved by a team when things go very wrong.

I'd consider this a very big issue, not being able to deploy to production can have serious consequences. Imagine someone deploy an issue that cause customer data loss, now no one can publish a fix for several hours.

But I don't expect one either

Workers didn’t go down though a small piece of it did and was resolved quickly. My current experience with workers has been you’ll need to access/update data with a third party API so the usefulness aside from a cheap React client host is limited to me.

Likewise if this ever happens you can disable workers API key to your internal API to minimize data loss

Your strawman is falling over...

My typical setup is: React client in workers > Python/Django API > PostgreSQL or Mongo Data Store

Depends entirely on the use-case of course

@User strawman for sure, I'm a control freak

@geelen welcome to the team buddy 🙂

🎸 GLEN so happy you're on the team. Welcome!