Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Where are Iperweb's servers?
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Where are Iperweb's servers?

rev3rserev3rse Member
edited July 2012 in General

Hello everyone,

I just wanted to know where IperWeb's servers locations? I know they're in Italy, but they offered 2 IP's to test, and they have different pings which led me to think that they have more than one location.

Comments

  • prometeusprometeus Member, Host Rep

    They are in the same racks :)

  • @prometeus said: They are in the same racks :)

    >
    Thanks for answering, already got one anyway :>

  • SpiritSpirit Member
    edited August 2012

    @rev3rse said: but they offered 2 IP's to test, and they have different pings

    Interesting - I am getting around 20ms difference between IPs and nodes I am hosted too.

    Pinging 194.14.179.254 with 32 bytes of data:
    
    Reply from 194.14.179.254: bytes=32 time=43ms TTL=52
    Reply from 194.14.179.254: bytes=32 time=43ms TTL=52
    Reply from 194.14.179.254: bytes=32 time=44ms TTL=52
    Reply from 194.14.179.254: bytes=32 time=46ms TTL=52
    
    Ping statistics for 194.14.179.254:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 43ms, Maximum = 46ms, Average = 44ms

    &&

    Pinging 195.88.4.7 with 32 bytes of data:
    
    Reply from 195.88.4.7: bytes=32 time=64ms TTL=51
    Reply from 195.88.4.7: bytes=32 time=58ms TTL=51
    Reply from 195.88.4.7: bytes=32 time=64ms TTL=51
    Reply from 195.88.4.7: bytes=32 time=59ms TTL=51
    
    Ping statistics for 195.88.4.7:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 58ms, Maximum = 64ms, Average = 61ms
    Tracing route to labrea.prometeus.net [194.14.179.254]
    over a maximum of 30 hops:
    
    ...
      7    19 ms    22 ms    19 ms  win-b4-link.telia.net [213.248.75.109]
      8    20 ms    21 ms    20 ms  win-bb2-link.telia.net [80.91.247.0]
      9    33 ms    35 ms    34 ms  ffm-bb2-link.telia.net [80.91.246.30]
     10     *        *       34 ms  ffm-b10-link.telia.net [80.91.251.250]
     11    46 ms    46 ms    45 ms  te-9-3-0.edge4.Frankfurt1.level3.net [4.68.111.1
    01]
     12    45 ms    45 ms    51 ms  vlan90.csw4.Frankfurt1.Level3.net [4.69.154.254]
    
     13    46 ms    46 ms    45 ms  ae-91-91.ebr1.Frankfurt1.Level3.net [4.69.140.13
    ]
     14    54 ms    53 ms    58 ms  ae-1-14.bar2.Milan1.Level3.net [4.69.142.193]
     15    59 ms    59 ms    58 ms  212.73.241.130
     16    60 ms    60 ms    65 ms  217.171.46.241
     17    48 ms    46 ms    41 ms  labrea.prometeus.net [194.14.179.254]
    
    Trace complete.
    Tracing route to pm07.prometeus.net [195.88.4.7]
    over a maximum of 30 hops:
    
    ...
      7    20 ms    20 ms    18 ms  win-b4-link.telia.net [213.248.75.109]
      8    20 ms    21 ms    19 ms  win-bb2-link.telia.net [213.155.132.128]
      9    74 ms    33 ms    33 ms  ffm-bb2-link.telia.net [80.91.246.140]
     10    32 ms    36 ms     *     ffm-b10-link.telia.net [80.91.251.124]
     11    89 ms    48 ms    43 ms  4.68.62.173
     12    46 ms    49 ms    45 ms  vlan60.csw1.Frankfurt1.Level3.net [4.69.154.62]
    
     13    46 ms    45 ms    45 ms  ae-61-61.ebr1.Frankfurt1.Level3.net [4.69.140.1]
    
     14    53 ms    53 ms    56 ms  ae-1-14.bar2.Milan1.Level3.net [4.69.142.193]
     15    57 ms    57 ms    57 ms  212.73.241.130
     16    45 ms    44 ms    44 ms  gw-umusic-v.umusic.cdlan.net [217.171.46.251]
     17    59 ms    59 ms    58 ms  pm07.prometeus.net [195.88.4.7]
    
    Trace complete.

    I tryed few different nodes (my own dedicated IP)

    Node    pm19
    Node    pm22
        Minimum = 47ms, Maximum = 50ms, Average = 48ms
    
    Node    pm12
        Minimum = 65ms, Maximum = 69ms, Average = 66ms
    
  • @prometeus said: They are in the same racks :)

    They're not taking up the same space?!

    BLASPHEMY. As compensation I demand a VPS sale!

    Thanked by 1NanoG6
  • @HalfEatenPie said: BLASPHEMY. As compensation I demand a VPS sale!

    NO! make them FREE at this time!

  • Not sure trolling or serious

    Thanked by 1yomero
  • Welcome to the support forum of IperWeb!

    Thanked by 1Mon5t3r
  • It would be nice to :D

  • @HalfEatenPie said: BLASPHEMY. As compensation I demand a VPS sale!

    There is an ongoing windows sale... go grab one...

  • prometeusprometeus Member, Host Rep

    the 195.88.4.0/23 net is announced directly under our upstream AS, while other nets are under our own AS. In traceroute you will see the last ip before the target is different and that's the only difference on our side...

    @Spirit said: Node pm19

    Node pm22

    Minimum = 47ms, Maximum = 50ms, Average = 48ms

    >

    Node pm12

    Minimum = 65ms, Maximum = 69ms, Average = 66ms

    this is unexplicable as the nodes use all IP announced under our own AS

    ....

  • MaouniqueMaounique Host Rep, Veteran
    edited August 2012

    Try some traceroutes. I suspect that, since there are more possible routes, it does not go all the time through the same path.
    Even if it does, you can see where the difference begins to show.
    From what Spirit put up, I see the difference appears towards the end.

    @breton said: Welcome to the support forum of IperWeb!

    Indeed, is there a forum at iperweb/prometeus ?

    M

  • prometeusprometeus Member, Host Rep

    @Maounique said: Indeed, is there a forum at iperweb/prometeus ?

    working on something like that :)

  • jcalebjcaleb Member
    edited August 2012

    I think there is a board already

  • prometeusprometeus Member, Host Rep

    @jcaleb said: I think there is a board already

    yes, the support board is a work in progress for now :)

  • Hm.. maybe any idea for me to buy a domain for Mr. Salvatore to run the forum? :D

  • You can trace 149.154.157.1 as well, same rack but our space

  • SpiritSpirit Member
    edited August 2012

    @William said: You can trace 149.154.157.1 as well, same rack but our space

    You use different providers as it's seen :)

    Pinging 149.154.157.1 with 32 bytes of data:
    
    Reply from 149.154.157.1: bytes=32 time=62ms TTL=51
    Reply from 149.154.157.1: bytes=32 time=65ms TTL=51
    Reply from 149.154.157.1: bytes=32 time=66ms TTL=51
    Reply from 149.154.157.1: bytes=32 time=71ms TTL=51
    
    Ping statistics for 149.154.157.1:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 62ms, Maximum = 71ms, Average = 66ms
    Tracing route to gw.it.milano.edis.at [149.154.157.1]
    over a maximum of 30 hops:
    ...
      6    10 ms     9 ms     7 ms  c28-1.itt.lju.si.as39912.net [91.220.194.116]
      7    16 ms    17 ms    17 ms  c76-1.ix1.vie.at.as39912.net [95.143.85.113]
      8    45 ms    44 ms    42 ms  c76-3.ix2.vie.at.as39912.net [95.143.89.68]
      9    39 ms    37 ms    39 ms  c76-1.eq1.zur.ch.as39912.net [81.94.48.210]
     10    41 ms    41 ms    42 ms  c72-1.mix.mil.it.as39912.net [95.143.82.242]
     11     *        *        *     Request timed out.
     12    62 ms    63 ms    63 ms  gw.it.milano.edis.at [149.154.157.1]
    
    Trace complete.

    @prometeus said: this is unexplicable as the nodes use all IP announced under our own AS

    Yeah? :)

    Node    pm12
    Pinging 194.14.179.xxx with 32 bytes of data:
    
    Reply from 194.14.179.xxx: bytes=32 time=67ms TTL=52
    Reply from 194.14.179.xxx: bytes=32 time=78ms TTL=52
    Reply from 194.14.179.xxx: bytes=32 time=67ms TTL=52
    Reply from 194.14.179.xxx: bytes=32 time=69ms TTL=52
    
    Ping statistics for 194.14.179.xxx:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 67ms, Maximum = 78ms, Average = 70ms
    
    
    Node    pm22
    Pinging 192.71.245.xxx with 32 bytes of data:
    
    Reply from 192.71.245.xxx: bytes=32 time=49ms TTL=51
    Reply from 192.71.245.xxx: bytes=32 time=48ms TTL=51
    Reply from 192.71.245.xxx: bytes=32 time=49ms TTL=51
    Reply from 192.71.245.xxx: bytes=32 time=49ms TTL=51
    
    Ping statistics for 192.71.245.xxx:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 48ms, Maximum = 49ms, Average = 48ms

    It's not issue for me - just informational post.
    (IPs are partially masked for public not prometeus)

  • @Spirit said: Tracing route to gw.it.milano.edis.at [149.154.157.1] over a maximum of 30 hops: ... 6 10 ms 9 ms 7 ms c28-1.itt.lju.si.as39912.net [91.220.194.116] 7 16 ms 17 ms 17 ms c76-1.ix1.vie.at.as39912.net [95.143.85.113] 8 45 ms 44 ms 42 ms c76-3.ix2.vie.at.as39912.net [95.143.89.68] 9 39 ms 37 ms 39 ms c76-1.eq1.zur.ch.as39912.net [81.94.48.210] 10 41 ms 41 ms 42 ms c72-1.mix.mil.it.as39912.net [95.143.82.242] 11 * * * Request timed out. 12 62 ms 63 ms 63 ms gw.it.milano.edis.at [149.154.157.1] Trace complete.

    Wut?
    This should not happen.
    Can you open it.edis.at?

  • SpiritSpirit Member
    edited August 2012

    @William said: Can you open it.edis.at?

    Yes, but what's the issue apart from different routing? :)

    EDIS Looking Glass (Milano, Italy)

    Files: 10 MB (10240 KB) 100 MB (10240 KB)
    Test-IPv4: 149.154.157.1
    Test-IPv6: 2001:b60:1000::1

  • @Spirit said: Yes, but what's the issue apart from different routing? :)

    I3B routing - Should not happen (unless this trace originates from our Austrian location)

Sign In or Register to comment.