MattIPv4

Just ran into a bunch of my E2Es failing on innocuous POST requests. Really interested to know how Cloudflare managed to outright break POST requests going through them.

I can unfortunately report that these dots have not helped me in cars or trains; anything more than a few seconds looking at a screen during a journey will ensure I feel awful until I have an opportunity to sit or lie still for quite a while after. To be fair, even facing backwards on a train usually makes me sick rather rapidly.

Related: https://news.ycombinator.com/item?id=47824426

https://x.com/theo/status/2045862972342313374

I have reason to believe this is credible.

https://x.com/theo/status/2045870216555499636

Env vars marked as sensitive are safe. Ones NOT marked as sensitive should be rolled out of precaution

https://x.com/theo/status/2045871215705747965

Everything I know about this hack suggests it could happen to any host

https://x.com/DiffeKey/status/2045813085408051670

Vercel has reportedly been breached by ShinyHunters.

https://vercel.com/kb/bulletin/vercel-april-2026-security-in...

https://nitter.net/theo/status/2045862972342313374

Hitting 500s when trying to push branches and create PRs.

Related: A better streams API is possible for JavaScript: https://news.ycombinator.com/item?id=47180569

Are y'all aware your agent's name clashes with an established and rather popular streaming bot/tool, https://fossabot.com ?

Again... Unicorns when trying to view files or PRs, errors trying to leave comments or review things if they do load.

Looks like they've got a status page up now for PRs, separate from the earlier notifications one: https://www.githubstatus.com/incidents/smf24rvl67v9

Edit: Now acknowledging issues across GitHub as a whole, not just PRs.

Status page currently says the only issue is notification delays, but I have been getting a lot of Unicorn pages while trying to access PRs.

Edit: Looks like they've got a status page up now for PRs, separate from the earlier notifications one: https://www.githubstatus.com/incidents/smf24rvl67v9

Edit: Now acknowledging issues across GitHub as a whole, not just PRs.

https://github.com/google-gemini/gemini-cli/issues/16723 is even worse, GitHub shows `5195 remaining items` in the collapsed timeline.

Leaked data includes:

  - Name, Discord username, email + other contact details.
  - Limited payment information, including type + last four of cards.
  - IP addresses.
  - Messages and attachments sent via the customer service system.
  - Notably, any government ID provided to Discord.

No, the content felt incredibly outdated and I can’t say I gained any technical knowledge from it. The only skill it really taught me was how to write effective filler content to boost the word count on something.

While I do now have a CS degree, I was hired into a big tech company prior to having that degree based on my work in open-source. I'd been (and still am) an active contributor to some large web projects for a few years, prior to this company reaching out to hire me (projects were unrelated to what they do, FWIW).

I did then get my degree in my spare time while at that job, with my salary covering the costs of tuition, which was very nice. I see my degree as a backup, if for any reason an employer has a strict requirement for it or if I leave this field -- I expect my experience to be what gets me jobs as it stands today.

PoE is around 15w at 48v, PoE+ is 30w, and PoE++ is 60 or 100w

Likely due to a Cloudflare incident: https://www.cloudflarestatus.com/incidents/8m177km4m1c9

We just have a single table, with a column indicating if the job has been taken by a worker or not. Probably could get a bit more performance out of it by splitting into two tables, but it works as it is for now.

We process around 1 million events a day using a queue like this in Postgres, and have processed over 400 million events since the system this is used in went live. Only issue we've had was slow queries due to the table size, as we keep an archive of all the events processed, but some scheduled vacuums every so often kept that under control.

That's fair, I would agree that caching at either end would fix this. It just strikes me as odd that GitHub, the middle-man that's just providing CI runners, is the one under fire.

Why is GitHub the one under fire here? Users on GitHub are using GitHub Actions to build CI pipelines that build stuff, and happen to be pulling from GMP. That's not GitHub's problem that users are using their product in a legitimate manner, it seems to me it is GMP's problem that they can't handle traffic for artifacts from CI systems? It is noted the requests are identical, so would a modicum of caching in front of their origin not make this problem go away completely?

Just got an email from GitLab about a group I'm part of that has more than five users. The docs linked says "For existing namespaces, this limit is being rolled out gradually. Impacted users are notified in GitLab.com at least 60 days before the limit is applied.", however upon checking the group in GitLab, we are greeted by a big red box stating "Your top-level group [group] is over the 5 user limit and has been placed in a read-only state."

Loading github.com is returning a 500 for me currently, so seems like more than just issues/pull requests. Also seeing actions fail with 500s on assorted steps.

Pricing for them:

Blob: https://vercel.com/docs/storage/vercel-blob/usage-and-pricin...

KV: https://vercel.com/docs/storage/vercel-kv/usage-and-pricing

Postgres: https://vercel.com/docs/storage/vercel-postgres/usage-and-pr...

Cloudflare's R2 costs $0.36 per million read operations (after the 10 million you get for free) [1]. Vercel is wrapping R2 and is charging $2 per million reads [2]. They're also charging $0.15/GB for egress (after the 1GB you get free), when R2 charges nothing, and the storage cost is doubled from $0.015/GB on R2 to $0.03/GB on Vercel. That's quite the cost increase for the DX improvement.

[1] https://developers.cloudflare.com/r2/pricing/

[2] https://vercel.com/docs/storage/vercel-blob/usage-and-pricin...

For what it's worth, it's powered by statuspage.io, which is relatively industry standard for status pages.

https://www.githubstatus.com/incidents/52z0j6phhnjs

https://www.githubstatus.com/incidents/52z0j6phhnjs

Also seeing unicorns, mostly for "No server is currently available to service your request.". If I don't get a unicorn, the page takes a long old time to load.

Related, LMC is a great simulator to learn basic CPU instructions on (I encountered it both at school and at university [UK]): https://peterhigginson.co.uk/lmc/