Howdy, Stranger!

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

Sign In Register

Quick Links


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

Categories

In this Discussion

Home โ€บ Offers
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.

[Clearance Sale] NAT VPS at COST | New locations France & Germany | 5 x 256MB NAT VPS Bundle @ $15!!

1…68101112

Comments

  • SmilenceSmilence Member

    https://status.natvps.net/
    The status page shows HKG3 v6 is back and online.

    Still waiting for my hkg1-hkg node back and online.....Currently, it's totally offline. ..May someone be working on it?

    BTW, there is NOT hkg1-hkg node on status page, why?

  • AbdAbd Member, Patron Provider

    @Smilence said:
    https://status.natvps.net/
    The status page shows HKG3 v6 is back and online.

    Still waiting for my hkg1-hkg node back and online.....Currently, it's totally offline. ..May someone be working on it?

    BTW, there is NOT hkg1-hkg node on status page, why?

    We sent an email notification regarding this yesterday. Awaiting upstream response.

  • yoursunnyyoursunny Member, IPv6 Advocate

    hkg3-hkg is coming back.
    Network was very slow 4 hours ago, but it's better now after MJJs went to bed.

    waw1-pol and nyc1-usa are showing as red in Virtualizor.
    The containers are still functional, but it's not possible to reboot or otherwise control them.

  • borowskyborowsky Member

    My nat vps in Switzerland is still not connectable since already over two weeks
    Now even control panel doesnt load up
    I asked in ticked for "Any progress or estimated time it can take to fix issues?" got no reply...

  • AbdAbd Member, Patron Provider
    edited September 2022

    @borowsky said:
    My nat vps in Switzerland is still not connectable since already over two weeks
    Now even control panel doesnt load up
    I asked in ticked for "Any progress or estimated time it can take to fix issues?" got no reply...

    That is because we are sending updates over email to all clients affected at HKG & ZRH.
    Switzerland is online already. kindly check now. :)

  • borowskyborowsky Member

    @Abd said:

    @borowsky said:
    My nat vps in Switzerland is still not connectable since already over two weeks
    Now even control panel doesnt load up
    I asked in ticked for "Any progress or estimated time it can take to fix issues?" got no reply...

    That is because we are sending updates over email to all clients affected at HKG & ZRH.
    Switzerland is online already. kindly check now. :) ![]

    Fair enough, I got this single email on Wednesday
    You could mention that nat ports has changed too... (personally I dont care about IPV6 on this service)

    All data is gone but at least vps is back up since - it says 5hours

  • SmilenceSmilence Member

    @borowsky said:

    @Abd said:

    @borowsky said:
    My nat vps in Switzerland is still not connectable since already over two weeks
    Now even control panel doesnt load up
    I asked in ticked for "Any progress or estimated time it can take to fix issues?" got no reply...

    That is because we are sending updates over email to all clients affected at HKG & ZRH.
    Switzerland is online already. kindly check now. :) ![]

    Fair enough, I got this single email on Wednesday
    You could mention that nat ports has changed too... (personally I dont care about IPV6 on this service)

    All data is gone but at least vps is back up since - it says 5hours

    Any update for HKG node? Will totally re-create all VMs too?

  • saywhat13saywhat13 Member
    edited September 2022

    @Smilence said:

    @borowsky said:

    @Abd said:

    @borowsky said:
    My nat vps in Switzerland is still not connectable since already over two weeks
    Now even control panel doesnt load up
    I asked in ticked for "Any progress or estimated time it can take to fix issues?" got no reply...

    That is because we are sending updates over email to all clients affected at HKG & ZRH.
    Switzerland is online already. kindly check now. :) ![]

    Fair enough, I got this single email on Wednesday
    You could mention that nat ports has changed too... (personally I dont care about IPV6 on this service)

    All data is gone but at least vps is back up since - it says 5hours

    Any update for HKG node? Will totally re-create all VMs too?

    +1๏ผŒ Is the maintenance of hkg1 finished? The hkg1 node's route is abnormal, with very high latency even to the CDN nodes in HK. The hkg2 instance is really slow in terms of performance although it's up right now, and the ipv4 reverse proxy is also nonfunctional.

  • cchwwwcchwww Member

    Ping time on HK1.

    PING 1.1.1.1 (1.1.1.1): 56 data bytes
    64 bytes from 1.1.1.1: icmp_seq=0 ttl=59 time=100.070 ms
    64 bytes from 1.1.1.1: icmp_seq=1 ttl=59 time=97.678 ms
    64 bytes from 1.1.1.1: icmp_seq=2 ttl=59 time=2513.924 ms
    64 bytes from 1.1.1.1: icmp_seq=3 ttl=59 time=204.866 ms
    64 bytes from 1.1.1.1: icmp_seq=4 ttl=59 time=99.867 ms
    64 bytes from 1.1.1.1: icmp_seq=5 ttl=59 time=1.499 ms
    64 bytes from 1.1.1.1: icmp_seq=6 ttl=59 time=1.336 ms
    64 bytes from 1.1.1.1: icmp_seq=7 ttl=59 time=1.092 ms
    64 bytes from 1.1.1.1: icmp_seq=8 ttl=59 time=2.472 ms
    64 bytes from 1.1.1.1: icmp_seq=9 ttl=59 time=98.052 ms
    64 bytes from 1.1.1.1: icmp_seq=10 ttl=59 time=1.232 ms
    64 bytes from 1.1.1.1: icmp_seq=11 ttl=59 time=199.802 ms
    64 bytes from 1.1.1.1: icmp_seq=12 ttl=59 time=1.987 ms
    64 bytes from 1.1.1.1: icmp_seq=13 ttl=59 time=1.421 ms
    64 bytes from 1.1.1.1: icmp_seq=14 ttl=59 time=1.198 ms
    64 bytes from 1.1.1.1: icmp_seq=15 ttl=59 time=2.100 ms
    64 bytes from 1.1.1.1: icmp_seq=16 ttl=59 time=1.990 ms

  • yoursunnyyoursunny Member, IPv6 Advocate

    @cchwww said:
    Ping time on HK1.

    Ping time in hkg3-hkg is also jumping up.
    Wait for MJJs to go to bed, and you'll see better results.

    root@hkg:~# ping -i 0.2 -c 100 2606:4700:4700::1111
