Our ISP is KT. (Korea Telecom)

we are having the same issue....

This is traceroute to Railway node. Please fix quickly.

traceroute to (35.213.168.149), 64 hops max, 52 byte packets

 1  172.30.1.254 (172.30.1.254)  5.325 ms  1.866 ms  1.799 ms

 2  * * *

 3  112.188.47.69 (112.188.47.69)  5.722 ms  3.937 ms  3.241 ms

 4  112.188.44.73 (112.188.44.73)  5.361 ms

    112.188.32.97 (112.188.32.97)  4.308 ms

    112.188.44.237 (112.188.44.237)  4.683 ms

 5  112.174.49.77 (112.174.49.77)  9.225 ms

    112.174.47.213 (112.174.47.213)  10.176 ms

    112.174.49.81 (112.174.49.81)  17.159 ms

 6  112.174.91.182 (112.174.91.182)  15.347 ms

    112.174.91.138 (112.174.91.138)  8.758 ms

    112.174.91.118 (112.174.91.118)  9.417 ms

 7  112.174.89.254 (112.174.89.254)  130.349 ms

    112.174.87.98 (112.174.87.98)  136.086 ms

    112.174.89.254 (112.174.89.254)  130.791 ms

 8  palo-b24-link.ip.twelve99.net (213.155.141.168)  128.157 ms  128.617 ms  134.809 ms

 9  sjo-b23-link.ip.twelve99.net (62.115.115.217)  152.929 ms  129.857 ms  132.332 ms

10  cablewireless-ic-382397.ip.twelve99-cust.net (62.115.46.249)  152.196 ms  139.897 ms  129.885 ms

11  ae13-xcr1.mry.cw.net (195.2.8.49)  232.963 ms  233.519 ms  233.846 ms

12  * * *

13  * * *

14  * * *

15  * * *

16  * * *

17  * * *

18  * * *

19  * * *

20  * * *

21  * * *

22  *

Hello all,

We are seeing the same from our side too, looking into it as we speak, deeply sorry for the inconvenience.

Will keep you updated as we go.

Update here, we have applied a fix and are seeing recovery of the affected region.

what happend?

We don't know at this time, we will continue to look into it.

Make sure to share it after you figure out the issue.

Of course!

is fixed? our web site doesnt work.

we meet the same issue from HK node

Sorry It's not fixed just yet, we are still investigating on our side.

Hope fix can be ASAP. Thanks!

Update, we are tracing down the issue, it seems to be with an upstream vendor outside of our Asia proxy network. We are still investigating. We will be sure to let you all know as updates arise.

The sites are online now. want to know what happened and fixed completely.

I attached another successful traceroute here for your investigation.

traceroute to (35.213.168.149), 64 hops max, 52 byte packets

 1  172.30.1.254 (172.30.1.254)  28.826 ms  16.225 ms  1.636 ms

 2  * * *

 3  112.188.47.69 (112.188.47.69)  6.028 ms  3.745 ms  4.608 ms

 4  112.188.44.129 (112.188.44.129)  4.584 ms

    112.188.44.205 (112.188.44.205)  4.697 ms

    112.188.32.89 (112.188.32.89)  14.061 ms

 5  112.174.49.81 (112.174.49.81)  11.141 ms

    112.174.47.77 (112.174.47.77)  11.567 ms  24.678 ms

 6  112.174.91.166 (112.174.91.166)  10.032 ms

    112.174.91.230 (112.174.91.230)  11.034 ms

    112.174.86.150 (112.174.86.150)  12.036 ms

 7  112.174.89.254 (112.174.89.254)  132.574 ms

    112.174.87.2 (112.174.87.2)  131.020 ms  129.419 ms

 8  palo-b24-link.ip.twelve99.net (213.155.141.168)  132.317 ms  135.271 ms  152.600 ms

 9  sjo-b23-link.ip.twelve99.net (62.115.115.217)  138.540 ms  130.939 ms  156.270 ms

10  cablewireless-ic-382397.ip.twelve99-cust.net (62.115.46.249)  189.580 ms  191.802 ms  190.282 ms

11  ae13-xcr1.mry.cw.net (195.2.8.49)  212.654 ms  195.880 ms  199.237 ms

12  ae8-xcr2.sgs.cw.net (195.2.28.66)  189.920 ms  189.013 ms  190.608 ms

13  googlecabjpn-gw.sg.cw.net (195.89.113.194)  192.049 ms  187.403 ms  186.257 ms

14  149.168.213.35.bc.googleusercontent.com (35.213.168.149)  185.010 ms  207.110 ms  184.699 msi

We are continuing to look into it, you can follow this incident for up to date reports -

https://status.railway.com/cm6a5qh51005n4xq5raoex05q

Hey all, are you still seeing this issue? we have seen recovery once again on our side.

Hi folks, sorry for the inconvenience again, we're digging in here — could you please let us know if you're seeing any improvements?

We are okay now. but is there any hotline to report an incident like this?

Like this, a Slack Connect channel (in the Pro workspace settings page), or directly to us via a thread.