There's also a lack of communication with the dev partners in general (e.g. the recent Service Worker issues). Building up a more robust partner program with (perhaps) a different support team could be really helpful.

Agreed. A lot of this is all standard now - even when I wrote about it circa 2013 [1]

[1] https://queue.acm.org/detail.cfm?id=2536492

See shakti.sh for downloads and some minimal .d (docs)

Includes new FFI interface. node.js , C and python. See (limited docs) https://shakti.sh/ffi/_.d

Oh man ... cantrilogy ... it was there the whole time. Absolutely going to steal that :)

Note this is part 1 of 2, 2nd part will be up later in the week

Actively impacting new tunnel registrations (we also had a number of tunnels fail). Logs include the status page.

Even though it’s a single metric point I like the comparison! It’s always fun to compare two web optimization companies. E.g Fastly and Cloudflare. https://crux.run/report?domain=www.Fastly.com https://crux.run/report?domain=www.Cloudflare.com

That’s helpful- and especially since we then directly strip it :/

This is EXACTLY why we moved this data into our own database for Crux.run. We took the JSON export of the Crux database and cleaned and loaded it into a database on a single server. E.g each of those queries are hitting a single box in us central

There’s some of that information in the docs : https://docs.crux.run/#/introduction?id

But yeah- BQ can get very expensive very quickly if miss step

Thanks for doing so!