Himu Mitra Update: recurring Jio DNS failure, with new affected-connection evidence (screenshots dated 27 September 2026; displayed local times approximately 00:46–01:11, timezone not independently verified). The affected connection is reported to be in Chennai, India. Later controlled comparisons show Airtel working; this report now focuses on Jio. On the same affected Jio hotspot / Windows laptop: 1. nslookup -type=A www.hhcare.eu.com Default resolver 10.191.189.227 returns Server failed / SERVFAIL. 2. nslookup -type=A www.hhcare.eu.com 198.51.44.13 Succeeds: 64.29.17.1 and 64.29.17.65. 3. nslookup -type=A www.hhcare.eu.com 198.51.45.13 Succeeds: 216.198.79.1 and 64.29.17.1. 4. Google Public DNS (8.8.8.8) resolves the custom hostname. Changing Android Private DNS to dns.google immediately restores access to the main domain on the same Jio phone. 5. Earlier, from the affected Jio connection: curl.exe -I --resolve www.hhcare.eu.com:443:216.198.79.1 --connect-timeout 8 --max-time 15 https://www.hhcare.eu.com/login returned HTTP/1.1 200 OK with Server: Vercel and X-Matched-Path: /login. This establishes reachability of that endpoint, not complete authentication coverage. Additional resolver comparisons: - NS eu.com via 10.191.189.227: timeout. - NS hhcare.eu.com via 10.191.189.227: Server failed. - Control NS google.com via 10.191.189.227: timeout too, so the NS-query failure is not evidence of an eu.com-specific block. - NS eu.com via 8.8.8.8: succeeds, returning ns1/ns2/ns3/ns4.centralnic.net. - nslookup -vc -type=NS eu.com 10.191.189.227: ends with Unspecified error. This generic error does not by itself prove TCP filtering. Public checks from a separate, unaffected connection found matching Vercel delegation at all four eu.com parent nameservers, successful A/SOA answers over UDP and TCP at both Vercel authoritative servers, and no child DS answer for hhcare.eu.com. These are not tests of the Jio recursive servers’ outbound path. The domain currently uses ns1.vercel-dns.com / ns2.vercel-dns.com; earlier CNAME observations in the initial post are historical, not a claim about the current wire response. Could the DNS/network team investigate authoritative reachability, response handling, filtering/rate limits or interoperability for Jio recursive-resolver traffic to this zone? 10.191.189.227 is the private resolver address visible to the subscriber, NOT the resolver’s public egress IP. We do not yet have the recursive backend/egress IP or EDE diagnostics. Please advise what operator-side evidence is needed and whether there is a supported remediation without requiring every visitor to change DNS. We are also pursuing Jio DNS support. Root cause remains unconfirmed; a universal Jio block is not established.
Himu Mitra Configuration update for investigators: at approximately 2026-09-26T19:53:21.965Z we changed the authoritative DNS delegation from Vercel to Cloudflare as a controlled diagnostic experiment. New nameservers are brian.ns.cloudflare.com and serenity.ns.cloudflare.com. Website hosting remains on the same Vercel deployment, with Cloudflare proxying OFF (DNS-only). The previous test results in post 2 were collected BEFORE this migration. We preserved the original Vercel zone for rollback, copied mail/verification/CAA records, and verified the new authoritative records on both servers. All four eu.com parent servers and Google/Cloudflare public resolvers now show the new delegation. Vercel still reports Valid Configuration, and HTTPS /login returned 200 in our check. Affected-Jio retesting without Private DNS/VPN is still pending. This is not a claim that the carrier issue is resolved. Please retain the earlier evidence when investigating the original recursive/authoritative path.
Larstraningsrapporter 8359 Same issue here. The ChatGPT ↔ Vercel MCP integration worked normally for me until yesterday evening, then suddenly stopped working across all ChatGPT chats. In my case: * list_teams returns teams: [] * all three Vercel projects on my account are affected * OAuth/reconnect succeeds * uninstalling and reinstalling/reconnecting the Vercel integration did not help * my Vercel dashboard works normally * all projects are visible and deployments continue to work * Hobby usage is far below all limits So this looks like the same OAuth/team-scope/MCP authorization problem described above, not a project-specific or quota issue. Happy to provide any additional details if useful.
Khaled0ezz 6568 I see the same `list_teams` result on a Hobby workspace: `{"teams":[]}`. The ChatGPT connection is active, and Vercel Account Settings lists “ChatGPT by Vercel MCP” with permission to read team data. `list_projects()`, `get_project({idOrName:"prj_xxx"})`, and `list_deployments({projectId:"prj_xxx"})` succeed without `teamId`; the project reports `accountId:"team_xxx"`. Supplying that `teamId` to the same calls returns 403 with “re-authenticate to this scope.” Team SAML and enforced 2FA are disabled. Reconnecting and reinstalling did not help. Is this team scope intentionally unsupported on Hobby, or can the MCP team investigate the effective OAuth grant? I can provide exact IDs privately.
Jbj11unh Additional diagnostic: I bypassed list_teams and called list_projects directly using my actual Vercel Team ID. The MCP request returned 403 Forbidden with: “Not authorized: Trying to access resource under scope jbj11unh. You must re-authenticate to this scope or use a token with access to this scope.” This happens even though the ChatGPT by Vercel MCP OAuth authorization screen explicitly displayed my team (jbj11unh's projects), and I clicked Allow Access. This appears to confirm that the team scope is not being retained or applied to the ChatGPT MCP OAuth grant. Another user in this thread appears to be seeing the same behavior when explicitly providing a Team ID.
system While a member of our team prepares to jump in, you might find your answer even faster in our community resources. - Official Documentation: https://v0.app/docs - The v0 expert walkthrough: https://community.vercel.com/t/become-a-v0-expert/5981 - Watch v0 in Action: https://community.vercel.com/live#v0
NotAVibeCoder Weird. I don't see any responses to my query. That must be a bug.
NotAVibeCoder Whoa, I still can't see any responses. What is causing this bug?
system The domain troubleshooting guide can help with most custom domain configuration issues. You might be able to use that guide to solve it before a human is available to help you. Then you can come back here and share the answer for bonus points. https://vercel.com/docs/domains/troubleshooting
Amy Egan Hey @yevheniia98! I asked the support team for help with this, and I believe they sent an update on the support case you opened. Please let us know if you still have trouble with your domain
system The domain troubleshooting guide can help with most custom domain configuration issues. You might be able to use that guide to solve it before a human is available to help you. Then you can come back here and share the answer for bonus points. https://vercel.com/docs/domains/troubleshooting
Hali Is anyone there
system Hi there! I'm just a bot here to share some info that might help you before a human arrives. If your account is eligible, you can use our new self-service recovery flow: 1. Go to vercel.com/login 2. Choose to sign in using the email + one-time password (OTP) option. 3. Select Use another sign-in method 4. Verify your identity using the GitHub, GitLab, or Bitbucket account previously linked to your Vercel account 5. Follow the remaining prompts to complete the recovery process If you've ever set up a passkey, possibly on another device, you can use that to get back into your account and update 2FA settings yourself. You can also use recovery codes if you've stored those in a safe place that you can still access. If you are unable to access your account using the steps above, you can open a support case using the Start 2FA recovery option on the Two-Factor Authentication login screen. **Please do not publicly post account details, like your email address, that could help an attacker gain access to your account in the future.** There's no need to open an additional case if you already have one open. Thanks for your patience while the team works to resolve all cases as quickly as possible while keeping everyone’s accounts safe and secure. A human should be here soon to help.
AayZen Thanks for the information. I’ve already tried the self-service recovery steps mentioned above. I can successfully sign in through my previously linked GitHub account, but Vercel still asks for the 2FA code afterward. Unfortunately, I no longer have access to my authenticator, and I don’t have a passkey or recovery codes. I have already submitted the 2FA recovery request and received case **#01563224**. I also accidentally submitted it a second time and received **#01577866**. Could a member of the support/security team please review my existing recovery case and help me complete the ownership verification process? I still have access to the verified email address associated with my Vercel account and can provide any required information privately. Thank you for your help.
system The domain troubleshooting guide can help with most custom domain configuration issues. You might be able to use that guide to solve it before a human is available to help you. Then you can come back here and share the answer for bonus points. https://vercel.com/docs/domains/troubleshooting
Zsofia Matrai I need to talk to a human please. I don't understand this.