republican-creole
Search:  

 
theme to black backgroundlet page decide theme
HomeFind ServiceReviewsISP NewsFAQsForumsToolsDatabaseAbout 
 
   All ForumsHot TopicsGallery






how-to block ads


 
Forums » The Site » Old Forums » AT&T Broadband » Post here the ping times to your gateway
Uniqs:
126		 Share Topic:
RSS topic:
toggle:
flat / full
normal / watch
Posting:
Links: ·Forum FAQ ·AT&T IP Network Performance ·Comcast Merger Page
ATTBI internet and cable television »
« South San Jose Deployment Date  
page: 1 · 2 · 3
ChuC

join:2001-12-18

Post here the ping times to your gateway

Let us post here our ping times to the gateway so that ATT can do something positive about it. They need data. I will start with mine. Include timestamp and your area.

>ping -n 10 12.234.176.1

Pinging 12.234.176.1 with 32 bytes of data:

Ping statistics for 12.234.176.1:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 251ms, Average = 133ms
>time
The current time is: 15:24:55.85 PDT (San Francisco Bay Area)
permalink · 2002-09-24 18:29:02 · Print ·

Mark IV
Premium
join:2002-09-22
Montreal, QC

Re: Post here the ping times to your gateway

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

in the bay area too (berkeley)
permalink · 2002-09-24 18:31:53 ·

prwood
Premium
join:2001-09-04
Danvers, MA

 >ping -n 10 66.31.24.1

Pinging 66.31.24.1 with 32 bytes of data:
Ping statistics for 66.31.24.1:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 78ms, Average = 26ms

---
This is the Boston, Mass area around 6:30 pm EDT.
--
[ boston ] [ my site ] [ photos ]
permalink · 2002-09-24 18:37:28 · Print ·

jeremy27

join:2001-11-29
Grand Rapids, MI		 Ping statistics for 12.245.88.1:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 94ms, Average = 14ms
permalink · 2002-09-24 20:33:53 ·

KeNsHiN x

join:2001-10-19
Elk Grove, CA

 Ping statistics for 12.246.188.1:
Packets: Sent = 15, Received = 15, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 17ms, Average = 11ms

This is in the Sacramento Area (95624) at 5:56 PM.
permalink · 2002-09-24 20:58:13 ·
urd

join:2001-07-26
Oakland, CA

 Pinging 12.233.50.1 with 32 bytes of data:

Reply from 12.233.50.1: bytes=32 time=8ms TTL=255
Reply from 12.233.50.1: bytes=32 time=7ms TTL=255
Reply from 12.233.50.1: bytes=32 time=8ms TTL=255
Reply from 12.233.50.1: bytes=32 time=9ms TTL=255

Ping statistics for 12.233.50.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 9ms, Average = 8ms

Bay Area
permalink · 2002-09-24 21:28:57 ·

EastLansing

@attbi.com

 >ping -n 10 10.186.160.1

Ping statistics for 10.186.160.1:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 136ms, Maximum = 463ms, Average = 277ms

East Lansing, Michigan...I'm tired of these ping times =/
permalink · 2002-09-24 21:36:27 ·

LarryE

join:2000-07-29
Chicago, IL
 What's the gateway and how do I find out what mine is?

el gringo
[text was edited by author 2002-09-24 21:40:01]
permalink · 2002-09-24 21:37:46 ·

KeNsHiN x

join:2001-10-19
Elk Grove, CA

Re: Post here the ping times to your gateway

said by LarryE See Profile:
What's the gateway and how do I find out what mine is?
Find out your IP by going to »www.ipchicken.com (or some other IP place).

