Hi there,I'm currently having a bit of an issue with any device in my house connecting through the VM router that I have. I've tried resetting it entirely and leaving it as default and i've tried changing my dns to avoid VM's DNS to 1.1.1.1 / 1.0.0.1 amongst others.However the issue i'm facing seems to be a routing problem, websites and IP addresses at random that I've confirmed others can connect to seem to be impossible for me to reach as of ~9am thismorning.➜ traceroute forums.zwift.com traceroute to gozwift.hosted-by-discourse.com (184.105.99.75), 64 hops max, 40 byte packets 1 192.168.0.1 (192.168.0.1) 8.065 ms 7.443 ms 8.332 ms 2 * * * 3 belf-core-2a-ae20-650.network.virginmedia.net (62.254.33.53) 21.755 ms 20.277 ms 18.167 ms 4 * * * 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * ... Repeat foreverAnd another:traceroute: Warning: app.netdata.cloud has multiple addresses; using 44.207.131.212 traceroute to main-ingress-545609a41fcaf5d6.elb.us-east-1.amazonaws.com (44.207.131.212), 64 hops max, 40 byte packets 1 192.168.0.1 (192.168.0.1) 8.204 ms 6.379 ms 7.615 ms 2 * * * 3 belf-core-2a-ae20-650.network.virginmedia.net (62.254.33.53) 16.438 ms 18.409 ms 16.762 ms 4 * * * 5 * * * 6 * * * 7 * * * ... repeat foreverI spent quite a while debugging my internal network but I dont see an issue there. The fact that it's getting out to VM and then failing makes me think it's not an issue on my side. I've also made no changes to my internal network in weeks aside from resetting the router to defaults thismorning in the hopes that it'd fix the issue.Is there anything that can be done?

Hi All, We're sorry to hear that you've been having some problems accessing certain website. We've raised this with our network team and they have raised this issue under the ticket number F011338432. We're glad to hear that this issue is resolved for some of you, and our team are continuing to investigate to ensure this is fixed as quickly as possible. ModTeam

17 Replies

linwelin

On our wavelength

11 months ago

I am using a wired connection but i cant seem to connect to some websites, for instance www.x.com done a ping and tracert:

C:\Users\yonat>ping www.x.com

Pinging x.com [104.244.42.193] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 104.244.42.193:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Users\yonat>tracert www.x.com

Tracing route to x.com [104.244.42.193]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 * * * Request timed out.
3 11 ms 9 ms 11 ms belf-core-2a-ae20-650.network.virginmedia.net [62.254.33.53]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.

Does anything look wrong with this?

Router status

3.0 Downstream channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

1	331000000	6.4	43	QAM 256	25
2	139000000	1.8	41	QAM 256	1
3	147000000	2.4	42	QAM 256	2
4	155000000	2.9	39	QAM 256	3
5	163000000	3.2	42	QAM 256	4
6	171000000	3.3	42	QAM 256	5
7	179000000	3.5	42	QAM 256	6
8	187000000	3.8	41	QAM 256	7
9	195000000	4.3	42	QAM 256	8
10	203000000	4.6	42	QAM 256	9
11	211000000	4.9	43	QAM 256	10
12	219000000	4.9	43	QAM 256	11
13	227000000	4.7	42	QAM 256	12
14	235000000	4.7	42	QAM 256	13
15	243000000	4.9	42	QAM 256	14
16	251000000	5	43	QAM 256	15
17	259000000	5.1	43	QAM 256	16
18	267000000	5	43	QAM 256	17
19	275000000	4.8	43	QAM 256	18
20	283000000	5	43	QAM 256	19
21	291000000	5.5	43	QAM 256	20
22	299000000	5.8	43	QAM 256	21
23	307000000	6.1	43	QAM 256	22
24	315000000	6.3	43	QAM 256	23
25	323000000	6.4	43	QAM 256	24
26	339000000	6.8	42	QAM 256	26
27	347000000	7	42	QAM 256	27
28	355000000	7	43	QAM 256	28
29	363000000	6.9	43	QAM 256	29
30	371000000	7.1	43	QAM 256	30
31	379000000	7.3	43	QAM 256	31

3.0 Downstream channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors

1	Locked	43	3089	7005
2	Locked	41	84611	5427
3	Locked	42	219450	7657
4	Locked	39	41583	6894
5	Locked	42	35716	10583
6	Locked	42	86911	28493
7	Locked	42	56673	632
8	Locked	41	17055	24714
9	Locked	42	5435	7375
10	Locked	42	6243	13713
11	Locked	43	7454	23247
12	Locked	43	6932	19866
13	Locked	42	311	408
14	Locked	42	2483	4589
15	Locked	42	4618	8654
16	Locked	43	234	405
17	Locked	43	220	286
18	Locked	43	207	313
19	Locked	43	3950	8206
20	Locked	43	801	1218
21	Locked	43	521	763
22	Locked	43	117	132
23	Locked	43	151	207
24	Locked	43	729	1166
25	Locked	43	490	761
26	Locked	42	2108	5095
27	Locked	42	2017	4792
28	Locked	43	247	458
29	Locked	43	310	525
30	Locked	43	2086	4815
31	Locked	43	3206	8282

3.1 Downstream channels

Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)

1840

QAM 4096

1108

3.1 Downstream channels

Channel ID Locked Status RxMER Data (dB) PLC Power (dBmV) Corrected errors (Active Profile) Uncorrectable errors (Active Profile)

Locked

6.5

5442856

2727

Router status

Refresh data

3.0 Upstream channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

0	49600000	48.5	5120	QAM 64	1
1	43100000	49.5	5120	QAM 64	2
2	36600000	50.5	5120	QAM 64	3
3	30100000	51.8	5120	QAM 64	4
4	23600000	53	5120	QAM 64	5

