google cache

[Тодор Лазаров]

погледнете прикачената картинка

Нищо особено само дето на този адрес се отваря google.bg и пинг е 4 ms

доставчика ми е: telehouse

Редактирано 21 Март, 2013 от Тодор Лазаров

[111111]

Това е някакъв мирър със странни параметри тотално различни от офицялните

178.132.81.12 - Whois информация

#

# Query terms are ambiguous. The query is assumed to be:

# "n 178.132.81.49"

#

# Use "?" to get help.

#

#

# The following results may also be obtained via:

# http://whois.arin.net/rest/nets;q=178.132.81.49?showDetails=true&showARIN=false&ext=netref2

#

NetRange: 178.0.0.0 - 178.255.255.255

CIDR: 178.0.0.0/8

OriginAS:

NetName: 178-RIPE

NetHandle: NET-178-0-0-0-1

Parent:

NetType: Allocated to RIPE NCC

Comment: These addresses have been further assigned to users in

Comment: the RIPE NCC region. Contact information can be found in

Comment: the RIPE database at http://www.ripe.net/whois

RegDate: 2009-01-30

Updated: 2009-05-18

Ref: http://whois.arin.net/rest/net/NET-178-0-0-0-1

OrgName: RIPE Network Coordination Centre

OrgId: RIPE

Address: P.O. Box 10096

City: Amsterdam

StateProv:

PostalCode: 1001EB

Country: NL

RegDate:

Updated: 2011-09-24

Ref: http://whois.arin.net/rest/org/RIPE

ReferralServer: whois://whois.ripe.net:43

OrgTechHandle: RNO29-ARIN

OrgTechName: RIPE NCC Operations

OrgTechPhone: +31 20 535 4444

OrgTechEmail: hostmaster@ripe.net

OrgTechRef: http://whois.arin.net/rest/poc/RNO29-ARIN'>http://whois.arin.net/rest/poc/RNO29-ARIN

OrgAbuseHandle: RNO29-ARIN

OrgAbuseName: RIPE NCC Operations

OrgAbusePhone: +31 20 535 4444

OrgAbuseEmail: hostmaster@ripe.net

OrgAbuseRef: http://whois.arin.net/rest/poc/RNO29-ARIN'>http://whois.arin.net/rest/poc/RNO29-ARIN

#

# ARIN WHOIS data and services are subject to the Terms of Use

# available at: https://www.arin.net/whois_tou.html

#

Found a referral to whois.ripe.net:43.

% This is the RIPE Database query service.

% The objects are in RPSL format.

%

% The RIPE Database is subject to Terms and Conditions.

% See http://www.ripe.net/db/support/db-terms-conditions.pdf

% Note: this output has been filtered.

% To receive output for a database update, use the "-B" flag.

% Information related to '178.132.80.0 - 178.132.81.255'

inetnum: 178.132.80.0 - 178.132.81.255

netname: Telehouse

remarks: INFRA-AW

descr: Telehouse EAD

country: BG

admin-c: AZ3665-RIPE

tech-c: ND2157-RIPE

status: ASSIGNED PA

mnt-by: AZ39139-MNT

source: RIPE # Filtered

person: Andon Zlatev

address: 122 Ovche pole str.

address: Sofia, Bulgaria

phone: +35924903211

nic-hdl: AZ3665-RIPE

mnt-by: AZ39139-MNT

source: RIPE # Filtered

person: Nedko Dimitrov

address: 122 Ovche pole str.

address: Sofia, Bulgaria

phone: +359 893590193

nic-hdl: ND2157-RIPE

mnt-by: AZ39139-MNT

source: RIPE # Filtered

% Information related to '178.132.80.0/23AS57344'

route: 178.132.80.0/23

descr: Telehouse EAD

origin: AS57344

mnt-by: AZ39139-MNT

source: RIPE # Filtered

% This query was served by the RIPE Database Query Service version 1.57.1 (WHOIS2)

[Mupo neTkoB]

щом и доставчика ти е телехаус даже доста големи латенции имаш до това ип

http://whois.domaintools.com/178.132.81.12

[NetworkPro]

http://smartage.bg/М.-Горанов,-Телепоинт:-Колокацията-е-услуга-на-бъдещето/?go=detail&articleId=2555 Редактирано 21 Март, 2013 от NetworkPro

[Тодор Лазаров]

щом и доставчика ти е телехаус даже доста големи латенции имаш до това ип

http://whois.domaint...m/178.132.81.12

това е от пампорово, смолян

като тествам headersна веб сервер-а ми дава:

Header are:

HTTP/1.1 200 OK

Date: Fri, 22 Mar 2013 05:30:47 GMT

Expires: -1

Cache-Control: private, max-age=0

Content-Type: text/html; charset=UTF-8

Set-Cookie: NID=67=ntfyFqAp-ff5d8wDqEVWgGLBJFOfJhBJUHiKykMhfJkkvgmlyOZ7n3uWv9yxqZxykLO51_gVmDE29wEAnzIwFP4AlnqehXxSZMZiB1GXWFO5UTg_Fy7U4af69RC9JABV; expires=Sat, 21-Sep-2013 05:30:47 GMT; path=/; domain=.; HttpOnly

