Huge packet-loss lately(pls read).

Hello! ATTENTION IBURST STAFF. THERE IS A PROBLEM WITH YOUR NETWORK OR YOUR PEERING.
 
w1z4rd said:
Hello! ATTENTION IBURST STAFF. THERE IS A PROBLEM WITH YOUR NETWORK OR YOUR PEERING.
Click to expand...
w1z4rd, I will offer some expert help: You are the only person experiencing this, there are no other complaints at this point so the network is running fine! :D Well, thats what they keep telling me even after referencing the existance of this very thread.

We are all figments of each others imaginations, obviously.
 
Hi All

There is a problem, looks like peering at this point. Our technical guys are on it and looking at one of the upstream pipes. I will have more within the next 24 hours...

Cheers for now
Ed
 
Pinging

196.30.31.120
Packet loss = 1%
Min = 45ms Max = 3031ms Ave = 379ms

64.233.183.103
Packet loss = 15%
Min = 279 Max = 3594 Ave = 1007

Download speeds between 200 and 400 kbps.
Load on BS 2.
I suspect network overload.
Wait 'til all planned future victims are on board!
 
Ed Hall said:
Hi All

There is a problem, looks like peering at this point. Our technical guys are on it and looking at one of the upstream pipes. I will have more within the next 24 hours...

Cheers for now
Ed
Click to expand...

Well I have reported it for over a week now that there is a problem. I have wasted over 700mb on trying to download security patches and updates to my new PC, and still no luck with the downloads.

This is the report that I get on my connection to Microsoft website:
Last diagnostic run time: 02/05/07 13:24:24 Network Adapter Diagnostic
Network location detection

info Using home Internet connection
info Redirecting user to support call
info Redirecting user to support call



HTTP, HTTPS, FTP Diagnostic
HTTP, HTTPS, FTP connectivity

warn HTTP: Error 12152 connecting to www.microsoft.com: The server returned an invalid or unrecognized response
info HTTP: Successfully connected to www.hotmail.com.
warn FTP (Passive): Error 12002 connecting to ftp.microsoft.com: The operation timed out
info HTTPS: Successfully connected to www.passport.net.
warn FTP (Active): Error 12031 connecting to ftp.microsoft.com: The connection with the server was reset
error Could not make an FTP connection.
 
Great Ed :) PS. Your peering to SAIX is also gammy:

smtp.saix.net
196.25.240.94
Location:South Africa
Packets Sent:34
Packets Received:10
Packets Lost:24(70% loss)
Response time Minimum:197ms
Response time Maximum:680ms
Response time Average:108ms
 
Type: VERIZON SA NETWORK

Date: 3 Feb 2007 5:32:46 PM
Scheduled Date: 4 Feb 2007
Cause of Problem: Informational
Point of Impact: National & International

Symptoms Experienced: Slight Degradation in Service
Severity: Critical
Status: Pending
Attending: Verizon Engineers
Ticket Number:
Additional Information: Due to a Cisco IOS Security vulnerability that has been
published by Cisco recently, we will be upgrading several
routers in our network to address the potential vulnerability issue. During
this time, you may notice a disruption of service while the router reloads
the new IOS version of code, however traffic should automatically re-route
over our redundant routers and links where available.
 
Great news Ed, all we wanted to hear is that you are aware of the problem and are working on the fix. I suggest you let your helpdesk know about the problem as theres nothing worse than someone telling you that there isn't a problem when there clearly is, i was hours away from cancelling iburst.

Thanx, awaiting some good news!
 
Has anyone else had connection problems, I couldnt connect earlier, it just got to Verifying username and password and then say disconnected "did not respond in a timely matter"
 
Im connected, but can hardly do anything. Filled out an ADSL application today, hoping they now have ADSL in our area. This is amongst the worse I have ever seen iburst :(
 
S1ght said:
Has anyone else had connection problems, I couldnt connect earlier, it just got to Verifying username and password and then say disconnected "did not respond in a timely matter"
Click to expand...

Yeah...been having those lately. I can connect again a few minutes after.
 
Pinging www.l.google.com [64.233.183.104] with 32 bytes of data:

Reply from 64.233.183.104: bytes=32 time=264ms TTL=234
Reply from 64.233.183.104: bytes=32 time=277ms TTL=234
Reply from 64.233.183.104: bytes=32 time=278ms TTL=234
Reply from 64.233.183.104: bytes=32 time=251ms TTL=234

Ping statistics for 64.233.183.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 251ms, Maximum = 278ms, Average = 267ms

Pinging www.iburst.co.za [196.30.31.120] with 32 bytes of data:

Reply from 196.30.31.120: bytes=32 time=48ms TTL=125
Reply from 196.30.31.120: bytes=32 time=65ms TTL=125
Reply from 196.30.31.120: bytes=32 time=104ms TTL=125
Reply from 196.30.31.120: bytes=32 time=69ms TTL=125

Ping statistics for 196.30.31.120:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 48ms, Maximum = 104ms, Average = 71ms
 
Fudzy said:
Pinging www.l.google.com [64.233.183.104] with 32 bytes of data:

Reply from 64.233.183.104: bytes=32 time=264ms TTL=234
Reply from 64.233.183.104: bytes=32 time=277ms TTL=234
Reply from 64.233.183.104: bytes=32 time=278ms TTL=234
Reply from 64.233.183.104: bytes=32 time=251ms TTL=234

Ping statistics for 64.233.183.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 251ms, Maximum = 278ms, Average = 267ms

Pinging www.iburst.co.za [196.30.31.120] with 32 bytes of data:

Reply from 196.30.31.120: bytes=32 time=48ms TTL=125
Reply from 196.30.31.120: bytes=32 time=65ms TTL=125
Reply from 196.30.31.120: bytes=32 time=104ms TTL=125
Reply from 196.30.31.120: bytes=32 time=69ms TTL=125

Ping statistics for 196.30.31.120:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 48ms, Maximum = 104ms, Average = 71ms
Click to expand...

-------------

Nice try, those are from adsl right?
 
Hi All

More news.....problem isolated to only one of the upstream providers, not all 3...technical people still on it and they reckon we should have this sorted within the next 72 hours. Sorry again for the delay, but if we have any luck it may be sooner.

I'll keep all updated, hopefully sooner with good news.

Ed
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X