IDnet problems?

[Technical Ben]

Routing problems atm, 19/02 @ 12:15. "Network unreachable" for almost everything.

It's not just FTTC or whatever. Got the problem here too.
I'm on asdl vanilla. Lost connections to almost everything. I could load up google and ping via IP. However, IDnet, IDNetters and any other site (including BBC) was dead. I was on IDNet DNS, did not have time or the details at hand to check OpenDNS. New thread for this problem?

PS, sounds like a strange routing thingy problem. As Google worked so well, I could view sites via the "cache" option, but could not load or even ping a single thing directly.

[minimoog]

LLU here, but all seems well again.

[Ray]

Same here I've swapped to the Google DNS servers and all is working again.

[Lance]

I've had a complete loss of routing too (not LLU). Unfortunately I was rebooting my router at the time so picked up a dodgy 172. BT IP address taking me tithe BT wholesale page.

[Baz]

hope ive done this right.

Tracing route to amazon.co.uk [178.236.6.39]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  192.***.***.*.*
  2    30 ms    30 ms    29 ms  bt1.idnet.net [212.69.63.42]
  3    30 ms    30 ms    30 ms  redbus-gw2-g0-0-300.idnet.net [212.69.63.226]
  4    30 ms    30 ms    30 ms  telehouse-gw5-5-331.idnet.net [212.69.63.6]
  5    31 ms    30 ms    31 ms  gi8-27.mpd01.lon02.atlas.cogentco.com [149.6.148
.205]
  6    31 ms    30 ms    31 ms  te7-2.ccr01.lon02.atlas.cogentco.com [130.117.50
.138]
  7    31 ms    31 ms    30 ms  te9-2.mpd02.lon01.atlas.cogentco.com [130.117.48
.153]
  8    32 ms    31 ms    30 ms  te0-3-0-5.ccr22.lon13.atlas.cogentco.com [130.11
7.0.93]
  9    32 ms    30 ms    31 ms  wind.mil01.atlas.cogentco.com [130.117.15.82]
10    32 ms    37 ms    30 ms  ae-51-51.csw1.London1.Level3.net [4.69.139.88]
11    32 ms    31 ms    31 ms  ae-57-112.ebr1.London1.Level3.net [4.69.153.117]

12    43 ms    43 ms    42 ms  ae-1-8.bar1.Dublin1.Level3.net [4.69.153.230]
13     *        *        *     Request timed out.
14     *        *        *     Request timed out.
15     *        *


what does all that mean then?

[johnny5]

Had some problems over the last half hour or so with internet very slow or pages not responding
but seems to be flying along now.

[pctech]

If you are not sure how to run a traceroute see below:

XP:

Go to Start > Run and type cmd and then click OK
at the prompt type tracert <web address you are trying to access e.g. www.bbc.co.uk> and press enter.
Wait until the command indicates 'trace complete' you will see responses from nearly all the routers en route, it is quite normal to see 'request timed out' toward the end, this indicates the presence of a firewall.
Right-click in the window and click Select All.
Press enter to copy the text.

Vista/7:

Go to Start > All Programs > Accessories > Command Prompt
Proceed as above.

Paste the results into a forum message (minus your IP if you have set this in your router, it will be 'hop' number one.)

[Bill]

Mostly OK here now, but I can't reach the tbb forums...

[armadillo]

Same here. Nothing would load, not even BBC or idnet or anything. Then BBC loaded very slowly. Then suddenly everything fine. On adlsmax via 21CN exchange. Not LLU.

I wonder why people keep trying changing DNS servers. When these problems occur, it is not even possible to access a site by entering its ip address.

e.g. type 178.236.6.39 into the browser address and it should reach amazon without going through a DNS server. Correct?

IMHO (and I know nothing), it has to be a routing problem somewhere, not necessarily within idnet's network.

[pctech]

Looking at your tracert Baz all looks ok.

Am able to access Amazon although oddly one of the routers within my ISP's network is not responding to tracert for that particular address.

If some folks are momentarily getting 172 addresses assigned to their routers it indicates a BT routing issue, one of IDNet's hostlinks flapping?

[Bill]

Mostly OK here now, but I can't reach the tbb forums...

Never mind, it would seem to be an Opera problem.

