07-02-2021 10:56 AM
Since you mention phone support I won't expect anything useful from scheduled vz phone callback then. Also I'd add that chat support is not up to task for this kind of problem either. All they can do appears to be reading from their monitoring system giving them good/bad and when it's "good" customers just get told to "factory resetting your router" or "reboot your router". PS: I'm new FIOS customer for 2mos just switched from Spectrum
Thanks a bunch with the tip I'll try twitter first.
07-02-2021 12:26 PM
To be honest, I suspect you'll have a hard time getting any of their support channels to understand your request. Their support staff are setup to handle the vast majority of users, which are people who don't know an IP address from a router. But we know what will happen if you don't even try their support - nothing. And, you may get a support tech who is able to understand and escalate the issue.
07-02-2021 12:55 PM
I guess third time's the charm. After two chats and one scheduled call back, the last one I communicate with over the phone actually log a ticket for me. Hours spent on this and it's so hard to get proper support.
A repair ticket <XXXXXXX> has been created for your service trouble and will be resolved on 07/03 by 5pm. Repair charges may apply.
If you need to reschedule your appointment or if your service is now working properly, just let us know by clicking verizon.com/managerepair.
07-02-2021 02:05 PM
Hello zeng. Since your issue is not hardware-related, it may be out of scope for the official tech support. I would suggest you to cancel the repair ticket as it may incur a $99 tech visit fee to your account.
07-02-2021 04:14 PM
Did they open an internal case that escalates the issue, or did the schedule a tech visit. If they scheduled a tech visit, cang_household has given you excellent advise. A field tech isn't going to do anything with this issue. If someone comes to your home, they will do nothing but shrug their shoulders and you may be charged for the visit.
Like I said, phone support doesn't understand issues like this. Use the twitter or VZDirect link I posted earlier, they are much better with stuff like this.
07-02-2021 04:23 PM
I received the following:
PING 126.96.36.199 (188.8.131.52) 56(84) bytes of data.
From 184.108.40.206 icmp_seq=156 Destination Net Unreachable
From 220.127.116.11 icmp_seq=244 Destination Net Unreachable
From 18.104.22.168 icmp_seq=311 Destination Net Unreachable
Destination Net Unreachable instead of Destination Host Unreachable means Verizon layer 3 does not know how to route to the subnet. I will do further testing to see whether the peering layer 3s do not know how to route either. I did find the IPs belong to Tencent. Are you trying to access certain resources on WeiXin or QQ?
07-02-2021 05:27 PM - edited 07-02-2021 05:30 PM
I think what happened was that over the phone, FIOS support opened that ticket to their 'network' team.
And I followed the link managerepair to see if cancellation was necessary. Turns out this is a different portal than their FIOS support. I made clear to them that this is internal VZ issue and there'd be no charge to me. So ticket is left open.
I used Twitter but no one responded to me.
So far I check VZ/Sprint/ATT/HE.NET. Previous two do not have the routes while the last two do. Lots and lots of routes appear to be missing besides
Yeah those subnets hold advertisement video for Tencent I find out by using tcpdump to monitor DNS/TCP traffic.