About the Network Conditions Desk

Network Conditions documents the chain side of trading on Solana. Congestion, degraded periods, epoch turnover, client upgrade windows, and the discipline of separating a network-wide condition from a fault inside your own stack. It exists because the language traders use for these situations is almost entirely tool language, and the mechanisms underneath have names, published documentation and specific responses.

What the desk covers

Three sections, deliberately narrow. Conditions describes the states a cluster can be in and what each one does to a trade. Diagnosis is about isolating which of four layers owns a failure, and about reading network signals yourself instead of guessing from a single failed request. Response covers the working posture during a bad period and the review that follows one.

What the desk does not cover is equally deliberate. It is not a market publication, it does not analyse tokens, it does not evaluate strategies, and it does not publish predictions. Where automation is mentioned, it is mentioned as a thing that meets network conditions differently from a human, not as a subject in its own right.

How pages are sourced

Mechanisms are described from public protocol documentation and from the documentation published by the maintainers of the validator client. Where a page refers to something an operator publishes, such as cluster status or an incident write-up, it links to the root of that property rather than paraphrasing or mirroring its contents.

Numbers appear under three conditions and no others. They may be published protocol constants, such as the number of lamports in a SOL or the target slot duration. They may be arithmetic derived from those constants, in which case the page says so in the same sentence. Or they may be assumptions in a worked example that is explicitly labelled as illustrative. Anything else would be a measurement, and this desk does not run measurements it could stand behind.

What is never published here

• Narratives of specific historical incidents with invented dates, durations, block heights or causes.
• Uptime percentages, failure rates, throughput figures or any statistic presented as an observation of the network.
• Testimonials, review counts, ratings, or any claim about how many people use anything.
• Invented authors, credentials, photographs or biographies. Pages carry the desk byline.
• Backdated publication dates. A page is dated when it was published and its modified date moves when it changes.
• Real-time status claims. Nothing here is live, and every report says where live status actually lives.

Why incidents are described as classes

Serious network events are documented by the people who have the evidence: the operators who ran through them and the maintainers who changed code afterwards. A third-party reconstruction adds nothing and reliably introduces errors, because the details that matter are exactly the ones that get compressed when a story is retold.

So this desk writes about incident classes and their mechanisms, and points readers at the official sources for anything specific. If you want to know what happened during a particular event, read what the operators published about it. If you want to know what to do the next time something like it happens, that is what these pages are for.

Corrections

Pages are corrected in place, and the modified date moves with the correction. If a report states something that contradicts the protocol documentation, or describes a mechanism that has since changed, the desk would rather be told than left alone. Point at the page, quote the sentence, and name the source that disagrees with it.

Corrections that change the meaning of a page are made as directly as possible rather than softened, because a hedged correction is worse than the original error. Where a change is substantial, the page says what changed rather than quietly rewriting the passage.

Independence and limits

This desk is not affiliated with the Solana Foundation, with any validator operator, with any client maintainer, or with any venue named in these pages. It does not operate any trading tool and does not verify the output of any product it links to. Commercial links on this site open products run by third parties, and their presence is not an endorsement of their results.

The limits are worth stating plainly. Nothing here is trading advice. Nothing here is a status indicator. Nothing here should be the last thing you read before making a decision with money attached, because a static page cannot know what the network is doing while you are reading it.