[19123] in North American Network Operators' Group
RE: Sprint/HiNet
daemon@ATHENA.MIT.EDU (Barry Raveendran Greene)
Wed Aug 26 20:56:49 1998
Reply-To: <bgreene@cisco.com>
From: "Barry Raveendran Greene" <bgreene@cisco.com>
To: <william@pacific.net.ph>, <nanog@merit.edu>, "APOPS" <apops@apnic.net>
Date: Thu, 27 Aug 1998 08:47:07 +0800
In-Reply-To: <3.0.1.32.19980827025523.01520828@pacific.net.ph>
Hi William,
APOPS is the more appropriate forum for a problem with HiNet.
Barry
> -----Original Message-----
> From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu]On Behalf Of
> william@pacific.net.ph
> Sent: Thursday, August 27, 1998 2:55 AM
> To: nanog@merit.edu
> Subject: Sprint/HiNet
>
>
>
> Hi all!
>
> Whenever we do a traceroute from our Sprint connection to a host in the
> HiNet network, we get timed out in the Sprint/HiNet link, as follows:
>
> Tracing route to w3.hinet.net [168.95.1.82]
> over a maximum of 30 hops:
>
> 1 138 ms 116 ms 113 ms pi-ph-ts01.pacific.net.ph [210.23.234.128]
> 2 142 ms 111 ms 116 ms pi-ph-gw01.pacific.net.ph [210.23.234.1]
> 3 332 ms 330 ms 340 ms 204.59.178.25
> 4 375 ms 324 ms 328 ms 204.59.120.198
> 5 323 ms 322 ms 339 ms 144.232.1.153
> 6 380 ms 366 ms 365 ms 144.232.8.70
> 7 347 ms 373 ms 374 ms 144.232.4.142
> 8 * * * Request timed out.
> 9 546 ms 529 ms 523 ms 168.95.253.126
> 10 540 ms 532 ms 540 ms 168.95.253.189
> 11 547 ms 556 ms 547 ms w3.hinet.net [168.95.1.82]
>
> Trace complete.
>
> Line 8 is always like this and a customer of ours is complaining about it.
> Is this a time out or congestion or something else?
>
> William
>
>