PING 2606:4700:4700::1111(2606:4700:4700::1111) 56 data bytes
64 bytes from 2606:4700:4700::1111: icmp_seq=1 ttl=59 time=1.65 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=2 ttl=59 time=2.84 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=3 ttl=59 time=3.55 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=4 ttl=59 time=4.56 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=5 ttl=59 time=3.10 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=6 ttl=59 time=3.15 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=7 ttl=59 time=3.08 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=8 ttl=59 time=2.75 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=9 ttl=59 time=2.53 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=10 ttl=59 time=3.75 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=11 ttl=59 time=2.87 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=12 ttl=59 time=2.73 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=13 ttl=59 time=2.78 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=14 ttl=59 time=2.61 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=15 ttl=59 time=3.06 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=16 ttl=59 time=2.81 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=17 ttl=59 time=3.60 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=18 ttl=59 time=3.23 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=19 ttl=59 time=2.89 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=20 ttl=59 time=3.61 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=21 ttl=59 time=7.64 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=22 ttl=59 time=93.1 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=23 ttl=59 time=6.37 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=24 ttl=59 time=3.37 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=25 ttl=59 time=2.56 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=26 ttl=59 time=3.99 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=27 ttl=59 time=2.62 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=28 ttl=59 time=2.77 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=29 ttl=59 time=3.41 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=30 ttl=59 time=3.20 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=31 ttl=59 time=4.01 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=32 ttl=59 time=3.02 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=33 ttl=59 time=2.96 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=34 ttl=59 time=3.10 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=35 ttl=59 time=3.02 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=36 ttl=59 time=2.60 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=37 ttl=59 time=2.75 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=38 ttl=59 time=3.32 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=39 ttl=59 time=3.01 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=40 ttl=59 time=2.78 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=41 ttl=59 time=3.21 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=42 ttl=59 time=77.9 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=43 ttl=59 time=3.90 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=44 ttl=59 time=3.16 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=45 ttl=59 time=3.30 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=46 ttl=59 time=2.54 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=47 ttl=59 time=3.35 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=48 ttl=59 time=3.21 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=49 ttl=59 time=2.97 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=50 ttl=59 time=3.98 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=51 ttl=59 time=3.47 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=52 ttl=59 time=3.84 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=53 ttl=59 time=3.05 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=54 ttl=59 time=4.62 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=55 ttl=59 time=6.60 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=56 ttl=59 time=4.15 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=57 ttl=59 time=7.56 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=58 ttl=59 time=4.63 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=59 ttl=59 time=3.61 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=60 ttl=59 time=3.35 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=61 ttl=59 time=3.17 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=62 ttl=59 time=2.74 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=63 ttl=59 time=92.0 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=64 ttl=59 time=2.52 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=65 ttl=59 time=2.89 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=66 ttl=59 time=3.75 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=67 ttl=59 time=3.07 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=68 ttl=59 time=3.03 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=69 ttl=59 time=2.76 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=70 ttl=59 time=2.78 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=71 ttl=59 time=77.4 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=72 ttl=59 time=3.14 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=73 ttl=59 time=3.00 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=74 ttl=59 time=3.23 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=75 ttl=59 time=80.5 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=76 ttl=59 time=5.44 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=77 ttl=59 time=3.31 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=78 ttl=59 time=3.94 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=79 ttl=59 time=3.80 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=80 ttl=59 time=2.68 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=81 ttl=59 time=2.66 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=82 ttl=59 time=2.92 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=83 ttl=59 time=5.35 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=84 ttl=59 time=3.07 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=85 ttl=59 time=2.78 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=86 ttl=59 time=3.62 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=87 ttl=59 time=3.79 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=88 ttl=59 time=3.57 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=89 ttl=59 time=2.43 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=90 ttl=59 time=3.10 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=91 ttl=59 time=3.40 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=92 ttl=59 time=2.66 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=93 ttl=59 time=3.23 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=94 ttl=59 time=3.01 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=95 ttl=59 time=2.98 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=96 ttl=59 time=2.91 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=97 ttl=59 time=80.4 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=98 ttl=59 time=80.1 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=99 ttl=59 time=80.4 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=100 ttl=59 time=80.9 ms

