[TelstraClear] Odd DNS to Google.co.nz and slow...

Forums › One New Zealand (including Vodafone, WxC, Farmside) › [TelstraClear] Odd DNS to Google.co.nz and slow...

1 | 2 | 3 | 4 | 5

3501 posts

Uber Geek

ID Verified

#529016 4-Oct-2011 13:14

Seems Snap customers are/have been suffering similar as well:
http://www.geekzone.co.nz/forums.asp?forumid=90&topicid=90670

Again showing my technical naivety (heck, I can't even spell it) but could it be related somehow.

Thanks for explaining "plethora".

It means a lot.

AliExpress

Shop now on AliExpress (affiliate link).

DonGould

3892 posts

Uber Geek

#529019 4-Oct-2011 13:19

cyril7: I see no one has posted in the GZ ISP fault log

Cyril

Some of us were trying to prove the fault first :)

But yes.

Promote New Zealand - Get yourself a .kiwi.nz domain name!!!

Check out mine - i.am.a.can.do.kiwi.nz - don@i.am.a.can.do.kiwi.nz

dets00b

60 posts

Master Geek

#529060 4-Oct-2011 14:29

I first noticed this about 3-4 weeks ago, it has been intermittent since :S

5 i-0-0-4-1.tlot-core01.bx.reach.com (202.84.142.106) 126.484 ms   125.852 ms                                126.234 ms
6 i-1-0.nwk-core01.bi.reach.com (202.84.141.125) 201.622 ms   201.688 ms   20                             1.642 ms
7 i-6-0.ulco-core01.bx.reach.com (202.84.144.142) 272.563 ms   272.379 ms   2                             72.431 ms
8 195.66.226.125 276.576 ms   276.274 ms   276.764 ms
9 209.85.255.175 286.732 ms 209.85.252.76 273.430 ms   273.794 ms
10 216.239.46.224 274.731 ms   273.824 ms   274.826 ms
11 72.14.238.107 274.842 ms   274.591 ms   280.127 ms
12 64.233.174.144 274.601 ms 64.233.174.146 269.970 ms   271.074 ms
13 64.233.174.179 327.587 ms 64.233.174.177 326.878 ms   332.206 ms
14 209.85.255.35 327.159 ms   326.467 ms   327.609 ms
15 64.233.175.0 331.779 ms   331.488 ms   330.269 ms
16 66.249.95.167 427.044 ms   427.241 ms   427.045 ms
17 72.14.237.51 427.754 ms   427.243 ms   427.505 ms
18 74.125.237.50 426.929 ms   427.644 ms   427.035 ms

freitasm

BDFL - Memuneh
79131 posts

Uber Geek

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#529080 4-Oct-2011 14:55

Yes, interesting... http://www.geekzone.co.nz/fault.asp

DonGould

3892 posts

Uber Geek

#529085 4-Oct-2011 14:59

freitasm: Yes, interesting... http://www.geekzone.co.nz/fault.asp

Yip, that's a very under used resource.

D

Promote New Zealand - Get yourself a .kiwi.nz domain name!!!

Check out mine - i.am.a.can.do.kiwi.nz - don@i.am.a.can.do.kiwi.nz

freitasm

BDFL - Memuneh
79131 posts

Uber Geek

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#529092 4-Oct-2011 15:09

This is what I get on TelstraClear cable:

Tracing route to www.l.google.com [74.125.237.20]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms srp521w [192.168.2.1]
2 * * * Request timed out.
3 8 ms 7 ms 7 ms lo0.internet.ivpn.pe25.telstraclear.net [218.101.61.124]
4 * * * Request timed out.
5 23 ms 24 ms 25 ms ie1-g-0-0-0.telstraclear.net [203.98.50.1]
6 24 ms 18 ms 19 ms ge-0-2-0-1.xcore1.acld.telstraclear.net [203.98.50.251]
7 17 ms 17 ms 17 ms 203.167.233.10
8 180 ms 149 ms 170 ms i-0-6-4-1.tlot-core01.bx.reach.com [202.84.142.114]
9 219 ms 217 ms 217 ms i-5-1.nwk-core01.bi.reach.com [202.84.141.137]
10 289 ms 289 ms 289 ms i-6-2.ulco-core01.bx.reach.com [202.84.140.46]
11 298 ms 325 ms 293 ms 195.66.226.125
12 292 ms 292 ms 290 ms 209.85.252.76
13 297 ms 297 ms 321 ms 216.239.46.224
14 292 ms 315 ms 297 ms 72.14.238.105
15 292 ms 293 ms 327 ms 64.233.174.146
16 344 ms 348 ms 368 ms 64.233.174.179
17 354 ms 359 ms 344 ms 209.85.255.57
18 348 ms 348 ms 358 ms 64.233.175.0
19 459 ms 448 ms 447 ms 66.249.95.167
20 444 ms 449 ms 455 ms 72.14.237.47
21 444 ms 445 ms 445 ms 74.125.237.20

This is what I get on 2degrees:

