-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
XBB.1.5.18 with spike muts Q675K and F456L (59 seqs, UK, France and Portugal) #29
Comments
48 seqs as today |
50 as today. Boris could you find a more specific nuc mutations query? i fear soon this will catch seqs from other lineages. |
There is recently a rising amouny of s:t961m in this lineage (about 13 in the most recent 25). While looking for a better query, i started with this one which is based on s:675k, orf1a:2554v and orf1a:t2300i: C23585A, C7926T, C7164T So here is the more strict one, missing the one sequence that probably does belong here, 50 seq: For the newer subbranch with 961m (here i exclude s:456l in the query to catch the extra one, i think it wouldnt matter much since 961m is only 0.1% prevalence in general) |
Furthermore, within this 961m branch there is also s:t76i which is a reasonably fit mutation, known from ba.5.5 |
Two more from England, even if it appears to me not that fast. better tracking it for a while more |
59 now |
Doesn't seem to be going anywhere, i'll give this issue one more week |
Closing this for now |
[transferred from the pango repo. This cluster has slowed down a lot so im closing it there and keeping it here only to keep an eye on it once in a while]
GISAID query: C23585A, C7926T, C7164T, T22930A
First sequence: 27-02-2023
Most recent sequence: 03-05-2023
USHER tree: (first zoomed in on subbranch of xbb.1.5.18, second is from root of xbb.1.5.18)
https://nextstrain.org/fetch/genome.ucsc.edu/trash/ct/subtreeAuspice1_genome_2423f_fdef30.json?c=gt-S_456
675K has had some mild success in other xbb.1.5 lineages, nothing too crazy though. The mutation site has however been designated before with 675H in EL.1.
F456L is present in the designated XBB.1.5.10. The mutations have not yet been together before. In that issue, the decreased ace2 affinity has been discussed, it still managed to reach 339 sequences. cov-lineages/pango-designation#1614
F456L is also trending upwards in general over the last half year, reaching 1% globally and as high as 30-40% in brazil (where there is another xbb.1.5.18 with F456L, but without the Q675K and maybe unrelated to this one) https://cov-spectrum.org/explore/World/AllSamples/AllTimes/variants?aaMutations=s%3A456l&
Currently all sequences come from the UK, but from different labs and spanning across one month. Perhaps monitor for a while for spread.
Covspectrum (xbb.1.5.18 + Q675K): https://cov-spectrum.org/explore/World/AllSamples/Past6M/variants?aaMutations=s%3A675k&nextcladePangoLineage=xbb.1.5.18*&aaMutations1=S%3Af456L%2Cs%3A675k&nextcladePangoLineage1=xbb.1.5.18*&
Covspectrum (xbb.1.5.18 + Q675K + F456L): https://cov-spectrum.org/explore/World/AllSamples/Past6M/variants?aaMutations=s%3A675k%2Cs%3A456l&nextcladePangoLineage=xbb.1.5.18*&aaMutations1=S%3Af456L%2Cs%3A675k&nextcladePangoLineage1=xbb.1.5.18*&
EPI:
EPI_ISL_17178847, EPI_ISL_17179037, EPI_ISL_17179130,
EPI_ISL_17210195, EPI_ISL_17267562, EPI_ISL_17284241,
EPI_ISL_17284584, EPI_ISL_17298483, EPI_ISL_17359825-17359826,
EPI_ISL_17359906, EPI_ISL_17359982, EPI_ISL_17359988,
EPI_ISL_17360033, EPI_ISL_17372899, EPI_ISL_17372927,
EPI_ISL_17372947, EPI_ISL_17373052, EPI_ISL_17373054,
EPI_ISL_17381791, EPI_ISL_17382468, EPI_ISL_17400433,
EPI_ISL_17400495, EPI_ISL_17400528
The text was updated successfully, but these errors were encountered: