As I'm sure many of us are aware, the GXE75 has current issues regarding the Quest 3 / Pro & the 6Ghz channel in the form of disconnections and Ping spikes depending on current firmware.

Issues with firmware version -  Archer GXE75_V1_1.0.5 Build 20241217 *AND BELOW* were fixed

Issues with firmware version -  Archer GXE75_V1_1.1.0 Build 202510107 BETA 

Both the 5Ghz & 6Ghz channels seem to be affected by the 160MHz band.

THIS LEADS TO SEVERE PING SPIKING ON BOTH CHANNELS AND CAN BE RECREATED EASILY

PING SPIKES CAN ALSO HAPPEN REGARDLESS UPON DEVICE SLEEP/WAKE - THIS INCLUDES DESKTOP STREAMING VIA VD/STEAM/META & DOES NOT STABILIZE - THIS HAPPENS ON BOTH 5 & 6GHZ CHANNELS

As another user had mentioned in the post - https://community.tp-link.com/us/home/threads/topic/845440
"Setting the 6G to 20/40/80 hz enables to quest pro to use it without issue, both headsets can't be on 6G at the same time though otherwise they have latency issues"

This seems to hold true, however; I'd connected my phone to the 6ghz channel to test if it was possibly an issue due to the device type (Multiple quests, etc) but this doesn't seem to be the case. Having another device connected to the 6ghz channel at all, regardless of usage seems to cause instability on the network. This happens regardless of TWT / MU-MIMO being enabled or disabled.
(Note that smart connect is disabled and all SSIDs are separate to avoid confusion)

I then tested with another smartphone to make sure (Pixel 6) and yet again, had the exact same issue. It doesn't seem to be a factor of what the device is doing, more that it's on the same channel at all. From what I've tested, manually choosing the channel (disabling PSC & choosing best channel in regards to least interference) also doesn't seem to make a difference in this case.

As mentioned, this is on the current Beta firmware so mileage may vary, but PLEASE sort this out. It's insanely frustrating & losing a 2.5gbps port by purchasing an AXE75 instead, just to have a stable experience, is such a headache.