I am finding a whole bunch of websites are not working. Example:
Pinging www.tomatoesareevil.com [81.88.57.71] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 81.88.57.71:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Is there still "upgrade" work going on?
No, and it's working fine for me. What happens when you do a tracert to the site?
Fine for me on IDNet DNS and OpenDNS.
They're working again now >:(
The last couple of days have felt like I'm back on Plusnet :bawl:
I've just had ten minutes when websites wouldn't work, but seems OK now :dunno:
Sounds like work is still under way somewhere,probably about time for LINX to play up >:D
It was weird... most (but not all) websites wouldn't load, and my RSS feeds failed.
Everything else was still working :dunno:
Quote from: Bill on Sep 07, 2010, 12:06:52
I've just had ten minutes when websites wouldn't work, but seems OK now :dunno:
Anything specific, Bill?
I've checked with support and they're not seeing any issues today, so if anyone does have problems, could they run both a traceroute and path ping to the sites.
The tbb sites weren't working (except the BQM), most IDNet ones seemed OK (except webmail), they're the only ones I can remember.
Restarting the browser didn't help so I rebooted the iMac (in case it was my end), by the time it was back up everything was working again!
Odd, Bill, because I was on TB at the time. :dunno:
In the last few weeks I've had the odd occasion on the iMac where ping times have been high, I don't know the cause but my only cure has been a reboot.
Quote from: Steve on Sep 07, 2010, 12:27:45
In the last few weeks I've had the odd occasion on the iMac where ping times have been high, I don't know the cause but my only cure has been a reboot.
Haven't seen that... occasionally I find that a frequently used site (eg the tbb forums or this one) goes
VERY sluggish, but I'm pretty sure that's an Opera problem- closing the tab and opening a new one on the same url cures it.
This forum going sluggish is often the server, Bill, we share it with 2 or 3 others.
I mean really sluggish... like over a minute to load :eek4:
And not intermittently- once it goes that way, it stays like it.
If the server is slow, try browsing to Orange bikes, if that is slow too, then it's the server.
OB often run processes which hog the server, Bill. The other time you'll see a slowdown is when the daily backup kicks in. The very long hang can often be cured by hitting stop then refresh (or link).
Cheers, I'll give that a try next time.
I suppose I got so used to it happening on tbb that I just used the same cure ;D
One backup runs at 6am everyday. When it starts, I get a 500 error trying to access the forum, normally it's OK within a couple of minutes.
Quote from: Glenn on Sep 07, 2010, 12:48:45
One backup runs at 6am
If I'm online at 6am it was a very late night ;D
;D
It was really quiet in here, Bill, you could have stayed asleep. ;)
I'm having a few issues with some American sites right now, UPS being one of them, in fact there is quite a few not responding right now
Server not found (ups.com)?
Quote from: Rik on Sep 07, 2010, 15:53:19
Server not found (ups.com)?
yep, mobog.com doing the same and myspace.com
And PC-Pals. On the phone...
Same here (FTTC) some sites won't load at all.
Quote from: Rik on Sep 07, 2010, 15:55:14
And PC-Pals. On the phone...
working on the phone :(
One of the resolvers is playing up - being worked on as I type.
Quote from: Rik on Sep 07, 2010, 15:59:07
One of the resolvers is playing up - being worked on as I type.
You said it was a quite day to early, Rik ;)
Yep had two bouts of this wierdness - just before lunch my VPN to the office dropped out, but MSN and Skype stayed up. I use OpenDNS routinely but couldn't get to their website at all. Thought it was them so after some faffing around switched to IDnet DNS servers - this resolved it. So, OpenDNS was the culprit i thought - but nothing on their forums or status. However, the same thing has just happened. I've once again switched to IDNet DNS and some sites work (this one) and some don't... VPN to office has dropped again but SKype/MSN are up. Obviously the first time around the problem had been sorted by the time I switched to IDNet DNS...
I use the IDnet RSS feed, but there's nothing in there.
Quote from: Gary on Sep 07, 2010, 15:59:53
You said it was a quite day to early, Rik ;)
;D
The number of users online is looking healthy again ;D
Thats because its like browsing through Treacle ;D
Every cloud, Bill. ;D
I am having a lot of DNS problems today too.
However, I am using OpenDNS and through Idnet on my netbook, Pings to 208.67.220.220 (openDNS servers ) fail and tracerts time out after the first hop 212.66.63.99.
Doing the same thing on the same netbook through my neighbours Talktalk connection, there is no problem at all.
That's odd. Have you told support, Alan?
I use OpenDNS too Alan, but have only seen issues twice today. When the problem at IDNet has occurred (just before lunch and just before 4pm) it affects my ability to connect to the OpenDNS DNS servers, rendering the connection completely useless. Switching to IDNet DNS opens up a bit more, but still 50% of sites (at a rough guess) don't work.
Edit: Like Alan, a tracert to one of the OpenDNS IP addresses times out after second hop 212.66.63.99.
Lost Myspace and Mobog again Cant sign in on the Playstaiton either now
Browsing has been a pit slow this afternoon, but I see that one of the resolvers is playing up - thanks Rik for the info.
NP. It should be returning to normal now.
Quote from: Rik on Sep 07, 2010, 15:59:07
One of the resolvers is playing up - being worked on as I type.
How/Why would that affect those of us using OpenDNS or Google DNS?
The traffic has to go through IDNet, before it reaches the outside world. I would think the resolver needs to know where to send the packets once you click on the links,
It shouldn't. Having checked the suspect resolver, it now looks like it's an intermittent external routing problem. This causes routes to be re-broadcast at frequent intervals, causing the problem. IDNet are working to identify the external route so they can bypass it.
I'm getting packet loss, high pings and timeouts all over the place. Bah! LiveJournal, Wordpress, Second Life, Twitter, Gmail. Flickr. The whole internets is playing hide and seek :(
Pings and tracerts from just two of those:
C:\Users\Reya>ping www.wordpress.com
Pinging lb.wordpress.com [74.200.244.59] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 74.200.244.59:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Users\Reya>tracert www.wordpress.com
Tracing route to lb.wordpress.com [74.200.244.59]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms www.routerlogin.com [192.168.0.1]
2 49 ms 33 ms 33 ms telehouse-gw2-lo1.idnet.net [212.69.63.51]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
(etc etc, over all 30 hops.)
C:\Users\Reya>ping livejournal.com
Pinging livejournal.com [208.93.0.128] with 32 bytes of data:
Request timed out.
Reply from 208.93.0.128: bytes=32 time=180ms TTL=239
Request timed out.
Reply from 208.93.0.128: bytes=32 time=181ms TTL=239
Ping statistics for 208.93.0.128:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 180ms, Maximum = 181ms, Average = 180ms
C:\Users\Reya>tracert livejournal.com
Tracing route to livejournal.com [208.93.0.128]
over a maximum of 30 hops:
1 2 ms <1 ms <1 ms www.routerlogin.com [192.168.0.1]
2 30 ms 32 ms 30 ms telehouse-gw2-lo1.idnet.net [212.69.63.51]
3 28 ms 28 ms 28 ms telehouse-gw5-lo1.idnet.net [212.69.63.245]
4 31 ms 31 ms 29 ms gi8-27.mpd01.lon02.atlas.cogentco.com [149.6.148
.205]
5 167 ms 203 ms 199 ms te1-2.ccr02.lon02.atlas.cogentco.com [130.117.50
.117]
6 114 ms 108 ms 107 ms te0-5-0-1.ccr22.jfk02.atlas.cogentco.com [154.54
.30.134]
7 119 ms 121 ms 112 ms te0-2-0-7.ccr22.dca01.atlas.cogentco.com [154.54
.41.9]
8 111 ms 110 ms 115 ms te0-0-0-5.ccr22.iad02.atlas.cogentco.com [154.54
.30.126]
9 112 ms 133 ms 114 ms qwest.iad01.atlas.cogentco.com [154.54.10.26]
10 180 ms 175 ms 189 ms bil-core-02.inet.qwest.net [205.171.8.154]
11 189 ms 184 ms 187 ms bil-edge-02.inet.qwest.net [205.171.154.22]
12 181 ms 181 ms 180 ms 65.121.112.210
13 182 ms * * livejournal.com [208.93.0.128]
14 194 ms 183 ms 182 ms livejournal.com [208.93.0.128]
Trace complete.
See above.
Quote from: .Griff. on Sep 07, 2010, 16:28:20
How/Why would that affect those of us using OpenDNS or Google DNS?
It cannot be the resolver, I am typing in IP addresses and failing.
I can't even contact Support by telephone, 0800 701 2000 gets an answerphone and 01462 476 555 is unobtainable.
The Idnet site is unreachable through Idnet and Talktalk
Same issues here with both OpenDNS and IDNet's servers. Network status page just updated:
QuoteNetwork Status
2010-09-07 16:37: There have been a couple of network routing issues this afternoon that we are working to resolve.
Phones are in meltdown, Alan, they're a man short and those who would normally step in to help are trying to fix the problem.
I can reach the site fine, but the problem is intermittent...
Thanks, Rik. I've no idea what a resolver is, apart from something horribly techie that's going to go whooshing over my head (well, not literally), so I guess I'll just make a cuppa and find one of those papery things to amuse myself with while I wait it out. Books, I think they're called ;D
I'm going to go kill some Helgans and take out my frustration on the PS3 ;D
Quote from: Reya on Sep 07, 2010, 16:42:37
Thanks, Rik. I've no idea what a resolver is, apart from something horribly techie that's going to go whooshing over my head (well, not literally), so I guess I'll just make a cuppa and find one of those papery things to amuse myself with while I wait it out. Books, I think they're called ;D
The resolver is the DNS nameserver, the bit that translates the www.xxx into an IP address. However, it now appears that it's an external problem to IDNet, with one of the peers dropping intermittently. When that happens, all the IP addresses have to be re-routed, which takes time and cause the slow access or lack of access. Being intermittent, of course, it's proving a bit more difficult to find and bypass.
Quote from: Reya on Sep 07, 2010, 16:42:37
Thanks, Rik. I've no idea what a resolver is, apart from something horribly techie that's going to go whooshing over my head (well, not literally)
Well that all depends how far you live from IDnet's HQ and how pee'd off Simon / Tim gets and can throw the damn thing! ;)
;D
I currently have a couple of RSS feeds not responding including one from the BBC. Everything else seems to be working though.
Quote from: Rik on Sep 07, 2010, 16:45:35
The resolver is the DNS nameserver, the bit that translates the www.xxx into an IP address. However, it now appears that it's an external problem to IDNet, with one of the peers dropping intermittently. When that happens, all the IP addresses have to be re-routed, which takes time and cause the slow access or lack of access. Being intermittent, of course, it's proving a bit more difficult to find and bypass.
Thank you! Makes sense now :)
Quote from: psp83 on Sep 07, 2010, 16:50:32
Well that all depends how far you live from IDnet's HQ and how pee'd off Simon / Tim gets and can throw the damn thing! ;)
I suppose sandbags and a blankie fort won't protect me? (I'm going! I'm going! ;D)
;D
:lol:
I almost logged into WoW, and then was DC'd, but some progress :D
Wondered what was going on, I thought it was the thunderstorm that has been going on for a few hours - hope it gets sorted soon I'm getting earache, "The internet has stopped working!"
*Fixcus Internetus!*
Quote from: Rik on Sep 07, 2010, 16:34:23
It shouldn't. Having checked the suspect resolver, it now looks like it's an intermittent external routing problem.
That sounds more like the problem. Latency has been on the increase since lunchtime I notice which I guess would be a result of routing issues.
Sounds probable. It's been a fun-filled few days hasn't it. 8-)
OMFG.... Just had a peep at the network status page. We are going to have a SIX hour outage tomorrow night!?? NOOOoooooooo. :bawl:
Oi! BT! :no:
You can see the packet loss increase on my graph (http://www.thinkbroadband.com/ping/share/fd74e756a502f41811d8fef05ebd688c.html)
Quote from: Glenn on Sep 07, 2010, 17:02:11
You can see the packet loss increase on my graph (http://www.thinkbroadband.com/ping/share/fd74e756a502f41811d8fef05ebd688c.html)
Same - (http://www.thinkbroadband.com/ping/share-thumb/76f4562de976c46054e6626496abcda3.png) (http://www.thinkbroadband.com/ping/share/76f4562de976c46054e6626496abcda3.html)
Quote from: Conrad on Sep 07, 2010, 17:01:26
OMFG.... Just had a peep at the network status page. We are going to have a SIX hour outage tomorrow night!?? NOOOoooooooo. :bawl:
Oi! BT! :no:
'Fraid so, though whether it will affect everyone or last that long is moot. BT tend to paint a 'worst case scenario' with this kind of work.
Similar here with mine, not quite as bad as yours, Glenn, Ping graph (http://www.thinkbroadband.com/ping/share/1ca567fe865c7b0477e046c00d425d76-07-09-2010.html)
Same here for packet loss:
(http://www.thinkbroadband.com/ping/share-thumb/d61c677a77b2bea640cc5401a183b5ac.png) (http://www.thinkbroadband.com/ping/share/d61c677a77b2bea640cc5401a183b5ac.html)
(http://www.thinkbroadband.com/ping/share-thumb/fb61cbda7e641dee6ef7353322a8bc40.png) (http://www.thinkbroadband.com/ping/share/fb61cbda7e641dee6ef7353322a8bc40.html)
The packet loss looks the same across all the graphs.
Like others, I have waited patiently over the past few days for commonly used sites to load. Geocaching.com is the latest one to 'hang'. I confess that I do not know what a traceroute shows but here are the details. Any thoughts? ???
Traceroute has started...
traceroute to www.geocaching.com (66.150.167.189), 64 hops max, 52 byte packets
1 www.routerlogin.com (192.168.0.1) 2.324 ms 1.521 ms 1.613 ms
2 telehouse-gw4-lo2.idnet.net (212.69.63.99) 33.596 ms 33.917 ms 32.971 ms
3 telehouse-gw5-lo1.idnet.net (212.69.63.245) 33.982 ms 32.850 ms 32.677 ms
4 gi8-27.mpd01.lon02.atlas.cogentco.com (149.6.148.205) 35.579 ms 33.592 ms 33.250 ms
5 te1-2.ccr02.lon02.atlas.cogentco.com (130.117.50.117) 40.034 ms
te1-2.ccr01.lon02.atlas.cogentco.com (130.117.50.138) 33.624 ms
te1-2.ccr02.lon02.atlas.cogentco.com (130.117.50.117) 35.240 ms
6 te0-1-0-5.ccr21.ymq02.atlas.cogentco.com (38.109.18.125) 112.438 ms
154.54.42.46 (154.54.42.46) 119.203 ms
154.54.42.49 (154.54.42.49) 109.936 ms
7 te0-0-0-6.mpd21.ord01.atlas.cogentco.com (38.20.46.9) 147.041 ms
te0-2-0-6.ccr21.ord01.atlas.cogentco.com (154.54.30.238) 135.648 ms
te0-2-0-6.mpd21.ord01.atlas.cogentco.com (154.54.30.234) 137.447 ms
8 multi-use.cogentco.com (154.54.25.81) 150.689 ms
te0-0-0-3.mpd21.mci01.atlas.cogentco.com (154.54.2.233) 149.224 ms
te0-0-0-3.ccr21.mci01.atlas.cogentco.com (154.54.2.217) 147.063 ms
9 te4-4.mpd01.den01.atlas.cogentco.com (154.54.24.81) 162.970 ms 159.297 ms
te4-4.mpd02.den01.atlas.cogentco.com (154.54.7.130) 162.514 ms
10 te4-2.ccr01.slc01.atlas.cogentco.com (154.54.0.42) 166.737 ms
te3-2.ccr01.slc01.atlas.cogentco.com (154.54.3.14) 178.726 ms
te4-2.ccr01.slc01.atlas.cogentco.com (154.54.0.42) 171.786 ms
11 te7-3.ccr01.smf01.atlas.cogentco.com (66.28.4.194) 181.596 ms
te4-2.ccr01.smf01.atlas.cogentco.com (154.54.1.101) 183.539 ms
te7-3.ccr01.smf01.atlas.cogentco.com (66.28.4.194) 182.417 ms
12 te4-3.ccr01.sea01.atlas.cogentco.com (154.54.40.106) 197.373 ms 196.867 ms 196.574 ms
13 te4-2.ccr01.sea03.atlas.cogentco.com (154.54.41.146) 198.659 ms 199.115 ms 197.782 ms
14 regus-business-center.demarc.cogentco.com (38.104.124.82) 197.101 ms 196.255 ms 197.762 ms
15 border8.t8-1-bbnet2.sef.pnap.net (63.251.160.82) 199.400 ms 197.167 ms 200.563 ms
16 * *
Ping has started...
PING www.geocaching.com (66.150.167.189): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
Request timeout for icmp_seq 6
Request timeout for icmp_seq 7
Request timeout for icmp_seq 8
--- www.geocaching.com ping statistics ---
10 packets transmitted, 0 packets received, 100.0% packet loss
They're all looking similar to the second one I gave here (http://www.idnetters.co.uk/forums/index.php?topic=21909.msg527226#msg527226)... the routers are sending some of us on the scenic route :P
And it's not even Scotland. :(
And .... the solution is? :-\
Quote from: Ardua on Sep 07, 2010, 17:20:32
And .... the solution is? :-\
I think it has to be- wait until IDNet get it fixed.
FWIW, Geocaching.com works fine for me :dunno:
There are no updates atm, they are working as quickly as possible to resolve the issue.
Quote from: Rik on Sep 07, 2010, 17:25:54
There are no updates atm, they are working as quickly as possible to resolve the issue.
Looks like some overtime needed tonight ;D
Could well be, Paul, though everything seems fine for me atm. (At which point I will probably lose all connectivity...)
I'm still seeing problems here.
Does a tracert give any clues?
I still get slow browsing, in patches.
Any common factors, Glenn, eg geography?
Between Paul and myself? We could both be connected via the Kingston node, but Paul is around 60 miles west of me.
How about the affected sites?
Quote from: Rik on Sep 07, 2010, 17:39:14
Does a tracert give any clues?
Nope. Its random & when it happens and I do a tracert, its normal.
Just been shouted at because facebook is being slow / not working, esp farmville! (cr*p game)
Think I might head towards the pub! ;D
;D
I was trying here and www.iracing.com, in USA which times out after 12 hops.
OK, here.
Quote from: Glenn on Sep 07, 2010, 17:47:24
I was trying here and www.iracing.com, in USA which times out after 12 hops.
Opens immediately for me, but a traceroute times out after 16 hops :dunno:
I can get to it, but it is slow to load.
About 2-3 seconds?
For me, a trace times out after 12 hops:
tracert www.iracing.com
Tracing route to www.iracing.com [174.129.239.237]
over a maximum of 30 hops:
1 <1 ms <1 ms 1 ms home [192.168.1.254]
2 14 ms 11 ms 12 ms telehouse-gw4-lo2.idnet.net [212.69.63.99]
3 15 ms 14 ms 13 ms telehouse-gw5-lo1.idnet.net [212.69.63.245]
4 15 ms 13 ms 13 ms gi8-27.mpd01.lon02.atlas.cogentco.com [149.6.148.205]
5 11 ms 13 ms 13 ms te1-2.ccr02.lon02.atlas.cogentco.com [130.117.50.117]
6 95 ms 92 ms 92 ms te0-5-0-1.ccr22.jfk02.atlas.cogentco.com [154.54.30.134]
7 98 ms 102 ms 100 ms te0-0-0-6.ccr22.dca01.atlas.cogentco.com [154.54.26.2]
8 97 ms 98 ms 98 ms te0-2-0-5.ccr22.iad02.atlas.cogentco.com [154.54.41.118]
9 99 ms 97 ms 97 ms verio.iad01.atlas.cogentco.com [154.54.12.238]
10 99 ms 119 ms 96 ms xe-0-4-0-7.r01.asbnva02.us.ce.gin.ntt.net [168.143.191.26]
11 100 ms 100 ms 102 ms 72.21.197.40
12 * 101 ms 100 ms 72.21.222.155
13 * * * Request timed out.
14 * * * Request timed out.
Around 10 seconds for me, but it times out at the same IP.
Which could, of course, just be later routers don't respond to ICMP.
Of course.
Interesting, my traceroute goes a different way:
traceroute www.iracing.com
traceroute to www.iracing.com (174.129.239.237), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 0.648 ms 0.309 ms 0.131 ms
2 telehouse-gw4-lo2.idnet.net (212.69.63.99) 10.861 ms 10.908 ms 10.557 ms
3 telehouse-gw5-lo1.idnet.net (212.69.63.245) 10.679 ms 11.133 ms 10.743 ms
4 gi8-27.mpd01.lon02.atlas.cogentco.com (149.6.148.205) 15.967 ms 12.403 ms 11.480 ms
5 te1-2.ccr02.lon02.atlas.cogentco.com (130.117.50.117) 11.926 ms 12.408 ms 11.514 ms
6 te0-0-0-1.ccr22.jfk02.atlas.cogentco.com (154.54.30.21) 82.987 ms 84.790 ms
te0-5-0-1.ccr22.jfk02.atlas.cogentco.com (154.54.30.134) 95.391 ms
7 te0-0-0-2.ccr22.dca01.atlas.cogentco.com (66.28.4.82) 103.548 ms
te0-0-0-6.ccr22.dca01.atlas.cogentco.com (154.54.26.2) 96.790 ms 97.074 ms
8 te0-0-0-1.ccr22.iad02.atlas.cogentco.com (154.54.26.134) 93.941 ms 98.698 ms
te0-1-0-1.ccr22.iad02.atlas.cogentco.com (154.54.26.138) 105.943 ms
9 verio.iad01.atlas.cogentco.com (154.54.12.238) 103.653 ms 99.875 ms 95.711 ms
10 xe-0-4-0-6.r01.asbnva02.us.ce.gin.ntt.net (168.143.191.18) 97.184 ms 94.057 ms 94.322 ms
11 72.21.197.34 (72.21.197.34) 96.414 ms 94.179 ms 97.014 ms
12 72.21.222.141 (72.21.222.141) 91.871 ms 92.665 ms 91.741 ms
13 216.182.224.51 (216.182.224.51) 95.213 ms 102.504 ms 108.981 ms
14 216.182.232.16 (216.182.232.16) 100.940 ms 99.800 ms 97.373 ms
15 216.182.232.67 (216.182.232.67) 101.693 ms 115.200 ms 104.931 ms
16 ec2-75-101-160-183.compute-1.amazonaws.com (75.101.160.183) 99.440 ms 99.618 ms 97.196 ms
17 * * *
That fits what I've just been told, Bill. I'm going to put up the newsfader so that everyone sees it.
Reposted on tbb :P
This Redbus?
http://www.red-bus.com/
And not the ones on the streets?
Seems to be working more than before :)
Quote from: Bill on Sep 07, 2010, 18:18:47
Reposted on tbb :P
Thanks.
It's nothing to do with Sunday's issues, just an unfortunate coincidence of events.
Quote from: Glenn on Sep 07, 2010, 18:19:56
This Redbus?
http://www.red-bus.com/
And not the ones on the streets?
The very same, though I have a soft spot for the Routemaster myself. :)
Quote from: Rik on Sep 07, 2010, 18:20:41
Thanks.
It's nothing to do with Sunday's issues, just an unfortunate coincidence of events.
Yup, Murphy's Law again.
(That's the one that says Sod's Law is optimistic :P)
:rofl: :karma: I know the very one.
Then of course there is Coles Law. Goes nice with salad.
:grn:
:karmic:
:lol:
:argh:
Rik, I know you must be having a rather hectic few days there but just to say thanks for keeping on top of the problems and being patient with us all here acting like cranky internet-deprived oldies that... we actually are. :shake: :D
I fully agree he deserves a big round of applause :great:
Absolutely :bow:
:iagree: :great:
Yes indeed! :thumb:
Most definitely ;D
I'm still seeing issues tonight.
I use trillian 5 for my messenger and I keep getting logged out from all (astra, msn, yahoo, skype, facebook chat)
I'm also having connection issues with xbox.
I've just been disconnected from WoW and cannot get logged back in, what have they broken this time :(
This is really starting to get on my nerves, it's been like this all day :(
Hey Kar, me to :(
Same here as well, can't get back into WoW
Dropped twice from iRacing already - will be a bit of a shame if I can't defend my championship lead tonight, especially as I was top of the timesheets both times so far...
testing my WoW now..
Login fine, character list for Terenas gained...
Main character accessible and loaded fine
u certain your realm is up?
It's working again now, my realm was definitely up as I was talking to other people on steam at the time.
:welc: :karma: Peyr
Sorry it seems to have been missed a couple of years ago.
Quote from: gizmo71 on Sep 07, 2010, 20:21:37
Dropped twice from iRacing already - will be a bit of a shame if I can't defend my championship lead tonight, especially as I was top of the timesheets both times so far...
Yep. I got the same disconnect here. But any open direct connections stayed live. Just could not do any webpages or new games ect. :/
Is it just me but struggling with http://forums.thinkbroadband.com/
OK here, Steve.
Quote from: Gary on Sep 07, 2010, 20:06:48
Most definitely ;D
Thanks, guys - we all try hard to get you the updates that we can.
I've got through now but seems very sluggish.
Quote from: Steve on Sep 07, 2010, 22:13:53
Is it just me but struggling with http://forums.thinkbroadband.com/
Slow at loading here aswell.
OK here... :dunno:
takes about 10 secs to load here, a few other sites are slow aswell.
even this forum is slow at times.
its been on and off all evening for me.
2 seconds for TB, this forum is generally instant, but sometimes hangs a bit, but then it's always done that.
ah well, hopefully all will be better tomorrow.. well I hope so, got quite alot of work to do this week :-\
So do I Paul, believe me. :)
Well have a good night Rik and the rest of IDnetters.. Calling it a night now.
Sleep well. :bye:
TB is fine for me too.
Quote from: gizmo71 on Sep 07, 2010, 20:21:37
Dropped twice from iRacing already - will be a bit of a shame if I can't defend my championship lead tonight, especially as I was top of the timesheets both times so far...
Well despite getting disconnected twice in practice, the connection stayed up for both qualifying and practice, and it was only my incompetence that dropped me out of the lead I took from pole position and back to tenth place :blush: though I did fight my way back to the bottom step of the podium. ;D
Everything seems to have settled down a bit now...
:phew:
Quote from: Kareha on Sep 07, 2010, 20:08:59
I've just been disconnected from WoW and cannot get logged back in, what have they broken this time :(
This has just happened to me again, same as yesterday. As with yesterday the server is definitely still up as I'm speaking with others over steam right now.
1 <1 ms <1 ms <1 ms 192.168.0.1
2 25 ms 25 ms 25 ms telehouse-gw4-lo2.idnet.net [212.69.63.99]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
Indeed, some things are working but for the past 10 mins it's been mostly dead :)
Quote from: Peyr on Sep 08, 2010, 20:40:38
This has just happened to me again, same as yesterday. As with yesterday the server is definitely still up as I'm speaking with others over steam right now.
Happened to me to just now again, can't log in yet still connected to Vent and the raid is carrying on which means the server is still up.
Quote from: Peyr on Sep 08, 2010, 20:40:38
This has just happened to me again, same as yesterday. As with yesterday the server is definitely still up as I'm speaking with others over steam right now.
I can confirm this, it appears to only be affecting IDNet customers including myself.
This is a tracert to my WoW server:
C:\Users\Kareha>tracert 80.239.185.127
Tracing route to 80-239-185-127.customer.teliacarrier.com [80.239.185.127]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 25 ms 24 ms 25 ms telehouse-gw4-lo2.idnet.net [212.69.63.99]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
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 * * * Request timed out.
Teamspeak up, rest of WoW Raiders appear unaffected.. just me, and was disconnected. cannot reconnect to WoW servers.. all realms.
Asked them to replace me due to this impaired connectivity.
It's working again now. Fingers crossed this doesn't happen again.
(http://www.speedtest.net/result/945778753.png) (http://www.speedtest.net)
this is what i'm now experiencing since the sunday afternoon issues.
Working agian now but big lag to WoW - 250ms atm :blush:
Guys, there is not a lot you can do at this time of day, apart from reporting the problems to support, either by calling now and leaving a message, email, or call tomorrow morning.
662ms to WoW.
Quote from: gyruss on Sep 08, 2010, 21:01:23
Teamspeak up, rest of WoW Raiders appear unaffected.. just me, and was disconnected. cannot reconnect to WoW servers.. all realms.
Asked them to replace me due to this impaired connectivity.
Hmmm. Strange. That's what happened to me yesterday. I had teamspeak up, and it kept working, but games and the web died.
Quote from: gyruss on Sep 08, 2010, 21:16:20
(http://www.speedtest.net/result/945778753.png) (http://www.speedtest.net)
this is what i'm now experiencing since the sunday afternoon issues.
That looks like a depressed profile, could you do a BT speed test and paste the results back here.
Depressed user more likely. I'm at work at the moment, will do that later.
;D