Your gateway is whatever your ping is but last set of numbers is a 1. (For example, IP 123.123.123.123 has a gateway of 123.123.123.1 - so *.*.*.1 is the gateway.

I hope this helps ya...
permalink · 2002-09-24 22:23:05 · Print ·

titanium
Titanium

join:2000-05-25
West Richland, WA
·Verizon Online DSL

 C:\>ping 24.98.2.1

Pinging 24.98.2.1 with 32 bytes of data:

Reply from 24.98.2.1: bytes=32 time=271ms TTL=255
Reply from 24.98.2.1: bytes=32 time=390ms TTL=255
Reply from 24.98.2.1: bytes=32 time=431ms TTL=255
Reply from 24.98.2.1: bytes=32 time=500ms TTL=255

Ping statistics for 24.98.2.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 271ms, Maximum = 500ms, Average = 398ms

C:\>

not normally this bad... but has been over 100ms for me on average lately.. tonight just completely blows though.. the one night i really need to use my internet in a while and its crawling slow enough it might as well be completely down.
[text was edited by author 2002-09-24 21:59:55]
permalink · 2002-09-24 21:55:46 · Print ·

titanium
Titanium

join:2000-05-25
West Richland, WA
·Verizon Online DSL

Re: Post here the ping times to your gateway

C:\>ping 24.98.2.1

Pinging 24.98.2.1 with 32 bytes of data:

Reply from 24.98.2.1: bytes=32 time=411ms TTL=255
Reply from 24.98.2.1: bytes=32 time=350ms TTL=255
Reply from 24.98.2.1: bytes=32 time=321ms TTL=255
Reply from 24.98.2.1: bytes=32 time=761ms TTL=255

Ping statistics for 24.98.2.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 321ms, Maximum = 761ms, Average = 460ms

C:\>

one run right after posting... hey, atleast i have 0% loss... yippie (pfft)
[text was edited by author 2002-09-24 22:00:25]
permalink · 2002-09-24 21:57:00 · Print ·
ihaddsl

join:2001-12-05
/dev/hda0
·Comcast

 Pinging 12.248.0.1 with 32 bytes of data:

Reply from 12.248.0.1: bytes=32 time=20ms TTL=254
Reply from 12.248.0.1: bytes=32 time10ms TTL=254
Reply from 12.248.0.1: bytes=32 time=10ms TTL=254
Reply from 12.248.0.1: bytes=32 time=10ms TTL=254

Ping statistics for 12.248.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 20ms, Average = 10ms
permalink · 2002-09-24 22:21:05 ·
migxxv

join:2002-04-30
Citrus Heights, CA		 Not always Kenshin, sometimes if you have a 123.123.123.123 address than your gateway can have a different second to last number (123.123.122.1; 123.123.121.1; etc...)
permalink · 2002-09-24 22:28:53 ·

wheelzoff

join:2001-02-14
Irving, TX
clubs:

Re: Post here the ping times to your gateway

True, my ip is 12.239.241.247 and my gateway is 12.239.240.1, so that isn't always the case. Too find your gateway open a command prompt and type "ipconfig" or "ipconfig/all"

Ping statistics for 12.239.240.1:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 37ms, Average = 13ms

Pretty damn good numbers for 9pm.
--
"The Stars win the Stanley Cup, The Stars win the Stanley Cup" Ralph Strangis!!
permalink · 2002-09-24 22:34:29 · Print ·

Mordy
Comfortably Numb
Premium,MVM,ExMod 2004-07
join:2001-12-02
Denver, CO
·Comcast Formerly ..

 Pinging 12.253.30.1 with 32 bytes of data:

Reply from 12.253.30.1: bytes=32 time=11ms TTL=255
Reply from 12.253.30.1: bytes=32 time=15ms TTL=255
Reply from 12.253.30.1: bytes=32 time=62ms TTL=255
Reply from 12.253.30.1: bytes=32 time=13ms TTL=255

Ping statistics for 12.253.30.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 62ms, Average = 25ms

Denver CO (80234) 8:30 pm MDT
--
The Hokey Pokey - What if that's what it's all about?
permalink · 2002-09-24 22:30:16 · Print ·

biff420
Premium
join:2002-01-26
Richmond, CA
·AT&T Yahoo

 Gateway pings in Berkeley

C:\Documents and Settings\biff>ping 12.233.44.1

Pinging 12.233.44.1 with 32 bytes of data:

Reply from 12.233.44.1: bytes=32 time=35ms TTL=255
Reply from 12.233.44.1: bytes=32 time=34ms TTL=255
Reply from 12.233.44.1: bytes=32 time=10ms TTL=255
Reply from 12.233.44.1: bytes=32 time=13ms TTL=255

Ping statistics for 12.233.44.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 35ms, Average = 23ms
permalink · 2002-09-24 22:42:53 · Print ·

moshua

join:2001-03-13
Stow, MA

 >ping 24.91.216.1

Pinging 24.91.216.1 with 32 bytes of data:

Reply from 24.91.216.1: bytes=32 time=91ms TTL=254
Reply from 24.91.216.1: bytes=32 time=148ms TTL=254
Reply from 24.91.216.1: bytes=32 time=57ms TTL=254
Reply from 24.91.216.1: bytes=32 time=97ms TTL=254

Ping statistics for 24.91.216.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 57ms, Maximum = 148ms, Average = 98ms

Boston, MA area @ 10:45 EDT
permalink · 2002-09-24 22:47:30 · Print ·

laprjns
Premium
join:2002-03-11
Ellington, CT
·AT&T Yahoo
·Comcast Formerly ..

sorry about the graphics, don't know how to copy from a dos window.

ping'ed around 10:40pm. ellington ct.
[text was edited by author 2002-09-24 22:53:33]
permalink · 2002-09-24 22:51:35 · Print ·
jdir

join:2001-05-04
Santa Clara, CA		 Geez, wouldnt it make more sense to ping some known host - ie Yahoo.com rather than your gateway?
permalink · 2002-09-25 00:53:36 ·
ChuC

join:2001-12-18

Re: Post here the ping times to your gateway

jdir, in a reasonable system, the ping time to one's own gateway will be very low, say below 30 ms or so. Everything has to go thru one's gateway, before getting to anywhere. The ping time being so bad at some places shows a fundamental problem. BTW, associated with this high ping time here, is a very slow net experience in general. This started about two weeks ago.

Tonight the ping time has improved a bit for me (compared to the last few evenings), and the net appears a bit better.
permalink · 2002-09-25 01:06:24 ·
pheebau

join:2001-12-12
El Cerrito, CA

 The usual...bad...and at midnight...

Pinging 12.233.156.1 with 32 bytes of data:

Reply from 12.233.156.1: bytes=32 time=160ms TTL=255
Reply from 12.233.156.1: bytes=32 time=128ms TTL=255
Reply from 12.233.156.1: bytes=32 time=254ms TTL=255
Reply from 12.233.156.1: bytes=32 time=40ms TTL=255
Reply from 12.233.156.1: bytes=32 time=81ms TTL=255
Reply from 12.233.156.1: bytes=32 time=359ms TTL=255
Reply from 12.233.156.1: bytes=32 time=137ms TTL=255
Reply from 12.233.156.1: bytes=32 time=25ms TTL=255
Reply from 12.233.156.1: bytes=32 time=145ms TTL=255
Reply from 12.233.156.1: bytes=32 time=136ms TTL=255
Reply from 12.233.156.1: bytes=32 time=73ms TTL=255
Reply from 12.233.156.1: bytes=32 time=243ms TTL=255
Reply from 12.233.156.1: bytes=32 time=172ms TTL=255
Reply from 12.233.156.1: bytes=32 time=135ms TTL=255
Reply from 12.233.156.1: bytes=32 time=191ms TTL=255
Reply from 12.233.156.1: bytes=32 time=326ms TTL=255
Reply from 12.233.156.1: bytes=32 time=164ms TTL=255
Reply from 12.233.156.1: bytes=32 time=326ms TTL=255
Reply from 12.233.156.1: bytes=32 time=386ms TTL=255
Reply from 12.233.156.1: bytes=32 time=343ms TTL=255
Reply from 12.233.156.1: bytes=32 time=139ms TTL=255
Reply from 12.233.156.1: bytes=32 time=337ms TTL=255
Reply from 12.233.156.1: bytes=32 time=240ms TTL=255
Reply from 12.233.156.1: bytes=32 time=147ms TTL=255
Reply from 12.233.156.1: bytes=32 time=39ms TTL=255
Reply from 12.233.156.1: bytes=32 time=226ms TTL=255
Reply from 12.233.156.1: bytes=32 time=192ms TTL=255
Reply from 12.233.156.1: bytes=32 time=221ms TTL=255
Reply from 12.233.156.1: bytes=32 time=222ms TTL=255
Reply from 12.233.156.1: bytes=32 time=120ms TTL=255
Reply from 12.233.156.1: bytes=32 time=268ms TTL=255
Reply from 12.233.156.1: bytes=32 time=219ms TTL=255
Reply from 12.233.156.1: bytes=32 time=201ms TTL=255
Reply from 12.233.156.1: bytes=32 time=172ms TTL=255
Reply from 12.233.156.1: bytes=32 time=134ms TTL=255
Reply from 12.233.156.1: bytes=32 time=145ms TTL=255
Reply from 12.233.156.1: bytes=32 time=203ms TTL=255
Reply from 12.233.156.1: bytes=32 time=195ms TTL=255
Reply from 12.233.156.1: bytes=32 time=141ms TTL=255
Reply from 12.233.156.1: bytes=32 time=218ms TTL=255
Reply from 12.233.156.1: bytes=32 time=34ms TTL=255
Reply from 12.233.156.1: bytes=32 time=42ms TTL=255
Reply from 12.233.156.1: bytes=32 time=163ms TTL=255
Reply from 12.233.156.1: bytes=32 time=141ms TTL=255

Ping statistics for 12.233.156.1:
Packets: Sent = 44, Received = 44, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 25ms, Maximum = 386ms, Average = 181ms
permalink · 2002-09-25 03:16:09 · Print ·

Holyearth
I Like This Forum

join:2002-07-18
Atlanta, GA

Re: Post here the ping times to your gateway

1:50 PM -- Atlanta, GA 30308

C:\>ping -n 10 10.238.136.1

Pinging 10.238.136.1 with 32 bytes of data:

Reply from 10.238.136.1: bytes=32 time=73ms TTL=255
Reply from 10.238.136.1: bytes=32 time=16ms TTL=255
Reply from 10.238.136.1: bytes=32 time=33ms TTL=255
Reply from 10.238.136.1: bytes=32 time=27ms TTL=255
Reply from 10.238.136.1: bytes=32 time=25ms TTL=255
Reply from 10.238.136.1: bytes=32 time=27ms TTL=255
Reply from 10.238.136.1: bytes=32 time=17ms TTL=255
Reply from 10.238.136.1: bytes=32 time=85ms TTL=255
Reply from 10.238.136.1: bytes=32 time=24ms TTL=255
Reply from 10.238.136.1: bytes=32 time=15ms TTL=255

Ping statistics for 10.238.136.1:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 15ms, Maximum = 85ms, Average = 34ms
permalink · 2002-09-25 13:50:48 · Print ·
cury19

join:2002-09-02
Weatogue, CT

 Here's my pings.

Reply from 12.243.112.1: bytes=32 time=8ms TTL=255
Reply from 12.243.112.1: bytes=32 time=12ms TTL=255
Reply from 12.243.112.1: bytes=32 time=44ms TTL=255
Reply from 12.243.112.1: bytes=32 time=8ms TTL=255
Reply from 12.243.112.1: bytes=32 time=8ms TTL=255
Reply from 12.243.112.1: bytes=32 time=8ms TTL=255
Reply from 12.243.112.1: bytes=32 time=26ms TTL=255
Reply from 12.243.112.1: bytes=32 time=18ms TTL=255
Reply from 12.243.112.1: bytes=32 time=18ms TTL=255
Reply from 12.243.112.1: bytes=32 time=10ms TTL=255

Ping statistics for 12.243.112.1:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 8ms, Maximum = 44ms, Average = 16ms
permalink · 2002-09-25 19:08:30 · Print ·
pheebau

join:2001-12-12
El Cerrito, CA

 ChuC,

Good luck - I tried and am even talking to local tech everyday...always the same song...still nothing...headend is bad but everytime I ask precised questions, I get no answer and the local tier2 tell me they don't know much about what the headend people are doing - I also asked about the upstreams channel width 15 times and still have not gotten any answer...

if you want data, I can send you A LOT of data - I traced data for the last 4 weeks so I got some interesting ones for the bay area

Anyhow...Am so pissed-off and frustrated that my DSL will come soon...to give you some idea - all my friends with their DSL ping CONSTANTLY the same low value to my ATT gateway (even 1 friend in Oregon with a slow DSL gets good ping time...)...I think Cable is particular as the line is shared by everyone so it might work in a good day or if your neighborhood is not too crowded and then change all of a sudden dramatically overnight leaving you perplex about the thing...PM me if you wanna discuss/know more...
permalink · 2002-09-25 03:22:06 · Print ·

LarryE

join:2000-07-29
Chicago, IL		 Thanks for your help in finding my gateway!

Ping statistics for 12.247.166.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 8ms, Maximum = 13ms, Average = 9ms
permalink · 2002-09-25 03:29:01 ·
teck9

join:2002-05-02
Fort Lauderdale, FL

 The best on here

Reply from 66.176.24.1: bytes=32 time=7ms TTL=255
Reply from 66.176.24.1: bytes=32 time=9ms TTL=255
Reply from 66.176.24.1: bytes=32 time=8ms TTL=255
Reply from 66.176.24.1: bytes=32 time=8ms TTL=255
Reply from 66.176.24.1: bytes=32 time=6ms TTL=255
Reply from 66.176.24.1: bytes=32 time=7ms TTL=255
Reply from 66.176.24.1: bytes=32 time=9ms TTL=255
Reply from 66.176.24.1: bytes=32 time=11ms TTL=255
Reply from 66.176.24.1: bytes=32 time=7ms TTL=255
Reply from 66.176.24.1: bytes=32 time=7ms TTL=255

Ping statistics for 66.176.24.1:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 11ms, Average = 7ms
permalink · 2002-09-25 13:17:54 · Print ·

SlyBry
Slyest Of All The Brys
Premium
join:2002-08-26
Manchester, NH

Re: Post here the ping times to your gateway

said by teck9 See Profile:
The best on here
Correction.... you were. =)

