IPv6 delegation, an unusually subtle failure mode
0 comments · linux, networking
- Comments7
0 comments · linux, networking
Story details from Lobsters ↗ · linked article on savyasacheejha.com.
IPv6 delegation, an unusually subtle failure mode was first seen on Lobsters · Hottest on Nov 18, 2026. Since then it has appeared in 51 checks on 2 different days. Its best position was #9 of 25, reached on Nov 19, 00:21 UTC. It dropped off the list after Nov 19, 19:22 UTC. The same link also trended on Hacker News, which raises its cross-platform score.
Position on Lobsters · Hottest at every check (lower is better).
Best rank per day (UTC).
Platform metric as reported by Lobsters.
| List | Best | Days | Checks | Last seen |
|---|---|---|---|---|
| Lobsters · Hottest | #9 | 2 | 51 | |
| YHacker News · Front page IPv6 delegation, an unusually subtle failure mode | same link | |||
A few top-level comments from Lobsters, shortened. Read the full thread on Lobsters.
Interesting. I will keep an eye on this in my setup. Given the abundance of IPv6 addresses, I wonder why ISPs keep them dynamic. Every client should be getting assigned the same prefix.
This is an interesting case of how a status quo solution has a drag effect on trying to improve on that. The post doesn't mention it, but this is an ISP providing a crappy IPv6 experience. The ISP is offering a prefix ("range of addresses") with a lifetime, but then not honouring that lifetime. In consumer IPv4…
Sometimes, IPv6 depends on your IPv4 (like with the 6rd transition technology). Sometimes, it is to avoid user tracking. Sometimes, it is just to avoid people believing they have a fixed IPv6 subnet and complain the day it changes.
Archived daily, weekly and monthly lists that include this entry.
Not at the moment. It was last on the list on Nov 19, 19:22 UTC, after 2 days of trending.
#9 on Lobsters · Hottest, on Nov 19, 00:21 UTC. Trendoday checks this list every 30 minutes.
It was first seen on Nov 18, 2026 and has been on the list on 2 days (51 checks) since.