Leo Cloud
series of galaxy clusters
The Leo II Groups, Leo II Cloud, or simply the Leo Cloud is a galaxy filament consisting of at least 18 galaxy groups. It is located approximately 86 Mly (26 Mpc) from the Solar System. The Leo Cloud in supergalactic SGY coordinates is physically behind the Virgo Cluster. Eventually, over the next Hubble time, the galaxy groups that make up the Leo II Cloud will infall and merge with the Virgo Cluster.
The Leo Cloud, along with the Crater Cloud which contains the NGC 4038 Group, is actually part of the same branch of a larger galaxy filament that extends from the Centaurus Cluster through the Virgo Cluster and continues through the Ursa Major Cluster, known as the Virgo Strand. The Virgo Strand is the main component of the Virgo Supercluster and is made of two branches with the lower branch consisting of the Leo and Crater clouds, while the upper branch is known as the Virgo Southern Extension or Virgo II Groups.
The Leo Cloud itself is actually composed of two filaments, the Leo II A and Leo II B filaments. The Leo II A filament consists of the majority of the cloud, while the Leo II B filament consists of a sparse region of the cloud.
The Leo Cloud, like the Virgo III Cloud, is prolate and points toward the Virgo Cluster.
List of groups
Below is a list of groups in the Leo Cloud according to astronomer Brent Tully.
“Leo Cloud” enters the record as series of galaxy clusters. Crown Archives preserves that source wording while asking what Cloud, series and galaxy can confirm, complicate or overturn.
Why this record matters
“Leo Cloud” is worth following because a concise public description often conceals a longer documentary argument. Here, Cloud, series and galaxy provides the most credible route into that argument.
The citation trail is more important than the brevity of the summary: it shows where individual claims can be examined in context. The source revision retrieved here is dated Aug 25, 2026. The linked authority identifier is Q113588300. None of the 0 selected statements returned an explicit reference.
Overview language is designed for orientation and should not be treated as a substitute for the evidence cited beneath it. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Leo Cloud”, its source revision and the description used here.
- Expand the search: follow Leo Cloud primary sources, Leo Cloud archive and Cloud research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Leo Cloud”?
- Which cited source is closest to the event, object or claim?
- Which institution is responsible for the underlying evidence?
Search terms from this dossier
This entry incorporates text from “Leo Cloud” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.