Three Days in August: What a DDoS Attack Exposed in Our Network
← All blog posts • Know-how • 9 min read RSSThree Days in August: What a DDoS Attack Exposed in Our NetworkWritten byRaphael KnechtPublished onSeptember 21, 2026Share On the evening of 11 August 2026, one of our customers became the target of one of the largest attacks we have ever seen directed at our infrastructure. Because we provide that customer’s connection to the internet, the impact hit us directly as well, and a few hours later the attacker turned against our own services too. We already published a technical postmortem as a PDF on this incident.
- ▪← All blog posts • Know-how • 9 min read RSSThree Days in August: What a DDoS Attack Exposed in Our NetworkWritten byRaphael KnechtPublished onSeptember 21, 2026Share On the evening of 11 August 2026, one of our customers became the target
- ▪Because we provide that customer’s connection to the internet, the impact hit us directly as well, and a few hours later the attacker turned against our own services too.
- ▪We already published a technical postmortem as a PDF on this incident.
Hacker News (Front Page) files mainly under programming. We currently carry 2,225 of its stories. Top-voted stories on Hacker News.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Nine |
| Canonical URL | https://nine.ch/en/blog/ddos-attack-august-2026-postmortem/ |
| Publication time | Mon, 28 Sep 2026 09:13:36 +0000 |
| Retrieval time | 2026-09-28T11:46:09.832Z |
| Last seen | 2026-09-28T11:46:09.832Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | Jd92HvbUR9Sb · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
← All blog posts • Know-how • 9 min read RSSThree Days in August: What a DDoS Attack Exposed in Our NetworkWritten byRaphael KnechtPublished onSeptember 21, 2026Share On the evening of 11 August 2026, one of our customers became the target of one of the largest attacks we have ever seen directed at our infrastructure. Because we provide that customer’s connection to the internet, the impact hit us directly as well, and a few hours later the attacker turned against our own services too. We already published a technical postmortem as a PDF on this incident.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Nine.
Discussion
0 commentsMore from Nine
