This is just using Android's DNS resolver, which is failing for twitter.com

Might be interesting to understand why that is failing for the sake of improving Android's resolver, but not sure if there is much we can do beyond using Chrome's built-in resolver for this case.

A tcpdump covering failed requests, and an Android bugreport would help diagnose the system resolver issue, but not much Chrome can do in this case (well we could "fall-forward" to our internal resolver but that seems heavy handed for this case, and I have no evidence the DNS server wouldn't give back the same result to our internal resolver).

Assume there is no way to nudge on the device except reboot the device, right?

Cycle airplane mode on and off to clear all DNS caches.

Closing this out, feel free to reopen with more info.

As #1 says, this would either require an Android platform-level fix (if that's the root issue) or something where we use Chrome's resolver on Android (a possibility).