Forum Discussion

Zangoose's avatar
Zangoose
Joining in
10 months ago

Network Issue between Virgin and AWS?

Hello,


Since last night I have noticed certain services are unable to function fully that seems to use AWS. Such as FlightRadar24, Signal, Slack etc.

In terms of FlightRadar24 the website loads but no planes show. It seems the planes load via data-feed.flightradar24.com which points to: ae6b5a65c402225de.awsglobalaccelerator.com  and when you do a traceroute towards that host it timeout after hitting the Virgin's first Core hop as shown in these results.

I compared this to a friend who also uses Virgin Media and they were able to do a successful trace. Is anyone else having any issues connecting towards certain services that may also use AWS?

I've tried rebooting the Hub, changing DNS servers but doesn't help. I can only get it to work If I use my phone and use 5G.

Here is the traceroute: 

Tracing route to ae6b5a65c402225de.awsglobalaccelerator.com [99.83.188.155]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms [192.168.1.1]
2 9 ms 10 ms 9 ms 10.53.38.173
3 10 ms 9 ms 9 ms bagu-core-2b-ae91-650.network.virginmedia.net [80.5.162.69]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.

  • Client62's avatar
    Client62
    Alessandro Volta

    Flight Radar 24 is working for us.

    This is the result from our VM connection in Colchester

    C:\Users\Philip>tracert 99.83.188.155

    Tracing route to ae6b5a65c402225de.awsglobalaccelerator.com [99.83.188.155]
    over a maximum of 30 hops:

    1 2 ms 2 ms 1 ms 192.168.0.1
    2 * * * Request timed out.
    3 12 ms 13 ms 12 ms nrth-core-2a-ae54-650.network.virginmedia.net [213.105.64.77]
    4 * * * Request timed out.
    5 15 ms 15 ms 15 ms brhm-ic-3-ae0-0.network.virginmedia.net [62.253.174.126]
    6 * * * Request timed out.
    7 * * * Request timed out.
    8 * * * Request timed out.
    9 * * * Request timed out.
    10 * * * Request timed out.
    11 * * * Request timed out.
    12 * * * Request timed out.
    13 20 ms 20 ms 17 ms ae6b5a65c402225de.awsglobalaccelerator.com [99.83.188.155]

    Trace complete.

    C:\Users\Philip>ping 99.83.188.155

    Pinging 99.83.188.155 with 32 bytes of data:
    Reply from 99.83.188.155: bytes=32 time=19ms TTL=247
    Reply from 99.83.188.155: bytes=32 time=19ms TTL=247
    Reply from 99.83.188.155: bytes=32 time=17ms TTL=247
    Reply from 99.83.188.155: bytes=32 time=16ms TTL=247

    Ping statistics for 99.83.188.155:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 16ms, Maximum = 19ms, Average = 17ms

     

    • ModTeam's avatar
      ModTeam
      Moderator

      Hi All, 

      we have raised this with our network support team for further investigation. This has been raised under the reference F011273523 and we'll endeavour to have any issue resolved as quickly as possible. 

      ModTeam

      • Mark19841's avatar
        Mark19841
        Tuning in

        Hi have we heard anything more on this?

        I called VM CS yesterday and said the issue was because I had a blacklisted IP. Which was a laod of rubbish. 

        I was on a call for over 4 hours. With no help whatsoever ever.

        Now 3 days out of work and still no further on.

        VM need to communicate with thier front line team. 

         

        I also checker the WA4 postcode on status checker and it says no know issues in my area. 

        But I cannot access many AWS services.

         

        Can you confirm if this is affecting WA4 

  • logan2's avatar
    logan2
    Just browsing

    Happening for me too. Really need this fixed as my work depends on numerous AWS services

    • vmrunreliable's avatar
      vmrunreliable
      Superfast

      In fairness, a visit from a virgin media technician is unlikely to resolve any issue, no matter what the cause.