All mobile traffic stalled (incredibly slow to load)

I've been using NextDNS mostly without issue for a year now. I just got a new Android phone and when using NextDNS with it any kind of internet traffic can be completely blocked for up to a minute or two as if I have no connectivity. Then all of a sudden the page will load or the app will advance/refresh as if the connection resurrected. Happens across all traffic, whether in Chrome browser or Samsung Internet or an app (e.g. trying to call a Lyft/Uber).

I had my old phone and new phone in hand at the same time and one had an issue and the other did not. The issue sounds very reminiscent of this one. Other computers in the house don't seem to have the issue but my roommates phone also had same/similar issue recently that seems to have self-resolved.

This happens whether I'm at home on wifi (where NextDNS IPv4 addresses are set on router), on mobile networks, or on other wifi networks, so it's not network specific, and seems to be something about the combination of this device while NextDNS is enabled. I can 100% resolve the issue by putting my phone on mobile network and deactivating NextDNS in Android settings. Note I do not use a VPN.

Here are the outputs from test.nextdns.io and ping.nextdns.io from my phone's Chrome browser:

do-sfo                    4 ms  (ultralow1)

  zepto-sjc (IPv6)          5 ms  (anycast2)

  zepto-sjc                 5 ms  (anycast2)

  do-sfo (IPv6)             6 ms  (ultralow1)

  vultr-lax (IPv6)         11 ms  (anycast1)

  vultr-lax                13 ms

  anexia-lax               14 ms

  zepto-lax                15 ms

  anexia-lax (IPv6)        16 ms

  vultr-sjc                17 ms  (anycast1, ultralow2)

  zepto-lax (IPv6)         17 ms

  frantech-las             20 ms

  frantech-las (IPv6)      21 ms

  smarthost-las            21 ms

  smarthost-las (IPv6)     21 ms

  directspace-pdx          22 ms

■ vultr-sjc (IPv6)         23 ms  (ultralow2)

  tier-pdx (IPv6)          29 ms

  tier-pdx                 48 ms

  directspace-pdx (IPv6)   error

{

 "status": "ok",

 "protocol": "DOT",

 "profile": "fp5d6c7c298fdd21ef",

 "client": "2604:5500:c02a:7b00:185e:8b63:cc77:757",

 "srcIP": "2604:5500:c02a:7b00:185e:8b63:cc77:757",

 "anycast": false,

 "server": "vultr-sjc-1",

 "clientName": "unknown-dot",

 "deviceName": "ZFold4",

 "deviceID": "EBSCU"

}

I ran the diagnostic tool, but note it was run from a Windows machine not experiencing the issue.

https://nextdns.io/diag/df0d0ef0-2708-11ed-9005-e7c8d61c9694