P3P: CP="This is not a P3P policy! See http://www.google.com/support/accounts/bin/answer.py?hl=en&answer=151657 for more info."

Server: gws

X-XSS-Protection: 1; mode=block

X-Frame-Options: SAMEORIGIN

Transfer-Encoding: chunked

иначе е супер доста бързичко

Редактирано 22 Март, 2013 от Тодор Лазаров

[MiPSus]

Защо се учудваш, в БГ има поне 3 кеша на Google(YouTube)/Facebook(Akamai) които знам - БТК , Телехаус (Пауърнет) и BIX.bg

При нас е:

root@nbr:~# ping google.bg

PING google.bg (212.39.82.182) 56(84) bytes of data.

64 bytes from 182-82.btc-net.bg (212.39.82.182): icmp_req=1 ttl=62 time=0.811 mst

64 bytes from 182-82.btc-net.bg (212.39.82.182): icmp_req=2 ttl=62 time=0.818 ms

64 bytes from 182-82.btc-net.bg (212.39.82.182): icmp_req=3 ttl=62 time=0.908 ms

64 bytes from 182-82.btc-net.bg (212.39.82.182): icmp_req=4 ttl=62 time=0.934 ms

Редактирано 22 Март, 2013 от MiPSus

[vv1]

При нас като чели в началото беше по добре с : "ms".

PING youtube.com (212.39.82.183) 56(84) bytes of data.

64 bytes from 183-82.btc-net.bg (212.39.82.183): icmp_req=1 ttl=60 time=9.90 ms

64 bytes from 183-82.btc-net.bg (212.39.82.183): icmp_req=2 ttl=60 time=10.3 ms

64 bytes from 183-82.btc-net.bg (212.39.82.183): icmp_req=3 ttl=60 time=9.75 ms

64 bytes from 183-82.btc-net.bg (212.39.82.183): icmp_req=4 ttl=60 time=11.2 ms

PING google.com (212.39.82.178) 56(84) bytes of data.

64 bytes from 178-82.btc-net.bg (212.39.82.178): icmp_req=1 ttl=60 time=9.97 ms

64 bytes from 178-82.btc-net.bg (212.39.82.178): icmp_req=2 ttl=60 time=9.93 ms

64 bytes from 178-82.btc-net.bg (212.39.82.178): icmp_req=3 ttl=60 time=10.0 ms

64 bytes from 178-82.btc-net.bg (212.39.82.178): icmp_req=4 ttl=60 time=10.1 ms

64 bytes from 178-82.btc-net.bg (212.39.82.178): icmp_req=5 ttl=60 time=10.3 ms

Редактирано 22 Март, 2013 от sairos

[111111]

Технически погледнато ако са обновени DNS записите гугъл щеше да прехвърля натам

все пак те имат един от опорните DNS сървъри

но от друга страна когато се ползва директно заявка към 8,8,8,8 и 8,8,4,4 от бг ип-то не ме праща там

[Mitko]

Хъм при мен излиза съвсем друго като адрес:

PING google.bg (173.194.39.255) 56(84) bytes of data.

64 bytes from sof01s02-in-f31.1e100.net (173.194.39.255): icmp_seq=1 ttl=59 time=1.55 ms

64 bytes from sof01s02-in-f31.1e100.net (173.194.39.255): icmp_seq=2 ttl=59 time=1.95 ms

64 bytes from sof01s02-in-f31.1e100.net (173.194.39.255): icmp_seq=3 ttl=59 time=1.52 ms

64 bytes from sof01s02-in-f31.1e100.net (173.194.39.255): icmp_seq=4 ttl=59 time=0.982 ms

64 bytes from sof01s02-in-f31.1e100.net (173.194.39.255): icmp_seq=6 ttl=59 time=0.810 ms

64 bytes from sof01s02-in-f31.1e100.net (173.194.39.255): icmp_seq=7 ttl=59 time=1.38 ms

64 bytes from sof01s02-in-f31.1e100.net (173.194.39.255): icmp_seq=8 ttl=59 time=0.825 ms

64 bytes from sof01s02-in-f31.1e100.net (173.194.39.255): icmp_seq=9 ttl=59 time=0.812 ms

PING youtube.com (173.194.39.227) 56(84) bytes of data.

64 bytes from sof01s02-in-f3.1e100.net (173.194.39.227): icmp_seq=1 ttl=59 time=1.74 ms

64 bytes from sof01s02-in-f3.1e100.net (173.194.39.227): icmp_seq=2 ttl=59 time=1.01 ms

64 bytes from sof01s02-in-f3.1e100.net (173.194.39.227): icmp_seq=3 ttl=59 time=1.71 ms

64 bytes from sof01s02-in-f3.1e100.net (173.194.39.227): icmp_seq=4 ttl=59 time=2.10 ms

64 bytes from sof01s02-in-f3.1e100.net (173.194.39.227): icmp_seq=5 ttl=59 time=1.62 ms

64 bytes from sof01s02-in-f3.1e100.net (173.194.39.227): icmp_seq=6 ttl=59 time=0.783 ms

[111111]

нормално е да се ползва цяла С мрежа за балансиране на натоварването

google.bg youtube.com gmail.com при мен ги отваря от 173.194.39.0/24