I'm experiencing brief but numerous periods of lag, resulting in web pages taking a long time to load - sometimes they fail to load at all. Anyone else?
Yup :)
Connections dropping and coming back, it's very unstable at the moment.
Yup, I've just had a total loss of throughput for around 10 minutes. I've had to switched from Max to WBC to post here.
There's been some sort of issue over the past few minutes, it was being worked on when I called, so I don't yet have details.
Getting booted off IRC quite a bit, webpages not loading, blips at IDNet again I guess :(
Getting this to was uploading to FTP at the time then it dropped :/
As long as I'm not suffering alone. ;D
As mentioned elsewhere, something seems to have fallen over at Telehouse, investigations continue.
I was running an upgrade script on one of my forums and now my email box is being spammed with the following message from the forum:
Quotemysql_connect() [<a href='function.mysql-connect'>function.mysql-connect</a>]: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) /home/zappadpj/public_html/forums/includes/class_core.php on line 311
Anyone speak Greek? :dunno:
Quote from: zappaDPJ on Apr 14, 2010, 16:51:16
I was running an upgrade script on one of my forums and now my email box is being spammed with the following message from the forum:
Anyone speak Greek? :dunno:
It cant connect to the mysql database, re upload your config file &/or run the upgrade again.
Seen nothing odd here :fingers:
Quote from: psp83 on Apr 14, 2010, 16:53:49
It cant connect to the mysql database, re upload your config file &/or run the upgrade again.
Cheers :thumb:
IDNet have ascertained that their LINX peering fell over. They've removed LINX from the network and this has brought everyone back up again, as far as we can tell. This may be related to the problem people were experiencing Monday (?) evening.
Thanks for the update Rik :thumb:
Quote from: psp83 on Apr 14, 2010, 16:53:49
It cant connect to the mysql database, re upload your config file &/or run the upgrade again.
Finally got my forum updated and back on-line :)
:phew:
I'm getting awful performance at the moment, probably 20% packet loss on pings to places like BBC, Google etc. :( also these forums tonight are really really slow as are most other places.
Same here.
Pinging www.idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=40ms TTL=59
Request timed out.
Reply from 212.69.36.10: bytes=32 time=38ms TTL=59
Request timed out.
Ping statistics for 212.69.36.10:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 38ms, Maximum = 40ms, Average = 39ms
Not good
Ping has started...
PING www.idnet.net (212.69.36.10): 56 data bytes
64 bytes from 212.69.36.10: icmp_seq=0 ttl=59 time=45.172 ms
64 bytes from 212.69.36.10: icmp_seq=1 ttl=59 time=46.608 ms
Request timeout for icmp_seq 2
64 bytes from 212.69.36.10: icmp_seq=3 ttl=59 time=497.720 ms
64 bytes from 212.69.36.10: icmp_seq=4 ttl=59 time=414.404 ms
Request timeout for icmp_seq 5
64 bytes from 212.69.36.10: icmp_seq=6 ttl=59 time=289.516 ms
64 bytes from 212.69.36.10: icmp_seq=7 ttl=59 time=42.561 ms
64 bytes from 212.69.36.10: icmp_seq=8 ttl=59 time=41.265 ms
--- www.idnet.net ping statistics ---
10 packets transmitted, 7 packets received, 30.0% packet loss
round-trip min/avg/max/stddev = 41.265/196.749/497.720/185.176 ms
Things really are not good this evening. I'll post again later if I can stay connected.
Very variable here with complete loss of connectivity a while ago .
on DSL4
had a full internet outage near 9pm(ish). Could ping all local lan ip's but not the dns servers etc.
since its back up this forum is slow at loading all pages/forums, hopefully this will improve. Have already purchased a new gigabit router recently so i know this router is fine.
done a path ping anyway to bbc.co.uk which can't really indicate a major concern as such, can see no displayed packetloss.
0/ 100 = 0% |
2 37ms 0/ 100 = 0% 0/ 100 = 0% telehouse-gw4-lo2.idnet.net [212.69.63.99]
0/ 100 = 0% |
3 59ms 0/ 100 = 0% 0/ 100 = 0% telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
0/ 100 = 0% |
4 51ms 0/ 100 = 0% 0/ 100 = 0% rt-lonap-a.thdo.bbc.co.uk [193.203.5.90]
0/ 100 = 0% |
5 39ms 0/ 100 = 0% 0/ 100 = 0% 212.58.238.153
0/ 100 = 0% |
6 37ms 0/ 100 = 0% 0/ 100 = 0% te12-1.hsw1.cwwtf.bbc.co.uk [212.58.239.234]
0/ 100 = 0% |
7 38ms 0/ 100 = 0% 0/ 100 = 0% 212.58.255.12
0/ 100 = 0% |
8 37ms 0/ 100 = 0% 0/ 100 = 0% fmt-vip01.cwwtf.bbc.co.uk [212.58.246.158]
Trace complete.
Think it may end up a DVD night :)
Same here. For once it seems that the problem has found my hard to find exchange! :D
Is it similar to the past Peterborough problem? Or more widespread? Like the main exchange/pipe downtime last week?
Total loss of connection here in North Lincs.
Connection appears to disappear and reappear without my intervention. Never happened before for me with IDNET....that's what makes the thing so worrying.
Theres an update on the network status page
http://www.idnet.net/support/status.jsp
2010-04-14 21:26: Our core router in London Telecity had not cleared itself since the incident this afternoon and was showing increasing signs of failing to keep its BGP table updated so it has been reloaded. This should fix the performance issues being experienced by web and mail servers hosted in Telecity.
Thanks for the update.
Not sure if it would apply to me, i'm not exactly living in hell but you can see it from my bedroom window.
Thanks Paul. Nice to see the status page updated. :)
Just lost sync for a few minutes. See how it goes tomorrow. :)
Losing sync will be a local issue, nothing to do with IDNet. Around midnight, it's often an indication of BT engineering work.
Quote from: Rik on Apr 15, 2010, 09:37:58
Losing sync will be a local issue, nothing to do with IDNet. Around midnight, it's often an indication of BT engineering work.
Just read your quoted response.
Refering back to my topic "Loss of connection" it reminded me that a friend of mine told me that BT were digging up the roads near the local exchange around the time my connection / sync went down. But I didnt link the two until I saw your post. Interesting... We will see what BT come up with!
:fingers:
Losing the onward connection to the web can be a raft of things, but losing sync is always something between your equipment and the equipment at the exchange, so it's a good basic diagnostic as to where the problem is likely to lay.