Jump to content

Recommended Posts

Posted

Asked whois.ripe.net:43 about 84.233.223.146)

 

inetnum: 84.233.223.0 - 84.233.223.255

netname: UK-INTEROUTE-INTERFACES

descr: Customer P2P interface addresses in UK

remarks: INFRA-AW

remarks: Interoute IP network - [email protected]

for complaints

country: GB

admin-c: INTR1-RIPE

tech-c: INTR1-RIPE

status: ASSIGNED PA

mnt-by: INTEROUTE-MNTNR

mnt-lower: INTEROUTE-MNTNR

source: RIPE Filtered

role: Interoute IP Hostmaster

address: Interoute Communications Ltd.

address: Wallbrook House

address: 195 Marsh Wall

address: E14 9SG

address: LONDON

e-mail: [email protected]

 

admin-c: ADAM1-RIPE

admin-c: SP1799-RIPE

admin-c: JK911-RIPE

admin-c: ASL13-RIPE

tech-c: ADAM1-RIPE

tech-c: SP1799-RIPE

tech-c: JK911-RIPE

tech-c: ASL13-RIPE

nic-hdl: INTR1-RIPE

mnt-by: INTEROUTE-MNTNR

source: RIPE Filtered

route: 84.233.128.0/17

descr: Interoute Telecommunications (UK) Ltd

origin: AS8928

mnt-by: INTEROUTE-MNTNR

source: RIPE Filtered

Posted

May be that the later routers are configured not to respond to ICMP? I get timeouts too when doing a tracert, but the site is loading up fine.

 

4 143 ms 146 ms 144 ms po2-104.cr05.hx2.bb.gxn.net [62.72.139.25]

5 190 ms 349 ms 36 ms ge0-1.lonap.lon.rapidswitch.com [193.203.5.86]

6 * * * Request timed out.

7 * * * Request timed out.

8 * * * Request timed out.

9 737 ms 247 ms 112 ms montrose.just4dns.com [78.129.134.30]

Posted
You can use tcptraceroute to port 80 to give you a bit more info, gets round routers dropping ICMP packets. It's not perfect but can help depending on the problem.
  • Thanks 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...