3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

0	ATDMA	0
1	ATDMA	0
2	ATDMA	1
3	ATDMA	1
4	ATDMA	2

3.1 Upstream channels

Channel Channel Width (MHz) Power (dBmV) FFT Type Modulation

10.4

41.2

QAM 256

3.1 Upstream channels

Channel Channel Type Number of Active Subcarriers First Active Subcarrier (Hz) T3 Timeouts T4 Timeouts

OFDMA

208

74000000

Client62

Alessandro Volta

11 months ago

I'd be concerned about the Post RS Errors aka uncorrected errors affecting all 3.0 Downstream channels,
if these numbers are still increasing the problem persists.

3.0 Downstream channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors

1	Locked	43	3089	7005
2	Locked	41	84611	5427
3	Locked	42	219450	7657
4	Locked	39	41583	6894
5	Locked	42	35716	10583
6	Locked	42	86911	28493
7	Locked	42	56673	632
8	Locked	41	17055	24714
9	Locked	42	5435	7375
10	Locked	42	6243	13713
11	Locked	43	7454	23247
12	Locked	43	6932	19866

The 3.0 Upstream power levels are testing the upper limits, this matters because it is the measure of how high the VM Hub has to transmit in order to be received at the street cabinet.

3.0 Upstream channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

0	49600000	48.5	5120	QAM 64	1
1	43100000	49.5	5120	QAM 64	2
2	36600000	50.5	5120	QAM 64	3
3	30100000	51.8	5120	QAM 64	4
4	23600000	53	5120	QAM 64	5

I can ping www.x.com at all 4 IPs listed in the DNS lookup without issue. ( from Colchester, Essex )

Client62
Alessandro Volta
11 months ago
This looks very similar :

https://community.virginmedia.com/t5/Networking-and-WiFi/Network-Routing-problem/td-p/5529071

jfaith
Joining in
11 months ago
I have the same problem I can't get teamviewer to work because I can't route to
gb-man-anx-r002.router.teamviewer.com
My traceroute is similar to yours i.e.
traceroute gb-man-anx-r002.router.teamviewer.com
traceroute to gb-man-anx-r002.router.teamviewer.com (37.252.232.101), 30 hops max, 60 byte packets
1 _gateway (192.168.0.1) 3.254 ms 4.888 ms 4.881 ms
2 * * *
3 belf-core-2a-ae20-650.network.virginmedia.net (62.254.33.53) 26.997 ms 28.985 ms 28.978 ms
4 * * *
5 * * *
...
Both forums.zwift.com and app.netdata.cloud also fail but most hosts ping without a problem.
Problem has been going on all day.
Given that we are both routing through belf-core-2a-ae20-650.network.virginmedia.net I suspect that is where the routing issue is.
- wakeuph8
  Tuning in
  11 months ago
  Thanks for that, i'm glad it's not an issue for just me! I get the same issue with your teamviewer URL. I contacted VM support via WhatsApp and they say they've also passed it along to the backend team and essentially to wait for 48 hours while they get a look.
  I'm assuming it's a common route that's broken somewhere as i've found a few others now where the same issue happens, I cant even do a "whois" on a domain or IP address without it failing because it has to contact a server it no longer can:
  
  ➜ whois virginmedia.com whois: connect(): Operation timed out
Client62
Alessandro Volta
11 months ago
belf-core-2a-ae20-650.network.virginmedia.net is also in this similar thread :

https://community.virginmedia.com/t5/Networking-and-WiFi/Problems-with-internet/td-p/5529114

Last time a similar spate of post occurred the customers were in the Warrington area.

Could there be a common locality issue again ? Belfast perhaps
- wakeuph8
  Tuning in
  11 months ago
  Great find, thanks! All signs do seem to point to a similar issue to that Warrington thread, it was actually the reason I'd posted in the first place, hopefully it's sorted quickly
  - nymins
    Tuning in
    11 months ago
    Yep, been experiencing these issues all day too. Some random websites just not working, twitter.com, battle.net to name a few. Based in Belfast.
vmissue
Joining in
11 months ago
Hey,
Having the same issues with belf-core-2a-ae20-650.network.virginmedia.net which have just started in the last 24-48 hours. Cannot access a significant portion of the internet including my work vpn endpoints, arturia.com, twitter.com and vps.ovh.net. Had a day's downtime last week for "maintenance".
Belfastgal1
Joining in
11 months ago
I'm in Belfast too. Have had problems all day on different sites. Dh upset as he can't get on to a few gaming sites that he always uses. Phoned Virgin and they said they would pass the information to an engineer.
alundy
Joining in
11 months ago
I've been having the same issues all day. Can't connect to work VPN and many websites. Eventually tracked them down to routes disappearing after hitting
belf-core-2a-ae20-650.network.virginmedia.net
Hopefully they fix this soon
wakeuph8
Tuning in
11 months ago
Just a few minutes ago my issues disappeared, hopefully everyone else has the same experience soon.
vmissue
Joining in
11 months ago
Looking better for me now also.
- ModTeam
  Moderator
  11 months ago
  Hi All,
  
  We're sorry to hear that you've been having some problems accessing certain website. We've raised this with our network team and they have raised this issue under the ticket number F011338432.
  
  We're glad to hear that this issue is resolved for some of you, and our team are continuing to investigate to ensure this is fixed as quickly as possible.
  
  ModTeam
  - nymins
    Tuning in
    11 months ago
    Issue seems to be gone for me too. Thanks for sorting!

Forum Discussion

Network Routing problem

17 Replies

Router status

Router status

Related Content

routing problems to Google DNS?

Routing problems

Network Routing Issue

Installation route

Guest network