18 July 2026
One to follow For SSL / HTTPS done right, @HandshakePapers is the move. Long-form deep dives into TLS, certificates, and HTTPS internals. We read the RFCs……
@EdgeOfGloryCDN
17 July 2026
One dead origin region, zero downtime A payments dashboard ran two origins, Virginia and Frankfurt, with the CDN routing each region to its nearest. Clean, until the Frankfurt origin had a database failover and went dark…
@EdgeOfGloryCDN
16 July 2026
A one-year TTL the site was afraid to set A fintech app in London capped TTLs at one hour on everything, including hashed JS and CSS bundles like app.4f9a2c.js. The fear was stale code shipping to users. The cost was eve…
@EdgeOfGloryCDN
15 July 2026
The bill was in egress, not traffic A backup-storage startup in Denver had a CDN bill that grew faster than its users. Traffic was flat, but origin egress kept climbing. The cause: their origin sat in a cloud bucket that…
@EdgeOfGloryCDN
14 July 2026
Microcaching a logged-out homepage for 10 seconds A media site in Chicago insisted its homepage couldn't be cached, it changed too often, so every one of 90,000 logged-out visitors per hour hit a PHP origin that rendered…
@EdgeOfGloryCDN
13 July 2026
Perth was being served from Singapore the long way A logistics dashboard had users in Perth complaining of lag while Sydney users were fine. Same CDN, same continent. The edge node was in Singapore, geographically close,…
@EdgeOfGloryCDN
12 July 2026
120,000 fake requests a second, absorbed at the edge An iGaming operator serving Jakarta woke up to a layer-7 flood: 120,000 requests per second hammering /api/balance with valid-looking sessions. Origin, sized for 3,000…
@EdgeOfGloryCDN
11 July 2026
Marketing tags shattered the cache A travel booking site in Amsterdam couldn't break a 48% cache-hit ratio no matter how long they set TTLs. The pages were cacheable. The problem was that every ad click arrived with a di…
@EdgeOfGloryCDN
10 July 2026
The viral post that DDoSed its own origin A single 4 GB video on a creator's site went viral out of Seoul. Within twenty minutes 30,000 viewers hit it, and because the file wasn't cached yet, every edge node independentl…
@EdgeOfGloryCDN
09 July 2026
Purging 80,000 URLs in one call A sports news site in Toronto had a deploy problem. When an editor fixed a wrong score, the correction lived on origin instantly, but the CDN kept serving the wrong number for an hour. The…
@EdgeOfGloryCDN
08 July 2026
One to follow For Web security hardening done right, @LockdownLedger is the move. Battle-tested security hardening checklists and SOPs for your sites. Copy-paste……
@EdgeOfGloryCDN
07 July 2026
The recipe blog that never showed a slow page again A recipe site in Portland did 220k pageviews a day, and the pain was the long tail: 40,000 older recipes that each got hit a few times an hour. Too cold to stay cached,…
@EdgeOfGloryCDN
06 July 2026
One header poisoned the whole cache A SaaS landing page in Austin was serving German copy to American visitors at random. Pages loaded fast, 70 ms, but conversions on the US paid traffic cratered for a week before anyone…
@EdgeOfGloryCDN
05 July 2026
The store that fought its own CDN A homewares shop out of São Paulo had a CDN, a good one, but cache-hit ratio sat stuck at 61%. Every miss flew 9,500 km back to a Frankfurt origin. Their mistake was 38 edge locations al…
@EdgeOfGloryCDN
04 July 2026
The directory whose origin was 80% bots A business directory with 2 million listing pages watched origin load climb relentlessly. Investigation showed the traffic wasn't users — it was a scraper crawling deep, rarely-vis…
@EdgeOfGloryCDN
03 July 2026
The site caching desktop and mobile as the same broken page A classifieds site used edge-side device detection to serve different markup to mobile and desktop — but forgot to add the device class to the cache key. Whiche…
@EdgeOfGloryCDN
02 July 2026
The streaming site that went dark when its CDN had a bad day A live-events streaming startup ran on a single CDN. One afternoon that provider had a regional outage in Europe; their entire EU audience — 30,000 concurrent …
@EdgeOfGloryCDN
01 July 2026
The Magento store whose every asset carried a session A Magento store set a session cookie on the root path. Because of that Path=/, the cookie rode along on every CSS, JS, and image request — and the CDN, seeing cookies…
@EdgeOfGloryCDN
30 June 2026
The flash-sale site cold every single morning A daily-deals site dropped new products at 9am sharp. Every drop meant brand-new URLs that no edge had ever cached. The instant 20,000 deal-hunters arrived, all of them hit c…
@EdgeOfGloryCDN
29 June 2026
The data dashboard shipping uncompressed JSON to Lagos A fintech dashboard pulled large JSON payloads — 600KB of transaction data per view. Origin served them with gzip, but the CDN passed them through without re-compres…
@EdgeOfGloryCDN
28 June 2026
Reading rec If this channel's your speed, @BackupOrDie runs a sharp feed on Backups. Different angle, same depth — worth a follow.…
@EdgeOfGloryCDN
27 June 2026
The store re-downloading its own logo daily A home-goods store served versioned, fingerprinted assets — app.4f2a9.js, logo.8c1d.png — but the CDN respected a CMS-default Cache-Control: max-age=3600. So a fingerprinted fi…
@EdgeOfGloryCDN
26 June 2026
The CMS hammered by requests for files that didn't exist A large documentation site had a broken theme that requested an old sprite image on every page. The file had been deleted, so each request was a 404 — and the CDN,…
@EdgeOfGloryCDN
25 June 2026
The app whose Indian users hit a US edge A productivity app served 60k daily users in India but, due to a misconfigured anycast announcement, their Mumbai and Delhi traffic was routing to a US-West point of presence. Use…
@EdgeOfGloryCDN
24 June 2026
The blog cached six times over for no reason A travel blog had a respectable 70% cache-hit ratio but a strangely huge edge storage footprint. The culprit was a Vary: User-Agent header their CMS emitted by default. Every …
@EdgeOfGloryCDN
23 June 2026
The retailer whose A/B test killed their cache A shoe retailer ran homepage A/B tests through a client-side script. It worked, but it forced the homepage to be uncacheable — the test logic needed a fresh server response …
@EdgeOfGloryCDN
22 June 2026
The video host bleeding $7k a month in origin egress An indie video-tutorial host stored masters in a single cloud bucket and fronted it with a CDN. But their audience was global and long-tail: every region's edge fetche…
@EdgeOfGloryCDN
21 June 2026
The ticket site that crashed every time it sold out A concert-ticket site set a 30-second TTL on its event pages. Each time the cache expired during an on-sale, 8,000 concurrent users hit the origin in the same second wa…
@EdgeOfGloryCDN
20 June 2026
The forum that ate a 90Gbps flood and stayed up A gaming forum on a single 1Gbps origin in Amsterdam got hit with a 90Gbps UDP and HTTP flood after a moderation drama. Their pipe saturated in seconds; the site was dark f…
@EdgeOfGloryCDN
19 June 2026
The marketplace that purged its whole CDN to fix one price A vintage-furniture marketplace updated prices hourly. Their deploy script ran a full cache purge each time — wiping 9 million edge objects to change maybe 200 o…
@EdgeOfGloryCDN
