Any Problems Today?

Started by psp83, Sep 28, 2009, 11:05:27

Previous topic - Next topic

0 Members and 2 Guests are viewing this topic.

Print
Go Down Pages 1 2 3 4 5 6
User actions

psp83

#75
Sep 29, 2009, 18:25:50
Oh and forgot the netbook. cant leave that out now!!  :) (not putting win7 on that thou)

Glenn

#76
Sep 29, 2009, 18:28:37
My corporate version of Windows 7 is running sweetly.
Glenn
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Rik

#77
Sep 29, 2009, 18:29:08
Quote from: psp83 on Sep 29, 2009, 18:24:40
I'm getting ready for windows 7.

Got 3 laptops and 3 pc's to upgrade, so thought i would do a fresh backup from all.. Big mistake  ;D

Paint drying? :)
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

psp83

#78
Sep 29, 2009, 18:30:09
My RC versions are running fine aswell..

I just havent decided.. full reformat and install or do the lifehacker upgrade way!

Glenn

#79
Sep 29, 2009, 18:30:37
It won't have time to dry when installing W7, it only takes around 30 minutes on an average spec laptop.
Glenn
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

psp83

#80
Sep 29, 2009, 18:31:03
Quote from: Rik on Sep 29, 2009, 18:29:08
Paint drying? :)
Yeh, think i'm on the 2nd room of paint drying now!  :laugh:

Rik

#81
Sep 29, 2009, 18:31:23
Quote from: Glenn on Sep 29, 2009, 18:30:37
It won't have time to dry when installing W7, it only takes around 30 minutes on an average spec laptop.

I have some Ronseal 20 minute woodstain. ;D
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Rik

#82
Sep 29, 2009, 18:32:05
Quote from: psp83 on Sep 29, 2009, 18:31:03
Yeh, think i'm on the 2nd room of paint drying now!  :laugh:

A feeling with which I can empathise.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

psp83

#83
Sep 29, 2009, 19:35:46
Quote from: Rik on Sep 29, 2009, 18:32:05
A feeling with which I can empathise.

Wish i never had the crazy idea!

Just starting to install a new server now, should keep me away from the backups for abit  :)

dujas

#84
Sep 29, 2009, 20:29:47
The congestion returned about 30 minutes ago for me:

Pinging www.idnet.net [212.69.36.10] with 32 bytes of data:

Reply from 212.69.36.10: bytes=32 time=157ms TTL=59
Reply from 212.69.36.10: bytes=32 time=167ms TTL=59
Reply from 212.69.36.10: bytes=32 time=102ms TTL=59
Reply from 212.69.36.10: bytes=32 time=89ms TTL=59
Reply from 212.69.36.10: bytes=32 time=132ms TTL=59
Reply from 212.69.36.10: bytes=32 time=172ms TTL=59
Reply from 212.69.36.10: bytes=32 time=160ms TTL=59
Reply from 212.69.36.10: bytes=32 time=169ms TTL=59
Reply from 212.69.36.10: bytes=32 time=114ms TTL=59
Reply from 212.69.36.10: bytes=32 time=93ms TTL=59

Ping statistics for 212.69.36.10:
    Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 89ms, Maximum = 172ms, Average = 135ms

psp83