[Baz]

Looking at your tracert Baz all looks ok.

really? I have know idea what it means to be honest 

but heres another one to same site but showing different results



Tracing route to www.amazon.co.uk [178.236.6.39]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  *********
  2    30 ms    29 ms    30 ms  redbus-gw3-lo1.idnet.net [212.69.63.42]
  3    30 ms    29 ms    30 ms  redbus-gw2-g0-0-300.idnet.net [212.69.63.226]
  4    30 ms    30 ms    30 ms  telehouse-gw5-5-331.idnet.net [212.69.63.6]
  5    31 ms    31 ms    30 ms  212.69.63.246
  6    32 ms    46 ms    31 ms  v225.core1.lon1.he.net [216.66.86.45]
  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     *        *        *     Request timed out.
14     *        *        *     Request timed out.
15     *        *        *     Request timed out.
16     *        *        *     Request timed out.
17     *        *        *     Request timed out.
18     *        *        *     Request timed out.
19     *        *        *     Request timed out.
20     *        *        *     Request timed out.
21     *        *        *     Request timed out.
22     *        *        *     Request timed out.
23     *        *        *     Request timed out.
24     *        *        *     Request timed out.
25     *        *        *     Request timed out.
26     *        *        *     Request timed out.
27     *        *        *     Request timed out.
28     *        *        *     Request timed out.
29     *        *        *     Request timed out.
30     *        *        *     Request timed out.

Trace complete.

[pctech]

All I can say is it looks like IDNet's router has routed it over an alternative connection this time, is it still inaccessible to you Baz?

[Gary]

Same here, rebooted router and ended up with a 88. one  seems ok now, but using Norton DNS I could not access any pages, now using IDnet DNS.

[Steve]

I'm not seeing any issues currently using OpenDNS or IDNet DNS

[Reya]

This is my TBB meter showing the issue:



Incidentally, everything before that (excluding the thick green stripe, which is where I was using up my monthly eMusic download allowance) is fairly typical of my connection lately. I was logged into Second Life (which streams everything down to your PC, so I'd expect a few latency issues) but the constant 'hangs' in my connection are starting to drive me barmy. Every five or ten minutes or so I can't do anything for between 30 seconds to a minute. Is this indicative of another issue I might be having, and if so... what? 

[pctech]

At a complete guess it sounds like hostlink weirdness.

[Technical Ben]

Same here. Nothing would load, not even BBC or idnet or anything. Then BBC loaded very slowly. Then suddenly everything fine. On adlsmax via 21CN exchange. Not LLU.

I wonder why people keep trying changing DNS servers. When these problems occur, it is not even possible to access a site by entering its ip address.

e.g. type 178.236.6.39 into the browser address and it should reach amazon without going through a DNS server. Correct?

IMHO (and I know nothing), it has to be a routing problem somewhere, not necessarily within idnet's network.

I could access some sites, and could ping/IP connect to others. So changing DNS could have suggested to me it was just a DNS error. However one of my direct IP/TCP connections (a game ) dropped, so I doubted it was DNS related.

[pctech]

Must be some equipment misbehaving somewhere.

Hsd it only been a single person I'd have said reset your router as had that issue with my Netgear router once as it was blocking random sites.

[Baz]

All I can say is it looks like IDNet's router has routed it over an alternative connection this time, is it still inaccessible to you Baz?

seems better now PC if any thing just a tad slow at the end of the loading stage.  will keep an eye on it.

Thanks

[pctech]

Np, think there is a router somewhere that may not be firing on all cylinders.

[armadillo]

I could access some sites, and could ping/IP connect to others. So changing DNS could have suggested to me it was just a DNS error. However one of my direct IP/TCP connections (a game ) dropped, so I doubted it was DNS related.

Thanks. That makes sense to me. Question. If you enter the ip address, rather than a url, direct into the browser, doesn't that bypass the DNS servers? If so, then inability to access via ip address means the problem is not DNS related?

[pctech]

That's correct armadillo.

[armadillo]

That's correct armadillo.

Thank you.

[esh]

Yeah it wasn't a DNS issue. My DNS (local) server fell back to the root servers but then couldn't even access those. I am assuming peering fell over somewhere.