--- 2606:4700:4700::1111 ping statistics ---
100 packets transmitted, 100 received, 0% packet loss, time 20397ms
rtt min/avg/max/mdev = 1.653/10.514/93.114/22.722 ms
  • SmilenceSmilence Member
    edited September 2022

    Again? Rebuilding OS is not successful.
    hkg1-hkg node

    Today at 2:13 pm
    Rebuilding VPS
    There was an error while reinstalling the OS
    Task could not be Completed.

  • saywhat13saywhat13 Member

    @cchwww said:
    Ping time on HK1.

    PING 1.1.1.1 (1.1.1.1): 56 data bytes
    64 bytes from 1.1.1.1: icmp_seq=0 ttl=59 time=100.070 ms
    64 bytes from 1.1.1.1: icmp_seq=1 ttl=59 time=97.678 ms
    64 bytes from 1.1.1.1: icmp_seq=2 ttl=59 time=2513.924 ms
    64 bytes from 1.1.1.1: icmp_seq=3 ttl=59 time=204.866 ms
    64 bytes from 1.1.1.1: icmp_seq=4 ttl=59 time=99.867 ms
    64 bytes from 1.1.1.1: icmp_seq=5 ttl=59 time=1.499 ms
    64 bytes from 1.1.1.1: icmp_seq=6 ttl=59 time=1.336 ms
    64 bytes from 1.1.1.1: icmp_seq=7 ttl=59 time=1.092 ms
    64 bytes from 1.1.1.1: icmp_seq=8 ttl=59 time=2.472 ms
    64 bytes from 1.1.1.1: icmp_seq=9 ttl=59 time=98.052 ms
    64 bytes from 1.1.1.1: icmp_seq=10 ttl=59 time=1.232 ms
    64 bytes from 1.1.1.1: icmp_seq=11 ttl=59 time=199.802 ms
    64 bytes from 1.1.1.1: icmp_seq=12 ttl=59 time=1.987 ms
    64 bytes from 1.1.1.1: icmp_seq=13 ttl=59 time=1.421 ms
    64 bytes from 1.1.1.1: icmp_seq=14 ttl=59 time=1.198 ms
    64 bytes from 1.1.1.1: icmp_seq=15 ttl=59 time=2.100 ms
    64 bytes from 1.1.1.1: icmp_seq=16 ttl=59 time=1.990 ms

    Dude, how's your hk1's IPV6 and reverse proxy? Is the domain forwarding functioning now? Mine is useless, plus the IPV6 is down so the VPS is basically obsoleted.

  • PhyMaaPhyMaa Member

    How hkg1-hkg progress, it has been offline for a long time, and https://status.natvps.net/ this page without hkg1 status.

  • AbdAbd Member, Patron Provider

    hkg1-hkg has some issues still , the upstream provider is working on it & has promised resolution in few hours.

  • SmilenceSmilence Member

    @Abd said:
    hkg1-hkg has some issues still , the upstream provider is working on it & has promised resolution in few hours.

    The issue fixed now? What should we do? Power Off/On VM? Currently, VM still without IPv6.

  • yemyem Member

    There was an error while creating the VPS There was an error while reinstalling the OS

  • protonproton Barred

    Hello, ticket #1301087, "17 d 3 hr 17 min Awaiting Staff Reply" >:)

    Hello, why my vps is suspended rather than limit to 10mbps, and why not reset traffic amount this month?

    This VPS is suspended due to Bandwidth Over Usage. You cannot perform any operations for the VPS !
    Your VPS was suspended on 2022-08-15 12:31:53 and it will be unsuspended on 2022-09-30 23:59:59

  • saywhat13saywhat13 Member

    buddies hkg2 ipv6 down again?

  • mrs92mrs92 Member

    Grabbed a bundle a few months ago and now some of them have been down. No email. No response to my ticket. Terrible service.
    Go with a provider tag to scam us right? F off @Abd.

    @yem said:
    There was an error while creating the VPS There was an error while reinstalling the OS

    Same here

    @proton said:
    Hello, ticket #1301087, "17 d 3 hr 17 min Awaiting Staff Reply" >:)

    Hello, why my vps is suspended rather than limit to 10mbps, and why not reset traffic amount this month?

    This VPS is suspended due to Bandwidth Over Usage. You cannot perform any operations for the VPS !
    Your VPS was suspended on 2022-08-15 12:31:53 and it will be unsuspended on 2022-09-30 23:59:59

    Ostracize him bro

    @saywhat13 said:
    buddies hkg2 ipv6 down again?

    Its all gone. See for yourself https://status.natvps.net/

  • yoursunnyyoursunny Member, IPv6 Advocate

    @mrs92 said:
    Grabbed a bundle a few months ago and now some of them have been down.

    For the ultra cheap price, you can only expect half of them to be up.

    I just tried my 5-continent bundle, SSH over IPv6:

    ๐Ÿ”ด South America - Valdivia
    ๐ŸŸข North America - New York
    ๐ŸŸข Europe - Warsaw
    ๐Ÿ”ด Asia - Hong Kong
    ๐ŸŸข Africa - Johannesburg

    Thanked by 1Ganonk
  • AbdAbd Member, Patron Provider
    edited September 2022

    @mrs92 said:
    Grabbed a bundle a few months ago and now some of them have been down. No email. No response to my ticket. Terrible service.
    Go with a provider tag to scam us right? F off @Abd.

    Mind mentioning your ticket # aswell ?

  • 3166931669 Member

    Anything in HK?

  • hmlianghmliang Member

    ticket #3999800, please. @Abd

  • yoursunnyyoursunny Member, IPv6 Advocate

    @yoursunny said:
    I just tried my 5-continent bundle, SSH over IPv6:

    ๐Ÿ”ด South America - Valdivia
    ๐ŸŸข North America - New York
    ๐ŸŸข Europe - Warsaw
    ๐Ÿ”ด Asia - Hong Kong
    ๐ŸŸข Africa - Johannesburg

    The following email arrived on Sep 30, three days after the above comment was posted.

    [Ongoing] IPv6 Issue Chile NAT VPS

    Hello push-ups specialist,

    This is to notify of an ongoing IPv6 issue on Chile NAT VPS node.
    We are working with the upstream provider & expecting a resolution soon.

    We will keep you informed once there are updates and this gets fixed.

    Kind regards,
    NatVPS.net / WebHorizon

    The good news is, all five containers are reachable via IPv6 today.

  • ratneoratneo Member

    @yoursunny said:

    @yoursunny said:
    I just tried my 5-continent bundle, SSH over IPv6:

    ๐Ÿ”ด South America - Valdivia
    ๐ŸŸข North America - New York
    ๐ŸŸข Europe - Warsaw
    ๐Ÿ”ด Asia - Hong Kong
    ๐ŸŸข Africa - Johannesburg

    The following email arrived on Sep 30, three days after the above comment was posted.

    [Ongoing] IPv6 Issue Chile NAT VPS

    Hello push-ups specialist,

    This is to notify of an ongoing IPv6 issue on Chile NAT VPS node.
    We are working with the upstream provider & expecting a resolution soon.

    We will keep you informed once there are updates and this gets fixed.

    Kind regards,
    NatVPS.net / WebHorizon

    The good news is, all five containers are reachable via IPv6 today.

    That's indeed a good news. However IPv6 address in hkg1 has been changed.

  • SmilenceSmilence Member

    [Resolved] IPv6 Issue Hong Kong NAT VPS

    Hello,

    This is to notify IPv6 issue on Hong Kong Nat VPS node hkg1-hkg is resolved.

    A new IPv6 address has been assigned. Please bind your app to this new IPv6.

    Incase of any queries, we are here to help.

    Kind regards,
    NatVPS.net / WebHorizon

    PS: IPv6/64->IPv6/80

  • SmilenceSmilence Member
    edited October 2022

    hkg1-hkg IPv6 connection lost? Or unstable again?

  • saywhat13saywhat13 Member

    Lololololol Immediately down after up for a short period..This is very webhorizonly.

  • pddpdd Member

    @Abd hkg1 Domain Forwarding is not working!

  • hmlianghmliang Member

    @Abd ticket #3999800 and #8556053, thx.

Sign In or Register to comment.