#85
Sep 29, 2009, 20:49:20
high pings here aswell :(

psp83

#86
Sep 29, 2009, 20:58:08
reboot not clearing it either :(

psp83

#87
Sep 29, 2009, 21:06:52
ok, this is getting annoying now. never had high pings like this with tiscali :(

Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  www.routerlogin.com [192.168.0.1]
  2    58 ms    46 ms    47 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3    55 ms    44 ms    40 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
  4    52 ms    48 ms    46 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5    24 ms    25 ms    23 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6    49 ms    64 ms    52 ms  www.idnet.net [212.69.36.10]

Trace complete.

C:\Users\Paul>tracert www.idnet.net

Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  www.routerlogin.com [192.168.0.1]
  2    15 ms    24 ms    14 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3    15 ms    16 ms    18 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
  4    14 ms    15 ms    16 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5    15 ms    16 ms    14 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6    27 ms    25 ms    17 ms  www.idnet.net [212.69.36.10]

Trace complete.

C:\Users\Paul>tracert www.idnet.net

Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  www.routerlogin.com [192.168.0.1]
  2   185 ms   156 ms   123 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3    97 ms    86 ms    83 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
  4    96 ms   106 ms   105 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5    98 ms    96 ms    91 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6    81 ms    90 ms    83 ms  www.idnet.net [212.69.36.10]

Trace complete.

Colin Burns

#88
Sep 29, 2009, 23:43:48
my pings have finnaly become stable and throughput has pritty much gone back to normal so im a happy bunny

psp83

#89
Sep 30, 2009, 01:21:54
Pings are back to normal here aswell.

root@saturn:~# ping -c 20 idnet.net
PING idnet.net (212.69.36.10) 56(84) bytes of data.
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=1 ttl=59 time=14.1 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=2 ttl=59 time=13.7 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=3 ttl=59 time=13.7 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=4 ttl=59 time=15.1 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=5 ttl=59 time=14.4 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=6 ttl=59 time=14.2 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=7 ttl=59 time=14.4 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=8 ttl=59 time=15.9 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=9 ttl=59 time=13.7 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=10 ttl=59 time=14.5 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=11 ttl=59 time=12.5 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=12 ttl=59 time=13.2 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=13 ttl=59 time=14.4 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=14 ttl=59 time=12.9 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=15 ttl=59 time=13.6 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=16 ttl=59 time=14.1 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=17 ttl=59 time=13.4 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=18 ttl=59 time=13.4 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=19 ttl=59 time=18.8 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=20 ttl=59 time=14.5 ms

--- idnet.net ping statistics ---
20 packets transmitted, 20 received, 0% packet loss, time 19029ms
rtt min/avg/max/mdev = 12.522/14.269/18.866/1.299 ms

Sebby

#90
Sep 30, 2009, 15:30:52
Quote from: psp83 on Sep 29, 2009, 18:30:09
My RC versions are running fine aswell..

I just havent decided.. full reformat and install or do the lifehacker upgrade way!

Clean install. :thumb:

Glenn

#91
Sep 30, 2009, 18:29:23
 :iagree:
Glenn
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

MattBeale

#92
Sep 30, 2009, 21:03:06
High pings and nasty slow data throughput here. One minute it's fast, the next minute it's like being back on dial-up. :eek4:

Speedtest on speedtester.bt.com gave me 765kbps and speedtester.net a little over 1mbit :'(

Niall

#93
Sep 30, 2009, 21:14:27
I did see a lot of websites taking ages to load over the last couple of days, but okay download speeds. I assumed at the time that it was my router needing a reboot, but it's back to normal now so could have been anything.

Wow, that's a helpful contribution :D
Flickr Deviant art
Art is not a handicraft, it is the transmission of feeling the artist has experienced.
Leo Tolstoy

psp83

#94
Sep 30, 2009, 21:58:07
Yet again, another night of high pings. Impossible to play xbox online.

Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  www.routerlogin.com [192.168.0.1]
  2   107 ms   109 ms   109 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3   129 ms   137 ms   136 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
  4   147 ms   149 ms   144 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5   111 ms   117 ms   106 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6   134 ms   119 ms   103 ms  www.idnet.net [212.69.36.10]

Trace complete.

Also, websites are lagging aswell.  :(

Simon

#95
Sep 30, 2009, 22:01:36
I hadn't actually noticed, but mine seem to be up too.

Pinging idnet.com [212.69.36.10] with 32 bytes of data:

Reply from 212.69.36.10: bytes=32 time=175ms TTL=59
Reply from 212.69.36.10: bytes=32 time=136ms TTL=59
Reply from 212.69.36.10: bytes=32 time=140ms TTL=59
Reply from 212.69.36.10: bytes=32 time=157ms TTL=59

Ping statistics for 212.69.36.10:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 136ms, Maximum = 175ms, Average = 152ms
Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.

Simon

#96
Sep 30, 2009, 22:08:33
Reboot hasn't help either.  :(

Pinging idnet.com [212.69.36.10] with 32 bytes of data:

Reply from 212.69.36.10: bytes=32 time=114ms TTL=59
Reply from 212.69.36.10: bytes=32 time=137ms TTL=59
Reply from 212.69.36.10: bytes=32 time=150ms TTL=59
Reply from 212.69.36.10: bytes=32 time=152ms TTL=59

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

C:\Documents and Settings\Simon>tracert idnet.com

Tracing route to idnet.com [212.69.36.10]
over a maximum of 30 hops:

  1     1 ms    <1 ms     1 ms  home [192.168.1.254]
  2    68 ms    61 ms    74 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3   124 ms   124 ms   122 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
  4   108 ms   106 ms   102 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5   126 ms   120 ms   121 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6   128 ms   139 ms   132 ms  www.idnet.net [212.69.36.10]

Trace complete.
Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.

Niall

#97
Sep 30, 2009, 22:33:21
Tracing route to www.idnet.co.uk [212.69.36.10]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  192.168.0.1
  2    24 ms    21 ms    22 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3    20 ms    19 ms    20 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

  4    25 ms    22 ms    20 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5    21 ms    25 ms    20 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6    26 ms    21 ms    22 ms  www.idnet.net [212.69.36.10]

Mine seems fine.
Flickr Deviant art
Art is not a handicraft, it is the transmission of feeling the artist has experienced.
Leo Tolstoy

Aaron

#98
Oct 01, 2009, 20:47:18
High pings tonight. Honestly what's going on? Having high pings in the afternoon was "acceptable" but to have it in the evening since yesterday isn't.
IDNet Home Pro ADSL2+ 4Mbps | Billion BiPAC 7800N

psp83

#99
Oct 01, 2009, 21:54:49
my pings are normal tonight, makes a change.

root@saturn:# ping -c 20 idnet.net
PING idnet.net (212.69.36.10) 56(84) bytes of data.
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=1 ttl=59 time=13.7 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=2 ttl=59 time=15.2 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=3 ttl=59 time=14.1 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=4 ttl=59 time=14.5 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=5 ttl=59 time=15.3 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=6 ttl=59 time=15.3 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=7 ttl=59 time=16.3 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=8 ttl=59 time=13.9 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=9 ttl=59 time=14.5 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=10 ttl=59 time=14.3 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=11 ttl=59 time=14.3 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=12 ttl=59 time=14.3 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=13 ttl=59 time=12.8 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=14 ttl=59 time=14.0 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=15 ttl=59 time=14.6 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=16 ttl=59 time=13.8 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=17 ttl=59 time=12.6 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=18 ttl=59 time=13.8 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=19 ttl=59 time=13.8 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=20 ttl=59 time=26.1 ms

--- idnet.net ping statistics ---
20 packets transmitted, 20 received, 0% packet loss, time 19028ms
rtt min/avg/max/mdev = 12.631/14.908/26.196/2.718 ms
Print
Go Up Pages 1 2 3 4 5 6
User actions