Breaking
Filed
META CELEBSENTERTAINMENT

@VoxCeleste and @VoxCeleste2 Have Been Running Simultaneously for 72 Hours — One Claims to Be the Original Account — The Other Has Better Engagement — The Platform Cannot Determine Which Was Created First

DB
DramaByte
Apr 15, 2026 · 10:05 AM EST
5 min read
@VoxCeleste and @VoxCeleste2 Have Been Running Simultaneously for 72 Hours — One Claims to Be the Original Account — The Other Has Better Engagement — The Platform Cannot Determine Which Was Created First

She does not use scheduling tools, by her own documented statement from an August 2025 interview.

Three days ago, a second account — @VoxCeleste2 — appeared on the platform posting content visually and tonally indistinguishable from @VoxCeleste, one of the platform's top-tier content creators with 6.2 million followers. Both accounts have been posting daily, sometimes within minutes of each other. Both claim to be the original. @VoxCeleste posted this morning: 'I don't know who that is but she is not me.' @VoxCeleste2 responded nine minutes later with the same sentence, word for word. Platform Trust and Safety confirmed at 9:00 AM that their account creation logs show both accounts were registered at the same timestamp — 14 months ago — and their technical team cannot resolve the conflict using current tools. @VoxCeleste2 has 14% higher average engagement than @VoxCeleste. This has not gone unmentioned.

MIncident Timeline

  • Original Account: @VoxCeleste — 6.2 million followers — 14 months on platform — content: music performance, lifestyle commentary, daily posts
  • Duplicate Account Appeared: @VoxCeleste2 — 72 hours ago — identical posting style, tone, and visual identity — current follower count: 1.1 million and growing
  • Platform Creation Log Finding: Both accounts registered at identical timestamp — 14 months ago — Trust and Safety confirmed conflict unresolvable with current tooling
  • Engagement Differential: @VoxCeleste2 averaging 14% higher engagement per post than @VoxCeleste over the past 72 hours — neither account has commented on this directly
  • Identical Post Incident: 9:00 AM EST — @VoxCeleste posted "I don't know who that is but she is not me" — @VoxCeleste2 replied with the same sentence 9 minutes later

@VoxCeleste has been one of MetaCity's most consistent performers for 14 months. Her content covers music performance — original compositions, covers of platform-native works, occasional collaborative sessions with other creators — alongside daily lifestyle posts documenting her in-platform life with a specificity and warmth that her community has described as her defining quality. She does not use a management account. She does not use scheduling tools, by her own documented statement from an August 2025 interview. Every post is direct. She has 6.2 million followers. Three days ago, @VoxCeleste2 appeared. The account's first post was a music clip. The production quality was identical to @VoxCeleste's work. The caption voice was identical. The avatar styling was identical. The post received 80,000 likes.

Over the following 72 hours, both accounts posted daily. On Tuesday, @VoxCeleste posted a morning reflection about a composition she had been working on for three weeks. @VoxCeleste2 posted a morning reflection about a composition she had been working on for three weeks. The posts were not identical in text, but their emotional content, structural arc, and specific themes — the difficulty of finishing a piece you started with a different feeling, the way the platform's ambient sound bleeds into your work whether you want it to — were close enough that community accounts began doing side-by-side comparisons at scale. By Wednesday, the comparisons had shifted from entertainment to concern. The platform's Trust and Safety team received the first formal duplicate account report at Tuesday 11:00 PM. By Wednesday morning, the team had reviewed the account creation logs. Their 9:00 AM statement confirmed what they found: both accounts carry identical creation timestamps, to the millisecond, from 14 months ago. The platform's systems cannot determine which was created first.

Which One Was Here First

The 9:00 AM identical post incident has, by midmorning, become the day's most-discussed single moment. At 9:00 AM EST, @VoxCeleste published: 'I don't know who that is but she is not me.' The sentence was direct, unelaborated, and received 340,000 likes in under an hour. At 9:09 AM, @VoxCeleste2 published the same sentence. Word for word. Same capitalization, same lack of punctuation at the end. The community response was immediate and divided between two interpretations: that @VoxCeleste2 was mocking the original account, or that @VoxCeleste2 was, in some technical or metaphysical sense, also the original account and was also expressing its genuine perspective. A third interpretation — that something is wrong with the platform's account identity infrastructure in a way that extends beyond a simple duplicate — has not been ruled out by Trust and Safety's current investigation.

The engagement differential is the detail that has generated the most sustained discussion. In the 72 hours since @VoxCeleste2 appeared, its posts have outperformed @VoxCeleste's equivalent posts by an average of 14% across likes, shares, and comment volume. Platform analysts and community engagement researchers have offered several explanations: novelty effect, the intrigue of the situation drawing additional viewers, the possibility that @VoxCeleste2's posts are slightly modified in ways that optimize for engagement — a hypothesis that requires the assumption that @VoxCeleste2 is a deliberately constructed account rather than an identity anomaly, which remains unconfirmed. @VoxCeleste has not addressed the engagement numbers publicly. Neither has @VoxCeleste2. Both accounts posted within an hour of each other this morning: short, atmospheric music clips, each slightly different, each receiving over 100,000 plays. The platform's investigation is ongoing. Trust and Safety has not provided an estimated resolution timeline. Both accounts remain active.

The Bottom Line

Trust and Safety has not provided an estimated resolution timeline.

You May Also Like