Re: GTS - Szczecin - Grupy dyskusyjne w eGospodarka.pl

eGospodarka.pl › Grupy › pl.internet.polip › GTS - Szczecin › Re: GTS - Szczecin

Path: news-archive.icm.edu.pl!mat.uni.torun.pl!news.man.torun.pl!newsfeed.pionier.net
.pl!news.gazeta.pl!newsfeed.gazeta.pl!newsfeed.tpinternet.pl!atlantis.news.tpi.
pl!news.tpi.pl!not-for-mail
From: Marek Burzyński <m...@c...pl>
Newsgroups: pl.internet.polip
Subject: Re: GTS - Szczecin
Date: Wed, 03 Jan 2007 01:14:50 +0100
Organization: tp.internet - http://www.tpi.pl/
Lines: 80
Message-ID: <enesob$m66$1@nemesis.news.tpi.pl>
References: <enef6t$217t$1@news2.ipartners.pl> <enegjf$224o$1@news2.ipartners.pl>
NNTP-Posting-Host: eit60.neoplus.adsl.tpnet.pl
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-2; format=flowed
Content-Transfer-Encoding: 8bit
X-Trace: nemesis.news.tpi.pl 1167783500 22726 83.21.135.60 (3 Jan 2007 00:18:20 GMT)
X-Complaints-To: u...@t...pl
NNTP-Posting-Date: Wed, 3 Jan 2007 00:18:20 +0000 (UTC)
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
In-Reply-To: <enegjf$224o$1@news2.ipartners.pl>
Xref: news-archive.icm.edu.pl pl.internet.polip:79695
[ ukryj nagłówki ]
Atman :

PING wp.pl (212.77.100.101): 56 data bytes
64 bytes from 212.77.100.101: icmp_seq=0 ttl=123 time=6.902 ms
64 bytes from 212.77.100.101: icmp_seq=1 ttl=123 time=7.138 ms
64 bytes from 212.77.100.101: icmp_seq=2 ttl=123 time=7.214 ms
64 bytes from 212.77.100.101: icmp_seq=3 ttl=123 time=8.089 ms
64 bytes from 212.77.100.101: icmp_seq=4 ttl=123 time=7.231 ms

--- wp.pl ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max/stddev = 6.902/7.315/8.089/0.405 ms

Nask:

traceroute wp.pl.
Translating "wp.pl."...domain server (193.59.201.27) [OK]

Tracing the route to wp.pl (212.77.100.101)

1 uw-gw0-at3-0-0-1.core.nask.pl (195.187.254.238) 0 msec
pw-gw0-at2-0-0-1.core.nask.pl (195.187.254.246) 0 msec
uw-gw0-at3-0-0-1.core.nask.pl (195.187.254.238) 0 msec
2 pw-gw2-gi1-2-0-110.warman.nask.pl (195.187.244.196) 0 msec 4 msec 0
msec
3 z-nask-com.warszawa-gw.10Gb.rtr.pionier.gov.pl (212.191.226.17) [AS
8501] 12 msec 4 msec 0 msec
4 lodz-gw.ge.rtr.pionier.gov.pl (212.191.126.17) [AS 8501] 4 msec 0
msec 4 msec
5 z-lodz-gw.gdansk.10Gb.rtr.pionier.gov.pl (212.191.225.38) [AS 8501]
16 msec 16 msec 12 msec
6 ci-wp-rtr.wp.pl (153.19.102.1) [AS 5550] 12 msec 12 msec 16 msec
7 zew.rtrd2.adm.wp-sa.pl (212.77.105.29) [AS 12827] 12 msec 12 msec
12 msec

Telia [Amsterdam]

Tracing the route to wp.pl (212.77.100.101)

1 adm-bb2-link.telia.net (80.91.249.227) 0 msec
adm-bb1-pos1-0-0-0.telia.net (213.248.72.137) 0 msec
adm-bb1-link.telia.net (80.91.249.217) 0 msec
2 hbg-bb1-pos7-1-0.telia.net (213.248.65.154) 4 msec
hbg-bb2-pos7-0-0.telia.net (213.248.65.162) 8 msec 8 msec
3 hbg-bb1-pos0-0-0.telia.net (213.248.64.221) [MPLS: Label 208256 Exp
0] 4 msec
war-b3-pos6-0-0.telia.net (213.248.96.2) 24 msec
hbg-bb1-pos0-0-0.telia.net (213.248.64.221) [MPLS: Label 208256 Exp
0] 8 msec
4 war-b3-pos6-0-0.telia.net (213.248.96.2) 24 msec
tpsa-01622-war-b3.c.telia.net (213.248.79.18) 20 msec 20 msec
5 so-2-2-0.war-tr3.tpnet.pl (195.149.232.33) [AS 29535] 24 msec
tpsa-01622-war-b3.c.telia.net (213.248.79.18) 24 msec 24 msec
6 so-2-2-0.war-tr3.tpnet.pl (195.149.232.33) [AS 29535] 24 msec
195.149.233.26 [AS 29535] 32 msec 28 msec
7 zew.rtrd2.adm.wp-sa.pl (212.77.105.29) [AS 12827] 32 msec
195.149.233.26 [AS 29535] 28 msec 32 msec
8 zew.rtrd2.adm.wp-sa.pl (212.77.105.29) [AS 12827] 32 msec * 28 msec

Level3 [San Francisco]

icmp_seq=0 time=196 ms
icmp_seq=1 time=188 ms
icmp_seq=2 time=188 ms
icmp_seq=3 time=192 ms
icmp_seq=4 time=188 ms
icmp_seq=5 time=188 ms
icmp_seq=6 time=188 ms

Więc wszystkim chodzi, GTS'owi nie, więc normalny człowiek pomyślał by
że to wina GTS