# Traffic Published articles for Traffic. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## CAPIF 5: Regional Interconnectivity in Central Asia DevFeed: [CAPIF 5: Regional Interconnectivity in Central Asia]() Original publisher: [Read original article]() Author: Anastasiya Pak Published: 2026-09-17T17:29:36Z Content type: article Language: en Sources: [RIPE Labs]() Topics: [Internet](), [Routing Security](), [networking](), [Networks]() Tags: [2026](), [adoption](), [aspa](), [atlas](), [central](), [connectivity](), [country](), [events](), [internet](), [ipv4](), [ipv6](), [ixps](), [measurements](), [progress](), [region](), [report](), [research](), [ripe](), [ris](), [routing](), [routing-security](), [rpki](), [traffic]() ### AI overview This report examines changes in Central Asia's Internet connectivity since CAPIF 1. It describes more direct regional routes, expanding IXPs, stronger routing security and new links toward Pakistan, China, Azerbaijan and Europe, while noting persistently low IPv6 adoption and continued, though reduced, reliance on routes through Russia. ### Source excerpt Central Asia's Internet looks very different than it did back at CAPIF 1. We trace the rise of direct regional routes, stronger routing security and new connectivity options - along with the gaps that remain. ## How to Get Free Traffic to Your Website in 2026: The Complete Free-to-Paid Growth Playbook DevFeed: [How to Get Free Traffic to Your Website in 2026: The Complete Free-to-Paid Growth Playbook]() Original publisher: [Read original article]() Author: iHateReading Published: 2026-09-10T12:46:02Z Content type: tutorial Language: en Sources: [iHateReading]() Topics: [Website](), [Software as a service]() Tags: [2026](), [backend](), [blockchain](), [coding](), [development](), [founders](), [frontend](), [growth](), [guide](), [how-to](), [how-to-get-free-traffic-to-your-website-in-2026-the-complete-free-to-paid-growth-playbook](), [ihatereading](), [javascript](), [marketing](), [node-js](), [product](), [programming](), [react](), [seo](), [seo-traffic-growth-founders-marketing](), [traffic](), [typescript](), [web-development](), [website]() ### AI overview A guide to getting free website traffic in 2026 and moving from free acquisition methods toward paid growth. ### Source excerpt ree SaaS directories to submit for free 2026, Reddit marketing for startups without ads, Hacker News Show HN launch guide, Dev.to article distribution for deve... ## Cache stampede: how one expired key takes down the database DevFeed: [Cache stampede: how one expired key takes down the database]() Original publisher: [Read original article]() Author: hello@ankit-rana.com Published: 2026-09-05T00:00:00Z Content type: tutorial Language: en Sources: [Ankit Rana | Mechanical Sympathy]() Topics: [Cache](), [Caching](), [Database](), [consistent hashing](), [Redis]() Tags: [cache-stampede](), [caching](), [connection-pool](), [consistent-hashing](), [distributed-systems](), [jitter](), [query](), [redis](), [reliability](), [thundering-herd](), [traffic](), [ttl]() ### AI overview This article explains how a cache stampede occurs when a hot key expires and many requests simultaneously recompute the same value against the database. It recommends TTL jitter to prevent synchronized expirations and request coalescing so only one caller recomputes while others wait or serve stale data. It also discusses cache warming and consistent hashing for broader cache-failure scenarios. ### Source excerpt A cache TTL is a scheduled simultaneous failure: every request being served from one key misses at the same instant and goes to the origin together. If the recompute takes two seconds, every request arriving during those two seconds also misses, so the pileup grows faster than it drains. Jitter on the TTL stops keys expiring in lockstep, and request coalescing so only one caller recomputes while the rest wait or serve stale is what stops a single expensive key from saturating the database. ## RFC 10005: BGP Community for link capacity DevFeed: [RFC 10005: BGP Community for link capacity]() Original publisher: [Read original article]() Author: j2sw Published: 2026-07-01T13:31:00Z Content type: article Language: en Sources: [Justin Wilson (j2sw)]() Topics: [BGP](), [standard](), [Load Balancing](), [Network]() Tags: [bgp](), [capacity](), [internet](), [load-balancing](), [network](), [network-operations](), [rfc](), [rfc-10005](), [route](), [routers](), [routing](), [standard](), [traffic]() ### AI overview RFC 10005 defines a BGP extended community for carrying link bandwidth information in routes. When multiple BGP paths are eligible, routers can use the value to weight traffic according to link capacity, while normal best-path policy still determines route eligibility. The RFC is currently a draft. ### Source excerpt RFC 10005 defines a BGP extended community that lets a router attach link bandwidth information to a route. Another router can use that value when it spreads traffic across multiple BGP paths. RFC 10005 matters because links are not always of the same capacity. This RFC provides routers with a standard way to carry bandwidth ... Read more The post RFC 10005: BGP Community for link capacity appeared first on Justin Wilson (j2sw). ## George Washington, the Delaware, and Direct Routes DevFeed: [George Washington, the Delaware, and Direct Routes]() Original publisher: [Read original article]() Author: j2sw Published: 2026-06-30T16:15:53Z Content type: opinion Language: en Sources: [Justin Wilson (j2sw)]() Topics: [Network design](), [Networks](), [BGP](), [Network]() Tags: [bgp](), [blog](), [fd-ix](), [internet-architecture](), [ixp](), [network-design](), [network-peering](), [networks](), [peering](), [route](), [routers](), [routing](), [traffic](), [transit]() ### AI overview This commentary compares George Washington's direct route across the Delaware with network peering. It argues that direct connections between networks can reduce transit dependencies, router hops, and latency compared with longer BGP-selected transit paths. ### Source excerpt I originally posted this over on the FD-IX Bloghttps://blog.fd-ix.com/george-washington-the-delaware-and-direct-routes/ When George Washington crossed the Delaware River on Christmas night in 1776, the goal was simple. Reach the objective by the most effective path while avoiding unnecessary delays and giving the opposing force as little warning as possible. The crossing was risky, but it created a ... Read more The post George Washington, the Delaware, and Direct Routes appeared first on Justin Wilson (j2sw). ## Sam's First Visit to An Internet Exchange DevFeed: [Sam's First Visit to An Internet Exchange]() Original publisher: [Read original article]() Author: j2sw Published: 2026-06-25T03:54:15Z Content type: release Language: en Sources: [Justin Wilson (j2sw)]() Topics: [networking](), [Networks](), [Internet Traffic](), [BGP]() Tags: [bgp](), [book](), [books](), [children](), [explainer](), [fiber](), [internet](), [internet-architecture](), [internet-exchange](), [internet-traffic](), [ix](), [ixp](), [j2-updates](), [j2sw](), [justin-wilson](), [network-engineering-resources](), [networking](), [networks](), [peering](), [router](), [sam](), [stem-book](), [traffic]() ### AI overview Justin Wilson announces A Kid's First Visit to An Internet Exchange, a children's picture book in which Sam learns how networks connect, peer, and move Internet traffic. The book is available in Kindle and paperback editions. ### Source excerpt Justin Wilson announces his second children's networking book, A Kid's First Visit to an Internet Exchange. Follow Sam as he learns how networks meet, peer, and move Internet traffic. The post Sam's First Visit to An Internet Exchange appeared first on Justin Wilson (j2sw). ## Telegram prefixes hijack by Rcom AS18101 DevFeed: [Telegram prefixes hijack by Rcom AS18101]() Original publisher: [Read original article]() Published: 2026-06-16T19:44:03Z Content type: opinion Language: en Sources: [Personal blog of Anurag Bhatia]() Topics: [BGP](), [networking](), [Routing (disambiguation)]() Tags: [airtel](), [as15412](), [as18101](), [as4755](), [bgp](), [india](), [outage](), [rcom](), [ripe-ris](), [routers](), [routing](), [rpki](), [telegram](), [traffic]() ### AI overview The article examines Rcom AS18101's apparent BGP hijacking of Telegram prefixes during Telegram's blocking in India. It confirms that Rcom originated at least one Telegram prefix and argues that the incident was more likely an accidental configuration error than intentional sabotage, while noting that the impact varied by upstream connectivity. ### Source excerpt The last few hours were quite noisy with a lot of discussion around Telegram block and Rcom's hijack of Telegram prefixes. For those who may not know, Telegram has been blocked in India till 22 June 2026 (news here). The justification has been to avoid paper leak over the telegram. Anyways, I am not going into whether the block is good or bad as it can be part of an endless discussion depending on how one views it. Maybe some separate time but let's look at the BGP routing side of things. ISPs went for blocking it in all possible ways - from the usual DNS layer to block resolution of Telegram to also blackhole its prefixes. Telegram is a special case as they have their own ASN, IP prefixes etc making it easy to block them at the routing layer directly. I saw this on Airtel, where traffic seems to be dropping at their routers. mtr -wby0 -4 web.telegram.org Start: 2026-06-17T01:20:46+0530 HOST: desktop Loss% Snt Last Avg Best Wrst StDev 1. AS??? _gateway (172.16.0.1) 0.0% 10 0.2 0.2 0.2 0.2 0.0 2. AS??? 10.240.9.204 0.0% 10 4.6 7.4 4.2 25.7 6.5 3. AS??? 172.31.0.154 0.0% 10 8.1 13.5 6.4 26.4 6.2 4. AS9498 169.168.18.125.dhcp.anaronline.net (125.18.168.169) 0.0% 10 5.2 6.8 4.9 13.6 2.6 5. AS??? ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 At 11:58 PM - Telegram CEO Pavel Durov tweeted and accused Reliance (technically Rcom and not Jio) for outage of Telegram outside of India by BGP hijacking. Indian telecom Reliance is sabotaging access to Telegram for millions of users OUTSIDE India (including the UAE) via a rogue method called BGP hijacking. The sabotage seems intentional, as Reliance has ignored multiple reports. This may be part of a competitive war, as... -- Pavel Durov (@durov) June 16, 2026 Technically it's true that Rcom AS18101 has hijacked Telegram's prefixes. Take e.g 91.105.192.0/23 - AS18101 started originating this prefix at 16:14:19 GMT / 21:44:19 IST on 16 June as visible from many RIPE RIS collectors including RIPE RIS RRC01 in London. It's bad and they should not ha ## Stressing the network when it's already down DevFeed: [Stressing the network when it's already down]() Original publisher: [Read original article]() Author: ben@benjojo.co.uk Published: 2020-04-30T10:08:38Z Content type: opinion Language: en Sources: [benjojo blog]() Topics: [Network](), [Internet](), [Networks](), [netflow]() Tags: [internet](), [netflow](), [network](), [outage](), [outages](), [traffic]() ### AI overview An analysis of recurring Liberty Global network outages, particularly on Virgin Media's UK network, and the evidence from reachability, bandwidth, and NetFlow monitoring. It discusses how customers running speed tests after connectivity returned may have created a positive feedback loop that added congestion. ### Source excerpt Stressing the network when it's already down [Impact by Eric Wienke, edits by Ben Cartwright- ## 2019 Recap: Blog Growth, Work Projects, and Mailchimp Presents DevFeed: [2019 Recap: Blog Growth, Work Projects, and Mailchimp Presents]() Original publisher: [Read original article]() Author: Stanko Published: 2019-12-31T00:00:00Z Content type: article Language: en Sources: [Stanko Tadić]() Topics: [Contentful](), [GraphQL](), [static-site-generator]() Tags: [blog](), [contentful](), [graphql](), [static-site-generator](), [traffic]() ### AI overview A personal 2019 recap covering blog analytics, work at Work & Co, the Mailchimp Presents media portal, collaboration with IKEA, and side projects. The Mailchimp project used a GatsbyReact static site generator, Contentful, and GraphQL API. ### Source excerpt Last time I wrote one of these recaps was in 2016. Not sure why I waited three years to write another, and from now on I'll try to do these annually. 2019 was a good year for me, and I want to highlight a couple of things. Blog # I'm really proud of my blog. And judging by the analytics, people are actually reading it - this year I had over 100k users visiting and ~85% of the traffic is coming from the organic search! This is not the first blog I had, but this is the one I'm sticking with. I love how there is a dip every single weekend. People are finding my articles almost exclusively on work days, probably while searching for work related problems. But the bounce rate is also high, almost 85%. After reading one article users are not sticking for long. That is something I want to improve in the next year. Work & Co # It has been a while since I started working with Work & Co, and it continues to be a wonderful experience. I'm thrilled and proud to have the opportunity to collaborate with such talented people. To top it all, this October I was promoted to a Group Technology Director. Mailchimp Presents # One of the projects I had a pleasure of working on this year was Mailchimp Presents. We teamed up with Mailchimp to help them create a brand new media portal. It was a short timeline, but it was a breeze as people from Mailchimp were brilliant to work with. The fact my team crushed it helped as well. It was built around mantra "content is king" and we dedicated a lot of attention to the content recirculation. All shows are Mailchimp originals, and they did incredible job with them. Production is world class, and content is in a short, snackable format for people on the go. You should definitely check it out yourself. We built it using GatsbyReact static site generator and Contentful (using GraphQL API). The stack helped us to move fast and to ship the product in time. The reception was incredible, people love the shows, and conversion numbers are really high. This S ## Economist submission: How the Internet Leaks DevFeed: [Economist submission: How the Internet Leaks]() Original publisher: [Read original article]() Published: 2019-10-05T11:08:38Z Content type: opinion Language: en Sources: [Bert Hubert's writings]() Topics: [networking](), [BGP](), [Internet](), [Routing (disambiguation)](), [datacenter]() Tags: [bgp](), [datacenter](), [fraud](), [internet](), [networking](), [routing](), [traffic](), [trust]() ### AI overview The article explains how route leaks caused by incorrect BGP announcements can disrupt internet services and redirect traffic. It describes filtering as a control that limits which routes operators trust and propagate, helping reduce accidental outages and some forms of internet hijacking. ### Source excerpt Note: For context, please see this article on the Economist Job. I also want to thank Job Snijders who was of great help in writing this article. How the Internet Leaks A few weeks ago large swathes of the internet stopped working around the world. The cause was quickly found: a computer networking mistake over at a specialty metals company based in Pittsburgh, Pennsylvania. Earlier that month, a similar accident took down payment terminals in The Netherlands because of a misconfiguration in a Swiss datacenter which rerouted key parts of the internet to China. ## How BGP Exchanges Routing Information Across Internet Networks DevFeed: [How BGP Exchanges Routing Information Across Internet Networks]() Original publisher: [Read original article]() Author: ben@benjojo.co.uk Published: 2018-05-21T12:24:31Z Content type: opinion Language: en Sources: [benjojo blog]() Topics: [BGP](), [networking](), [Routing (disambiguation)](), [Internet](), [Protocol (disambiguation)](), [Amazon Route 53]() Tags: [bgp](), [configuration](), [internet](), [protocol](), [router](), [routing](), [topology](), [traffic]() ### AI overview An explanation of how BGP enables routers and ISPs to exchange routing information across the internet. It discusses internet topology, peer relationships, configuration policies, route filtering, and the risks of route hijacking. ### Source excerpt Playing battleships over BGP BGP is the glue of the internet. For a protocol that was produced on two napkins in 1989 it is both amazing and horrifying that it runs almost all of the ## Where to start with developer content DevFeed: [Where to start with developer content]() Original publisher: [Read original article]() Author: Map Published: 2014-01-21T20:55:56Z Content type: opinion Language: en Sources: [Craig Kerstiens]() Topics: [Publishing](), [Reddit](), [X (Twitter)]() Tags: [developer](), [developers](), [engagement](), [hacker-news](), [indexing](), [marketing](), [publishing](), [reddit](), [traffic](), [twitter]() ### AI overview The article discusses how developers and companies can distribute content beyond Hacker News. It compares Hacker News, other news sites, Twitter, and Google Plus, arguing that these channels differ in reach, shelf life, traffic quality, engagement, and indexing speed. ### Source excerpt Getting the word out Hacker News When it comes to marketing, specifically to developers, the most common question is how do I get on Hacker News? The second most commong is, well in addition to there what matters. This fully depends on your audience, and if you really only care about the former versus the broader issue of creating a sustainable model for circulating your content then just read these links then move on. If you want a full model for getting your content out there then keep reading. The best time to post to hacker news How to get on the front page of hacker news More than just Hacker News First off don't get me wrong, HN can provide a great surge of short term traffic. There's a few problems I have with this though. To begin with it gives you one shot to get your message perfect, if you have the wrong message, miss your call to action, or forget an affiliate link then you get your 15k viewers well you get no second shot at it. Though more interestingly and a bit of gut feel, I've noticed that traffic contains more bounes and lower engagement. And then theres the issue that its definitely not a science to getting on there.... Other news sites Of course theres other news sites, ones of relevance include reddit, dzone, monacle. I've found each of these can be similar in some ways to hacker news. Yet, they have a bit longer of a shelf life, giving me a slightly higher propensity to give them some attention. At the same time they also have a smaller reach. Twitter Twitter is yet another method that can work quite well. Observations of it include lower traffic than something like a hacker news, and equal to better engagement overall. Perhaps the most interesting piece I find is that you'll often get more intelligent and also positive discussion on twitter vs. HN. There is one huge fail I find with twitter that nearly every company commits. The author of the post or company twitter handle posts it, then 10 people proceed to retweet it within 10 minutes. The pro ## SSL scanners DevFeed: [SSL scanners]() Original publisher: [Read original article]() Author: Marek Published: 2012-11-11T23:00:00Z Content type: opinion Language: en Sources: [Marek Majkowski]() Topics: [SSL](), [TLS (Transport Layer Security)](), [client](), [browser]() Tags: [browser](), [client](), [scanners](), [ssl](), [tls](), [traffic]() ### AI overview The author analyzes unusual SSL client requests observed while recording traffic on port 443 to build a database of SSL fingerprints. The article compares scans associated with SSL Labs, Netco Solutions, Johns Hopkins University, Amazon, and Opera, and discusses possible purposes and suspicious protocol probes. ### Source excerpt SSL scanners In June I started playing with fingerprinting SSL client requests. For example, an SSL fingerprint of my browser is: Read the docs of fingerprint format, or even more detailed description. I wanted to prepare a database of popular fingerprints, so I started recording traffic on port 443. I quickly noticed that apart from normal traffic there are some hosts sending weird SSL requests that make no practical sense and look like scanning. ## Evaluating Paying for a Blog Post DevFeed: [Evaluating Paying for a Blog Post]() Original publisher: [Read original article]() Author: Map Published: 2011-02-26T03:55:56Z Content type: opinion Language: en Sources: [Craig Kerstiens]() Topics: [Users]() Tags: [blog-post](), [business](), [sponsored](), [traffic]() ### AI overview The article explains how to evaluate paying for sponsored blog posts as a user acquisition channel. It recommends checking a blog's reported traffic, audience engagement, and posting frequency before sponsoring a post. ### Source excerpt At a recent meetup I talked a bit about how I'd been using blog posts on other blogs, both free and paid for as a primary user acquisition tool. I was very shocked, when several were surprised and curious on the method for this. In tech startups coverage is common, but its usually just that press, not paid for press. I must say I love how the tech community doesn't force people to pay to get the word out, but it is very much a competition; that might be just as much work as paying. In contrast the wedding industry is very much a pay to play space. If you give some money you can get some attention. First things first, contact the blog you're interested in being written up in and ask for their media kit. If they welcome sponsored posts, then it is likely called out in their media kit. However, this isn't always the case, if you've noticed posts on their blog that have been sponsored posts but pricing isn't called out in their blog then email them explicitly and inquire. Once you've got their media kit its time to do some digging. My process has first been to validate their numbers. Most blogs include their unique visitors and page views in their media kits. I immediately jump over to compete to check if their numbers are even in the ballpark. To clarify in the ballpark can be somewhere around 1.5x of compete. There are a surprising number of blogs that may be 20x off in the numbers they are stating. This could mean you're outright lying on your stats, or that you're not running a solid enough business that you know how to effectively track your numbers. It could be, because your blog exists on 5 different domains, while compete I'm checking only the primary. Regardless, if you're numbers aren't close, it often means you're not as together as we'd like. If they pass the first smoke screen of the stats being in the ballpark, then we can move on to evaluating sponsoring a post. Traffic's a big factor, unique visitors are important as well as page views. Next we'll typica ## Apple's Software Control and Product Failures Compared with Microsoft DevFeed: [Apple's Software Control and Product Failures Compared with Microsoft]() Original publisher: [Read original article]() Author: Map Published: 2008-07-16T07:19:48Z Content type: opinion Language: en Sources: [Craig Kerstiens]() Topics: [Microsoft](), [Software](), [iphone](), [SDKs]() Tags: [apple](), [drive](), [iphone](), [marketing](), [microsoft](), [revenue](), [sdk](), [traffic]() ### AI overview An opinion piece argues that Apple and Microsoft should be judged similarly, criticizing Apple's control over software functionality and SDK access, its handling of iPhone 3G launch traffic, and its continued restrictions on applications. ### Source excerpt I find it extremely amusing that Microsoft and Apple are in many senses the very same company, at least in their actions, yet people feel very different about the two. For the average person they aren't really a fan of Microsoft, and many love Apple. While I'm not really suggesting anyone should love Microsoft, why are people such Apple fanboys. Apple makes the same bad moves as Microsoft, they control their software and limit functionality in order to drive sales in the future. For example with the iPhone, by disabling video streaming they are simply leaving something to be supported for next year. There's now doubt that the phone is fully capable, especially with 3g, as qik is already supporting it. However they are having to jump through hoops to do it, when Apple could have simply enabled it in the SDK, and yet they didn't. It's unfortunate for AT&T in the process as well, because as people are die hard Apple fans, they feel Apple can do no wrong. This wasn't quite the case in recent days, first with the launch of the iPhone 3g, there were many many bricked iPhones for that morning. Almost every complaint I saw on twitter drawed attention to AT&T screwing it up. However, from a source very close to the issue, the problem was entirely on Apple's end, as they had tested for only a fraction of the traffic they got that day, and were not able to scale up new machines nearly fast enough. Now Apple woes seem to continue as with MobileMe. For all the fan boys out there, and while I agree they make a good product, they should still be help to the same regard of anyone else that makes a product, and be complained to when they screw up. Apple has indeed done a great job with marketing and a reasonable job with products, however they keep a strong reign on applications, which is why I like the applications that are on OSX, but hate that its sucha smaller number. I'm not saying love Microsoft, or even hate Apple. But people judge them on their actions, and while they drive