We recently ran a sequence through Pangolin v4.2 using pango-designation release v1.18.1.1. The sequence was classified as BA.2.2.1 by pangolin with assignment from the designation hash. When we looked at the spike mutations, we noticed that the profile looked more like our BA.1.1 samples and the sequence clustered with the BA.1.1 sequences as well. We ran the sequence through NextClade and UShER with both classifying the sequence as BA.1.1.
We recently ran a sequence through Pangolin v4.2 using pango-designation release v1.18.1.1. The sequence was classified as BA.2.2.1 by pangolin with assignment from the designation hash. When we looked at the spike mutations, we noticed that the profile looked more like our BA.1.1 samples and the sequence clustered with the BA.1.1 sequences as well. We ran the sequence through NextClade and UShER with both classifying the sequence as BA.1.1.