Pinging 24.147.72.1 with 32 bytes of data:

Reply from 24.147.72.1: bytes=32 time=3ms TTL=255
Reply from 24.147.72.1: bytes=32 time=3ms TTL=255
Reply from 24.147.72.1: bytes=32 time=3ms TTL=255
Reply from 24.147.72.1: bytes=32 time=2ms TTL=255
Reply from 24.147.72.1: bytes=32 time=3ms TTL=255
Reply from 24.147.72.1: bytes=32 time=3ms TTL=255
Reply from 24.147.72.1: bytes=32 time=3ms TTL=255
Reply from 24.147.72.1: bytes=32 time=3ms TTL=255
Reply from 24.147.72.1: bytes=32 time=4ms TTL=255
Reply from 24.147.72.1: bytes=32 time=3ms TTL=255

Ping statistics for 24.147.72.1:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 4ms, Average = 3ms
permalink · 2002-09-26 01:17:20 · Print ·

13120635
Watching in silence
Premium
join:2001-01-03
Aurora, CO

 Pinging gateway.attbi.com [63.240.76.6] with 32 bytes of data:

Reply from 63.240.76.6: bytes=32 time=63ms TTL=49
Reply from 63.240.76.6: bytes=32 time=66ms TTL=49
Reply from 63.240.76.6: bytes=32 time=64ms TTL=49
Reply from 63.240.76.6: bytes=32 time=64ms TTL=49