Tracing route to www.l.google.com [74.125.237.51]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 64 ms 58 ms 68 ms 172.21.32.11
4 92 ms 58 ms 58 ms 172.21.32.2
5 58 ms 58 ms 58 ms 18-0-148-118.nzcomms.co.nz [118.148.0.18]
6 64 ms 58 ms 58 ms 2-0-148-118.nzcomms.co.nz [118.148.0.2]
7 65 ms 58 ms 59 ms 242-7-148-118.nzcomms.co.nz [118.148.7.242]
8 77 ms 59 ms 58 ms 111-69-27-65.core.snap.net.nz [111.69.27.65]
9 59 ms 59 ms 58 ms 203.167.233.10
10 205 ms 199 ms 198 ms i-0-6-4-0.tlot-core01.bx.reach.com [202.84.142.110]
11 260 ms 258 ms 258 ms i-5-1.nwk-core01.bi.reach.com [202.84.141.137]
12 349 ms 338 ms 339 ms i-6-2.ulco-core01.bx.reach.com [202.84.140.46]
13 349 ms 348 ms 349 ms 195.66.226.125
14 348 ms 368 ms 442 ms 209.85.252.76
15 355 ms 349 ms 349 ms 216.239.46.224
16 365 ms 339 ms 339 ms 72.14.238.105
17 354 ms 359 ms 338 ms 64.233.174.146
18 410 ms 398 ms 408 ms 64.233.174.179
19 401 ms 409 ms 419 ms 209.85.255.57
20 403 ms 399 ms 399 ms 64.233.175.0
21 504 ms 499 ms 499 ms 66.249.95.167
22 502 ms 498 ms 489 ms 72.14.237.51
23 493 ms 499 ms 499 ms 74.125.237.51

Trace complete.

nickt

90 posts

Master Geek

#529625 5-Oct-2011 15:34

203.167.233.10 is common to those two traces, which the MaxMind GeoIP database says is run by Telstraclear in Auckland. I'm seeing the same 450-500ms latency to google sites too, using TelstraClear DSL. Routing to California via Hong Kong and London is clearly suboptimal!

captk

19 posts

Geek

#529659 5-Oct-2011 16:08

nickt: 203.167.233.10 is common to those two traces, which the MaxMind GeoIP database says is run by Telstraclear in Auckland. I'm seeing the same 450-500ms latency to google sites too, using TelstraClear DSL. Routing to California via Hong Kong and London is clearly suboptimal!

Hi nickt,

Please report a fault here: http://www.geekzone.co.nz/fault.asp

That way we can show we're not the only ones with the problem.

Cheers
j

Screeb

698 posts

Ultimate Geek

#529663 5-Oct-2011 16:11

I'm also seeing the same thing (cable). Very odd. Seems like a REACH issue.

freitasm

BDFL - Memuneh
79131 posts

Uber Geek

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#529667 5-Oct-2011 16:15

Reported on http://www.geekzone.co.nz/fault.asp as I am seeing the same on cable.

freitasm

BDFL - Memuneh
79131 posts

Uber Geek

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#529686 5-Oct-2011 16:34

Use a nifty tool to check the tracert on a map:

freitasm

BDFL - Memuneh
79131 posts

Uber Geek

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#529689 5-Oct-2011 16:37

Giving this issue a bit more visibility: www.geekzone.co.nz/freitasm/7819

floydbloke

3501 posts

Uber Geek

ID Verified

#529691 5-Oct-2011 16:47

Thanks for this and the cool graphic. You might want to review the grammar/typing in the 2nd paragraph of your blog entry.

Edit. Sorry just re-read and now understand the context. Reader's error on my behalf.

Thanks for explaining "plethora".

It means a lot.

jonherries

1388 posts

Uber Geek

Trusted

Subscriber

#529695 5-Oct-2011 16:54

On our corporate network (not my job to worry about it so I won't post it on the faults log) Telstraclear is our ISP, and it is going via china to the US.

Will check my cable from home tonight, and post a fault if consistent.

Jon

Proxy trace to
google.com
24 hops / 23.3 seconds

New Zealand

1. 202.0.124.3 New Zealand

2. 203.97.41.178 New Zealand

3. clix.net.nz New Zealand

4. telstraclear.net New Zealand

5. telstraclear.net

6. 210.80.27.6

7. ALTER.NET

8. ALTER.NET United States

9. ALTER.NET United States

10. ALTER.NET United States

11. ALTER.NET United States

12. ntt.net United States

13. ntt.net United States

14. ntt.net United States

15. dreamhost.com

16. dreamhost.com United States

17. dreamhost.com United States

18. coresite.com United States

19. 64.233.174.31 United States

20. 64.233.174.192 United States

21. 64.233.174.205 United States

22. 209.85.250.61 United States

23. 64.233.174.119 United States

24. 74.125.224.145
~14,959 miles traveled

freitasm

BDFL - Memuneh
79131 posts

Uber Geek

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#529697 5-Oct-2011 16:55

A disclaimer I put in my blog post:

Update: Yes, someone mentioned it's the Internet, if things are not well, alternative routes and all. Yes, I know that. Still, if we are so far away from content that 200ms influences the results, it would be good if a high quality network could make sure things were taking the optimal path and only use the fallback as a. fallback, not something that happens for days/weeks.

1 | 2 | 3 | 4 | 5