Dog pinging

  • Hey - turns out IRC is out and something a little more modern has taken it's place... A little thing called Discord!

    Join our community @ https://discord.gg/JuaSzXBZrk for a pick-up game, or just to rekindle with fellow community members.

Quasi^

Quasi^

Me.
Oct 26, 2002
3,410
48
Behind a crate
I noticed today my ping was going anywhere from 80 - 220 :/

My ping is usually around 25-30 and when I did a traceroute to dog std this is what I found:

Code: 
traceroute to 213.230.216.2 (213.230.216.2), 30 hops max, 38 byte packets
 1  10.0.0.1 (10.0.0.1)  2.278 ms  0.520 ms  0.409 ms
 2  10.90.0.1 (10.90.0.1)  9.506 ms  14.963 ms  13.394 ms
 3  osr01craw-v15.network.virginmedia.net (62.30.128.40)  11.575 ms  8.523 ms  9.754 ms
 4  osr01croy-tenge71.network.virginmedia.net (62.30.242.45)  9.895 ms  16.952 ms  14.925 ms
 5  brnt-bb-1a-ae2-0.network.virginmedia.net (195.182.178.82)  20.049 ms  9.461 ms  8.847 ms
 6  brnt-bb-1b-ae0-0.network.virginmedia.net (213.105.174.226)  9.422 ms  15.299 ms  10.127 ms
 7  telc-ic-1-as0-0.network.virginmedia.net (62.253.185.74)  20.134 ms  14.545 ms  12.657 ms
 8  ldn-b2-link.telia.net (213.248.100.97)  63.396 ms  59.424 ms  61.115 ms
 9  ldn-tch-i2-link.telia.net (80.91.250.214)  63.898 ms  71.947 ms  61.152 ms
10  ldn-tch-i1-link.telia.net (80.91.250.217)  86.828 ms  81.737 ms  70.181 ms
11  datahop-116558-ldn-tch.c.telia.net (213.248.100.178)  66.842 ms  70.844 ms  76.682 ms
12  * * *
13  * * *

Has dog servers moved? Or is this some more lameness from virginmedia? :/
 
Think its your isp route m8

Code: 
Pinging 213.230.216.2 with 32 bytes of data:
Reply from 213.230.216.2: bytes=32 time=13ms TTL=123
Reply from 213.230.216.2: bytes=32 time=12ms TTL=123
Reply from 213.230.216.2: bytes=32 time=12ms TTL=123
Reply from 213.230.216.2: bytes=32 time=13ms TTL=123

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



Tracing route to 213.230.216.2 over a maximum of 30 hops

  1     1 ms     1 ms     1 ms  192.168.1.254
  2    10 ms    11 ms    11 ms  93-96-183-1.zone4.bethere.co.uk [93.96.183.1]
  3    12 ms    12 ms    12 ms  10.1.3.50
  4    12 ms    12 ms    13 ms  ae0-1234.rt2.the.uk.goscomb.net [195.66.224.226]

  5    11 ms    13 ms    13 ms  213.230.194.161
  6    13 ms    13 ms    13 ms  213.230.216.2

Trace complete.
 
I've posted on the vm forum. Prhaps they can shed some light. I don't how long they've been using telia.net but no doubt they will say the problem is with them.
 
Yes, it's been the same for me for just over a week now. Where did you post? Think I might like to add my 2p.

I can adjust reverse routing, but outgoing is out of my control.

Code: 
Tracing route to 213.230.216.2 over a maximum of 30 hops

  1     7 ms     7 ms     4 ms  192.168.1.1
  2    25 ms    11 ms     9 ms  10.100.152.1
  3    10 ms    11 ms    26 ms  pool-cam-1b-ge97.network.virginmedia.net [80.5.1
68.161]
  4    14 ms    22 ms    47 ms  sotn-core-1b-ge-113-0.network.virginmedia.net [8
0.4.225.165]
  5    35 ms    34 ms    41 ms  glfd-bb-1b-ae3-0.network.virginmedia.net [212.43
.163.153]
  6    17 ms    19 ms    19 ms  brnt-bb-1a-as3-0.network.virginmedia.net [212.43
.163.106]
  7    20 ms    16 ms    26 ms  brnt-bb-1b-ae0-0.network.virginmedia.net [213.10
5.174.226]
  8    21 ms    18 ms    34 ms  telc-ic-1-as0-0.network.virginmedia.net [62.253.
185.74]
  9    35 ms    28 ms    21 ms  ldn-b2-link.telia.net [213.248.100.97]
[COLOR=Red][B] 10    92 ms   206 ms   154 ms  ldn-tch-i2-link.telia.net [80.91.250.214][/B][/COLOR]
 11    30 ms    42 ms    19 ms  ldn-tch-i1-link.telia.net [80.91.250.217]
 12    37 ms    39 ms    29 ms  datahop-116558-ldn-tch.c.telia.net [213.248.100.
178]
 13    44 ms    21 ms    42 ms  213.230.216.2

Trace complete.
Edit:

I checked reverse routing - we peer directly on to the old NTL network, so it's only 4 hops to VM.

Code: 
Tracing route to cpc3-pool6-0-0-cust212.sotn.cable.ntl.com [80.7.200.213]
over a maximum of 30 hops:

  1    22 ms    <1 ms    <1 ms  2124.gi1-2.rt0.the.core.lchost.net [213.230.216.
1]
  2    <1 ms    <1 ms    <1 ms  gi3-37.telehouse-east.core.enta.net [62.249.255.
77]
  3    <1 ms    <1 ms    <1 ms  te5-1.telehouse-east2.core.enta.net [87.127.236.
98]
  4    <1 ms    <1 ms    <1 ms  tele-ic-1-ge-300-0.network.virginmedia.net [212.
250.14.89]
  5     2 ms     2 ms     2 ms  nrth-bb-1b-as0-0.network.virginmedia.net [62.253
.184.1]
  6     *        *        *     Request timed out.
  7     4 ms     4 ms     4 ms  glfd-bb-1b-ae0-0.network.virginmedia.net [213.10
5.172.6]
  8     *        *        *     Request timed out.
  9     8 ms     8 ms     9 ms  pool-cam-1b-ge-wan32.network.virginmedia.net [80
.4.225.166]
 10     8 ms     7 ms     9 ms  pool-cmts-06-ge02.network.virginmedia.net [80.5.
168.162]
 11    26 ms    25 ms    15 ms  ****-****6-0-0-cust***.sotn.cable.ntl.com [80.7.
***.***]

I guess VM are just routing a massive netblock through Telia, and we're caught up in the middle?
 
Last edited:
You must log in or register to reply here.
Top Bottom
Back