Ping statistics for 63.240.76.6:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 63ms, Maximum = 66ms, Average = 64ms

Okay I guess.
--
Put them in the iron maiden!
permalink · 2002-09-25 13:37:07 · Print ·
Forums » The Site » Old Forums » AT&T BroadbandATTBI internet and cable television »
« South San Jose Deployment Date  
page: 1 · 2 · 3

Wednesday, 09-Dec 11:22:25 Terms of Use | Privacy Policy | Hosting by www.nac.net - DSL,Hosting & Co-lo | feedback | contact
over 10 years online! © 1999-2009 dslreports.com.
page compression OFF
Most commented news this week
· [197] Sprint Sued For Distracted Driving Death
· [81] 3G Network Test Says AT&T Is Tops
· [72] Mediacom Unveils 105 Mbps Pricing
· [65] Sprint Poised For A Turnaround?
· [56] WPA Cracker: Test WPA-PSK Networks In 20 Minutes
· [50] The Future Of Wi-Fi Is Bright
· [47] Site Leaks Yahoo, Verizon Fed Data Share Pricing
· [44] Microwaving Your Innards Is Not 'Extreme'
· [43] AT&T Launching New 24 Mbps U-Verse Tier
· [39] Verizon LTE: 5-12 Mbps Downstream
Most people now reading
· Comcast refused to install 400' feet. [Comcast HSI]
· HOA Headaches [General Questions]
· [How to] Install Asterisk on an Asus WL-520GU router [VOIP Tech Chat]
· Cross Server Dungeon Experience [World of Warcraft]
· Is sleeping similar to being dead? [General Questions]
· [Gold] Making a Killing on Patch Day [World of Warcraft]
· Windows 7 boot manager editing questions [Microsoft Help]
· CRTC Response to ME: You will be Band F FOREVER!!! [TekSavvy]
· 5 weeks and still no internet [TekSavvy]
· persistent connection to qw-in-f113.1e100.net on boot [Security]