Howdy, Stranger!

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


Shells Virtual Desktop
BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
InterServer VPS
BMail.ag - Secure Email Service
Best VPN
High-Performance Bare Metal Server Solutions
Karvl.com
Server Mania Cloud Hosting
DataWagon Hosting
AlphaVPS Hosting
Evoxt.com
Clouvider
VPS Hosting with NVMe
Residential IPs in the US & 4G Mobile Proxies in EU & US with Unlimited Bandwidth
ReliableSite White-Label Dedicated Hosting for Resellers
Rabisu - Hosting Solutions
Shells Virtual Desktop
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.

47% OFF 10 Gbps VPS in New Zealand + 20% OFF Dedicated Servers in Germany!

13»

Comments

  • @ehhthing said:
    At this point you might as well just host in Singapore or Los Angeles instead, if everything is going to be routed through there...

    I think single homed Cogent is possibly the worst options out of all the T1...

    Admittedly I think this problem is not hard to solve, just need to get some IX ports, but trying to launch this product even if its a beta without those is laughable.

    Vetta seems fine but Vetta have a very open peer policy.

    1. bng1-chc2.vetta.net 0.0% 32 1.8 2.0 1.3 2.4 0.2
      1. core1-chc2.vetta.net 0.0% 32 2.1 2.1 1.2 2.4 0.2
      2. core1-akl1.vetta.net 0.0% 32 15.0 14.8 14.3 15.1 0.2
      3. core1-akl2.vetta.net 0.0% 32 14.9 14.8 14.2 15.1 0.2
      4. edge2-akl2.vetta.net 0.0% 32 14.7 14.9 14.3 15.3 0.2
      5. (waiting for reply)
      6. 45.15.140.1 0.0% 31 23.2 21.0 15.8 55.3 6.9

    Wish I knew what One was like but I would imagine it's either fucked or fine.

  • @MaxTakeba said:
    To be fair... Spark hates peering with anyone in NZ.

    Even Hurricane Electric is "only" going to Sydney and back with Spark...

    @MaxTakeba said:
    Wish I knew what One was like but I would imagine it's either fucked or fine.

    Also fucked:

    traceroute to 45.15.140.1 (45.15.140.1), 30 hops max, 60 byte packets
     1  _gateway (10.1.1.1)  0.290 ms  0.260 ms  0.318 ms
     2  10.5.1.1 (10.5.1.1)  5.741 ms  5.734 ms  5.655 ms
     3  * * *
     4  lo151.bgnzftc02.akl.vf.net.nz (203.109.180.133)  13.678 ms  9.675 ms  13.692 ms
     5  10.200.12.148 (10.200.12.148)  169.618 ms 10.200.12.150 (10.200.12.150)  157.706 ms  169.578 ms
     6  lo151.bguspmk02.sjc.vf.net.nz (203.109.180.132)  153.615 ms  157.000 ms  157.043 ms
     7  38.142.8.89 (38.142.8.89)  156.999 ms  155.919 ms  155.386 ms
     8  be3528.ccr21.sjc01.atlas.cogentco.com (154.54.94.49)  155.417 ms  156.000 ms  155.904 ms
     9  be3142.ccr41.sjc03.atlas.cogentco.com (154.54.1.194)  155.901 ms be3144.ccr41.sjc03.atlas.cogentco.com (154.54.5.102)  157.014 ms be3142.ccr41.sjc03.atlas.cogentco.com (154.54.1.194)  156.991 ms
    10  be3670.ccr22.sfo01.atlas.cogentco.com (154.54.43.13)  161.017 ms be3669.ccr21.sfo01.atlas.cogentco.com (154.54.43.9)  159.872 ms be3670.ccr22.sfo01.atlas.cogentco.com (154.54.43.13)  159.875 ms
    11  be5716.ccr21.pdx01.atlas.cogentco.com (154.54.87.118)  171.856 ms be5386.ccr21.pdx01.atlas.cogentco.com (154.54.43.158)  171.836 ms  171.825 ms
    12  be2216.ccr51.pdx02.atlas.cogentco.com (154.54.31.158)  168.032 ms  168.039 ms  168.042 ms
    13  be5436.ccr71.akl01.atlas.cogentco.com (154.54.162.46)  299.748 ms  298.726 ms  298.712 ms
    14  be5434.agr61.akl01.atlas.cogentco.com (154.54.44.173)  298.563 ms  298.342 ms  299.318 ms
    15  be2194.rcr61.b073288-1.akl01.atlas.cogentco.com (154.54.88.214)  299.304 ms  299.482 ms  299.578 ms
    16  45.15.140.1 (45.15.140.1)  299.535 ms  303.220 ms  303.264 ms
    
  • beanman109beanman109 Member, Host Rep, Megathread Squad

    Thanked by 1Blembim
  • @Peppery9 said:

    @MaxTakeba said:
    To be fair... Spark hates peering with anyone in NZ.

    Even Hurricane Electric is "only" going to Sydney and back with Spark...

    @MaxTakeba said:
    Wish I knew what One was like but I would imagine it's either fucked or fine.

    Also fucked:

    traceroute to 45.15.140.1 (45.15.140.1), 30 hops max, 60 byte packets
     1  _gateway (10.1.1.1)  0.290 ms  0.260 ms  0.318 ms
     2  10.5.1.1 (10.5.1.1)  5.741 ms  5.734 ms  5.655 ms
     3  * * *
     4  lo151.bgnzftc02.akl.vf.net.nz (203.109.180.133)  13.678 ms  9.675 ms  13.692 ms
     5  10.200.12.148 (10.200.12.148)  169.618 ms 10.200.12.150 (10.200.12.150)  157.706 ms  169.578 ms
     6  lo151.bguspmk02.sjc.vf.net.nz (203.109.180.132)  153.615 ms  157.000 ms  157.043 ms
     7  38.142.8.89 (38.142.8.89)  156.999 ms  155.919 ms  155.386 ms
     8  be3528.ccr21.sjc01.atlas.cogentco.com (154.54.94.49)  155.417 ms  156.000 ms  155.904 ms
     9  be3142.ccr41.sjc03.atlas.cogentco.com (154.54.1.194)  155.901 ms be3144.ccr41.sjc03.atlas.cogentco.com (154.54.5.102)  157.014 ms be3142.ccr41.sjc03.atlas.cogentco.com (154.54.1.194)  156.991 ms
    10  be3670.ccr22.sfo01.atlas.cogentco.com (154.54.43.13)  161.017 ms be3669.ccr21.sfo01.atlas.cogentco.com (154.54.43.9)  159.872 ms be3670.ccr22.sfo01.atlas.cogentco.com (154.54.43.13)  159.875 ms
    11  be5716.ccr21.pdx01.atlas.cogentco.com (154.54.87.118)  171.856 ms be5386.ccr21.pdx01.atlas.cogentco.com (154.54.43.158)  171.836 ms  171.825 ms
    12  be2216.ccr51.pdx02.atlas.cogentco.com (154.54.31.158)  168.032 ms  168.039 ms  168.042 ms
    13  be5436.ccr71.akl01.atlas.cogentco.com (154.54.162.46)  299.748 ms  298.726 ms  298.712 ms
    14  be5434.agr61.akl01.atlas.cogentco.com (154.54.44.173)  298.563 ms  298.342 ms  299.318 ms
    15  be2194.rcr61.b073288-1.akl01.atlas.cogentco.com (154.54.88.214)  299.304 ms  299.482 ms  299.578 ms
    16  45.15.140.1 (45.15.140.1)  299.535 ms  303.220 ms  303.264 ms
    

    Disastrous...

  • from ZappieHost NewZealand

    HOST: z472                                                     Loss%   Snt   Last   Avg  Best  Wrst StDev
      1. AS61138  xxx-xxx-xx-x.rdns.zappie.host                     0.0%    10    0.2   0.2   0.2   0.3   0.0
      2. AS55850  ip-116-251-187-224.as55850.net                    0.0%    10    0.8   0.8   0.6   1.0   0.1
      3. AS55850  et-0-2-1.atc-p-4.as55850.net                      0.0%    10  132.0 131.9 131.5 132.1   0.2
      4. AS1299   mercurynz-ic-388837.ip.twelve99-cust.net          0.0%    10  131.5 132.9 131.2 147.2   5.0
      5. AS1299   sjo-b23-link.ip.twelve99.net                      0.0%    10  132.0 131.8 131.6 132.0   0.1
      6. AS1299   sjo-bb1-link.ip.twelve99.net                     30.0%    10  134.1 134.6 132.1 136.9   1.5
      7. AS1299   palo-b24-link.ip.twelve99.net                     0.0%    10  133.6 133.6 133.5 133.8   0.1
      8. AS???    ???                                              100.0    10    0.0   0.0   0.0   0.0   0.0
      9. AS174    be2379.ccr21.sfo01.atlas.cogentco.com             0.0%    10  134.1 134.2 134.0 134.8   0.3
     10. AS174    be5386.ccr21.pdx01.atlas.cogentco.com             0.0%    10  142.0 142.0 141.9 142.2   0.1
     11. AS174    be2216.ccr51.pdx02.atlas.cogentco.com             0.0%    10  142.2 142.1 141.9 142.3   0.1
     12. AS174    be5436.ccr71.akl01.atlas.cogentco.com             0.0%    10  269.1 269.3 269.1 270.0   0.3
     13. AS174    be5434.agr61.akl01.atlas.cogentco.com             0.0%    10  269.1 269.7 269.0 274.7   1.8
     14. AS174    be2194.rcr61.b073288-1.akl01.atlas.cogentco.com   0.0%    10  269.6 269.5 269.3 269.7   0.1
     15. AS44477  45.15.140.1
    
  • edited April 2025

    Are you DMCA ignored in any locations?
    What is your Fair Usage Policy for the 10G?

  • GulfGulf Member

    do you open 25 port by request?

  • Ok, you're heard. NZ-IX is on the way - seems most of "around the world" mtrs should be fixed . After location we'll be live we'll analyze traffic and will connect another IXs if this will be necessary.

    @Gulf said:
    do you open 25 port by request?

    Yep, KYC procedure will be engaged.

    Thanked by 1Peppery9
  • MumblyMumbly Member
    edited April 2025

    @zGato said: But you don't comment anything about Austria?

    95.164.9.5 is not located in Vienna. I am getting 25ms instead of standard 6 - 9ms from my home. I checked also from my Vienna HH and Netcup VPSes. Around 12ms.

    My guess is that they made fake "Vienna" from Frankfurt, the same as just.hosting before.

  • zGatozGato Member

    @Mumbly said:

    @zGato said: But you don't comment anything about Austria?

    95.164.9.5 is not located in Vienna. I am getting 25ms instead of standard 6 - 9ms from my home. I checked also from my Vienna HH and Netcup VPSes. Around 12ms.

    My guess is that they made fake "Vienna" from Frankfurt, the same as just.hosting before.

    :)

    justhosting upstream their "Vienna" location to pq, so yeah

    Thanked by 1Mumbly
  • That's not cool.
    For distant international clients, either Germany or Austria, etc., it probably doesn't make much of a difference, but if you live closer to Vienna, it does.
    There are also plenty of good German hosting offers, and people have plenty to choose from. But for Vienna... people will choose it because they actually prefer Vienna over just another German hosted offer.

    Thanked by 1zGato
  • zGatozGato Member

    @Mumbly said:
    That's not cool.
    For distant international clients, either Germany or Austria, etc., it probably doesn't make much of a difference, but if you live closer to Vienna, it does.
    There are also plenty of good German hosting offers, and people have plenty to choose from. But for Vienna... people will choose it because they actually prefer Vienna over just another German hosted offer.

    But @pqhosting doesn't want to comment on this like he did so fast with Liechtenstein ;)

  • netsujitnetsujit Member
    edited April 2025

    @pq_hosting said:
    Ok, you're heard. NZ-IX is on the way - seems most of "around the world" mtrs should be fixed . After location we'll be live we'll analyze traffic and will connect another IXs if this will be necessary.

    Would you refund if after the location goes live and with your new IX users are still getting the 'around the world' trip?
    Or let's say you fixed the routing now but after few months you decide to change the IX again and routing gets effed up, can we cancel the service for a refund?

  • 0ka0ka Member

    perfect quality... yeah, i remember when the server i ordered worked for 2 minutes, then the network dropped for 1 minute, then it worked for 2 minutes again and then dropped again... and it worked like this for the whole month, i couldn't do anything and support had no clue about this, absolutely incompetent and they just wanted to waste my time asking for useless MTR screenshots

  • pq_hostingpq_hosting Barred
    edited April 2025

    @netsujit said:
    Would you refund if after the location goes live and with your new IX users are still getting the 'around the world' trip?
    Or let's say you fixed the routing now but after few months you decide to change the IX again and routing gets effed up, can we cancel the service for a refund?

    When location goes live it's up to customer to decide if he is fine with internet connection since LG will be live too. For this reason no refund will be issued.
    IX will not be disconnected since it's pretty cheap, we're discussing only if there is any need to add some more (as far as I know, there are 6 IXs in NZ).

    @zGato said:

    @Mumbly said:
    That's not cool.
    For distant international clients, either Germany or Austria, etc., it probably doesn't make much of a difference, but if you live closer to Vienna, it does.
    There are also plenty of good German hosting offers, and people have plenty to choose from. But for Vienna... people will choose it because they actually prefer Vienna over just another German hosted offer.

    But @pqhosting doesn't want to comment on this like he did so fast with Liechtenstein ;)

    We need some time to check everything. Your proofs looks reasonable, I will not argue with them or try find illogical explanations.

    @0ka said:
    perfect quality... yeah, i remember when the server i ordered worked for 2 minutes, then the network dropped for 1 minute, then it worked for 2 minutes again and then dropped again... and it worked like this for the whole month, i couldn't do anything and support had no clue about this, absolutely incompetent and they just wanted to waste my time asking for useless MTR screenshots

    That's your vision on the situation. However, we can't know where internet is broken, so we're asking all necessary information to investigate the issue. That's pretty normal.

    Thanked by 2zGato fluffernutter
  • 0ka0ka Member

    @pq_hosting said: However, we can't know where internet is broken, so we're asking all necessary information to investigate the issue. That's pretty normal

    your gateway was down for 90% of the time for the whole month, everything was clear from the beginning.

    Thanked by 1tumble
  • netsujitnetsujit Member
    edited April 2025

    @pq_hosting said:

    @netsujit said:
    Would you refund if after the location goes live and with your new IX users are still getting the 'around the world' trip?
    Or let's say you fixed the routing now but after few months you decide to change the IX again and routing gets effed up, can we cancel the service for a refund?

    When location goes live it's up to customer to decide if he is fine with internet connection since LG will be live too. For this reason no refund will be issued.

    I am talking about this presale.
    While the NZ location and LG aren't yet live, the presale ordering is live and active. If someone orders now, they are essentially receiving a VPS with a claim that "NZ-IX is on the way."
    Once the NZ location goes live, if the new IX doesn't resolve the routing issues, can users who placed presale orders request a refund?
    Put simply, if the promises/claims made during the presale are not met, can these orders be cancelled and refunded? Hopefully I've worded by question in a better way now.

  • GulfGulf Member

    @pq_hosting said:
    Yep, KYC procedure will be engaged.

    What documents do you require?

  • @0ka said:

    @pq_hosting said: However, we can't know where internet is broken, so we're asking all necessary information to investigate the issue. That's pretty normal

    your gateway was down for 90% of the time for the whole month, everything was clear from the beginning.

    That can't be. Sorry, but without any traceroutes and further diagnostics we can't agree with this.

    @netsujit said:
    I am talking about this presale.
    While the NZ location and LG aren't yet live, the presale ordering is live and active. If someone orders now, they are essentially receiving a VPS with a claim that "NZ-IX is on the way."
    Once the NZ location goes live, if the new IX doesn't resolve the routing issues, can users who placed presale orders request a refund?
    Put simply, if the promises/claims made during the presale are not met, can these orders be cancelled and refunded? Hopefully I've worded by question in a better way now.

    I can't see any promises we made. Yes, right now we're connecting NZ-IX (agreement was accepted, cross-connect was ordered), however, as far as you know, it's Easter hoilday in many parts of the world so it will take some time.
    What about refund. I don't want to be dodgy here. No, no refund will be given. We provided all necessary information, we do not conceal the fact we're using cogent in NZ.
    Test IP was given, mtrs were provided by other members of LET. Customer is always welcome to ask support team to provide traceroute to any IP from any our location.

    @Gulf said:

    @pq_hosting said:
    Yep, KYC procedure will be engaged.

    What documents do you require?

    National passport or ID card. KYC procedure is being made by well-known 3rd party service withpersona.com (we don't store any scans or photos of customer ids/passports).

  • It took some time because of holidays, then we faced the issue with cross-connect ... But for now - NZ-IX is live.

    @NHNHNH000 said:
    from ZappieHost NewZealand

    HOST: z472                                                     Loss%   Snt   Last   Avg  Best  Wrst StDev
      1. AS61138  xxx-xxx-xx-x.rdns.zappie.host                     0.0%    10    0.2   0.2   0.2   0.3   0.0
      2. AS55850  ip-116-251-187-224.as55850.net                    0.0%    10    0.8   0.8   0.6   1.0   0.1
      3. AS55850  et-0-2-1.atc-p-4.as55850.net                      0.0%    10  132.0 131.9 131.5 132.1   0.2
      4. AS1299   mercurynz-ic-388837.ip.twelve99-cust.net          0.0%    10  131.5 132.9 131.2 147.2   5.0
      5. AS1299   sjo-b23-link.ip.twelve99.net                      0.0%    10  132.0 131.8 131.6 132.0   0.1
      6. AS1299   sjo-bb1-link.ip.twelve99.net                     30.0%    10  134.1 134.6 132.1 136.9   1.5
      7. AS1299   palo-b24-link.ip.twelve99.net                     0.0%    10  133.6 133.6 133.5 133.8   0.1
      8. AS???    ???                                              100.0    10    0.0   0.0   0.0   0.0   0.0
      9. AS174    be2379.ccr21.sfo01.atlas.cogentco.com             0.0%    10  134.1 134.2 134.0 134.8   0.3
     10. AS174    be5386.ccr21.pdx01.atlas.cogentco.com             0.0%    10  142.0 142.0 141.9 142.2   0.1
     11. AS174    be2216.ccr51.pdx02.atlas.cogentco.com             0.0%    10  142.2 142.1 141.9 142.3   0.1
     12. AS174    be5436.ccr71.akl01.atlas.cogentco.com             0.0%    10  269.1 269.3 269.1 270.0   0.3
     13. AS174    be5434.agr61.akl01.atlas.cogentco.com             0.0%    10  269.1 269.7 269.0 274.7   1.8
     14. AS174    be2194.rcr61.b073288-1.akl01.atlas.cogentco.com   0.0%    10  269.6 269.5 269.3 269.7   0.1
     15. AS44477  45.15.140.1
    

    Should be fixed.

    @Peppery9 said:

    Also fucked:

    traceroute to 45.15.140.1 (45.15.140.1), 30 hops max, 60 byte packets
     1  _gateway (10.1.1.1)  0.290 ms  0.260 ms  0.318 ms
     2  10.5.1.1 (10.5.1.1)  5.741 ms  5.734 ms  5.655 ms
     3  * * *
     4  lo151.bgnzftc02.akl.vf.net.nz (203.109.180.133)  13.678 ms  9.675 ms  13.692 ms
     5  10.200.12.148 (10.200.12.148)  169.618 ms 10.200.12.150 (10.200.12.150)  157.706 ms  169.578 ms
     6  lo151.bguspmk02.sjc.vf.net.nz (203.109.180.132)  153.615 ms  157.000 ms  157.043 ms
     7  38.142.8.89 (38.142.8.89)  156.999 ms  155.919 ms  155.386 ms
     8  be3528.ccr21.sjc01.atlas.cogentco.com (154.54.94.49)  155.417 ms  156.000 ms  155.904 ms
     9  be3142.ccr41.sjc03.atlas.cogentco.com (154.54.1.194)  155.901 ms be3144.ccr41.sjc03.atlas.cogentco.com (154.54.5.102)  157.014 ms be3142.ccr41.sjc03.atlas.cogentco.com (154.54.1.194)  156.991 ms
    10  be3670.ccr22.sfo01.atlas.cogentco.com (154.54.43.13)  161.017 ms be3669.ccr21.sfo01.atlas.cogentco.com (154.54.43.9)  159.872 ms be3670.ccr22.sfo01.atlas.cogentco.com (154.54.43.13)  159.875 ms
    11  be5716.ccr21.pdx01.atlas.cogentco.com (154.54.87.118)  171.856 ms be5386.ccr21.pdx01.atlas.cogentco.com (154.54.43.158)  171.836 ms  171.825 ms
    12  be2216.ccr51.pdx02.atlas.cogentco.com (154.54.31.158)  168.032 ms  168.039 ms  168.042 ms
    13  be5436.ccr71.akl01.atlas.cogentco.com (154.54.162.46)  299.748 ms  298.726 ms  298.712 ms
    14  be5434.agr61.akl01.atlas.cogentco.com (154.54.44.173)  298.563 ms  298.342 ms  299.318 ms
    15  be2194.rcr61.b073288-1.akl01.atlas.cogentco.com (154.54.88.214)  299.304 ms  299.482 ms  299.578 ms
    16  45.15.140.1 (45.15.140.1)  299.535 ms  303.220 ms  303.264 ms
    

    That's too.

    Seems you sent too much mtrs, so please, check if connection to NZ-IX fixed the issue.

  • PQ.Hosting is now on IX.NZ — faster and closer to your users

    Our team is always moving forward. Based on your feedback, we continuously refine what matters most. That’s why we’re expanding our infrastructure in the most stable and strategically important regions around the world.

    PQ.Hosting has joined the New Zealand Internet Exchange (NZIX) — the national internet exchange point in New Zealand.

    Why does this matter to you?

    NZIX is an independent, non-profit organization that brings together major local and international internet providers.

    Our direct connection to NZIX provides tangible benefits:

    ✅ Lower latency. Direct peering minimizes the distance between your users and our servers;
    ✅ 9 exchange points across the country ensure wide coverage and strong availability;
    ✅ No intermediaries. We’re connected directly, so your services are closer to your users.

    This is great news for clients in Oceania, Australia, Japan, and Southeast Asia — faster, more stable, and more predictable connections are now within reach.

    If you’ve been looking for a reliable entry point to the region — this is it. Check out our plans and deploy your VPS in New Zealand today.

Sign In or Register to comment.