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.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
All of my servers at Online.et appear to be up with no issues in the last 24 hours.
it's just routing problem I guess, anyone in southeast asia region have same issue accessing online.net?
All is well here too (Not from Asia though).
I have the same situation like yours. I have an openvpn server on DO that uses remote mysql for authentication on my online's server. Suddenly my vpn stopped working because couldnt connect to the remote mysql server.
Online.net didnt even load for me, but after many retries, it slowly loaded.
But still my openvpn server couldnt connect to my online's server at port 3306 LOL. I couldnt find any cause because it suddenly happened at the same time website online.net had problem with no changes I did to those 2 servers.
Other port can be contacted, only port 3306 wont. Now I am scratching my head searching for the fix LOL.
Edit: and now miracally, port 3306 can be connected from other server again. But very slow connection between them.
I had some issues with mine. All seems well now though.
Working fine for me, western US. Ssh session from last night is still up.
It is happening again. I couldnt even log into ssh of all my Online servers. Couldnt connect and sometimes it stuck while connecting.
Cloudflare gave timeout error for my websites. Isup.me reported my website is up.
Same here,south east Asia.
I can access my servers with Canada vpn, but not with Singapore vpn. My local internet also couldnt reach them.
Mine's still fine, was typing on it in another window just now.
Basically it seems like their Asia-Pacific/Oceania routing is messed up, no idea when/if it'll be fixed
Open tickets with mtr when this happens,
for what I've been able to see, yesterday's issue was caused (I guess) by a major fiber cut in Ashburn area, which caused main transit providers to "reroute" however they can the traffic, but I have not received a single ticket about it so it's hard to debug without any IPs/routes to check
Yeh, i saw the drop on akl monitoring system
I am living in the South East Asia, the connection is fine.
But I cannot ping from my server (DC2) to a server of Godaddy in Arizona. There're indeed some problems.
Trace route from DC2 to 166.62.10.137 (godaddy). It seems that Singapore has some problems with their routing.
traceroute to 166.62.10.137 (166.62.10.137), 30 hops max, 60 byte packets 1 62-210-252-1.rev.poneytelecom.eu (62.210.252.1) 0.371 ms 0.461 ms 0.590 ms 2 195.154.1.140 (195.154.1.140) 0.691 ms 195.154.1.138 (195.154.1.138) 0.819 ms 195.154.1.140 (195.154.1.140) 0.775 ms 3 ix-ae-4-0.thar2.VI8-Vitry-Sur-Seine.as6453.net (5.23.25.17) 2.277 ms 2.271 ms 2.253 ms 4 if-ae-30-2.tcore1.PYE-Paris.as6453.net (5.23.25.6) 322.421 ms 322.496 ms 322.558 ms 5 if-ae-3-6.tcore1.L78-London.as6453.net (80.231.130.85) 320.367 ms * if-ae-11-2.tcore1.PYE-Paris.as6453.net (80.231.153.50) 345.693 ms 6 if-ae-3-6.tcore1.L78-London.as6453.net (80.231.130.85) 320.470 ms * 320.509 ms 7 if-ae-5-2.tcore1.N0V-New-York.as6453.net (66.198.70.82) 325.102 ms 325.051 ms * 8 if-ae-14-14.tcore2.NTO-New-York.as6453.net (66.198.111.9) 393.342 ms * * 9 * if-ae-7-2.tcore1.NTO-New-York.as6453.net (63.243.128.141) 321.962 ms if-ae-8-2.tcore1.NTO-New-York.as6453.net (63.243.128.69) 340.030 ms 10 * if-ae-12-2.tcore1.SQN-San-Jose.as6453.net (63.243.128.29) 470.584 ms 343.309 ms 11 if-ae-7-2.tcore2.SVW-Singapore.as6453.net (180.87.15.25) 333.875 ms if-ae-3-2.tcore2.LVW-Los-Angeles.as6453.net (63.243.205.14) 343.474 ms if-ae-28-2.tcore2.SVW-Singapore.as6453.net (64.86.252.33) 324.798 ms 12 if-ae-7-2.tcore2.SVW-Singapore.as6453.net (180.87.15.25) 328.283 ms if-ae-28-2.tcore2.SVW-Singapore.as6453.net (64.86.252.33) 331.668 ms ip-182-50-156-241.ip.secureserver.net (182.50.156.241) 345.042 ms 13 120.29.215.18 (120.29.215.18) 348.415 ms if-et-24-2.hcore1.KV8-Chiba.as6453.net (66.198.144.57) 248.086 ms if-ae-20-2.tcore1.SVQ-Singapore.as6453.net (180.87.96.21) 350.305 ms 14 120.29.215.18 (120.29.215.18) 349.206 ms if-et-24-2.hcore1.KV8-Chiba.as6453.net (66.198.144.57) 247.594 ms ip-182-50-156-245.ip.secureserver.net (182.50.156.245) 332.637 ms 15 if-et-1-2.hcore2.KV8-Chiba.as6453.net (120.29.211.3) 257.210 ms * * 16 if-ae-20-2.tcore1.SVQ-Singapore.as6453.net (180.87.96.21) 386.042 ms * 399.355 ms 17 * * if-ae-20-2.tcore1.SVQ-Singapore.as6453.net (180.87.96.21) 414.622 ms 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 ip-182-50-156-245.ip.secureserver.net (182.50.156.245) 327.669 ms !X * *
In my case, only Australia (NextDC) and for a brief time. Singapore and Hong Kong were not affected.
Tata confirmed their traffic is affected by a major fiber cut on their backbone in Ashburn, they are rerouting stuff but it's not as good as usual
the fiber seem to be repared so we can expect back to normal quite soon now
Use a site like this next time http://ping.pe