Can you provide more information here?

yep, what do you need?

seems like it resolved itself, can ignore for now

still looking ito it

newest issue shows same

@Brody we just had this issue and project id was dfca2de8-200c-4fbb-b74c-74a8a8ee1296

if you guys want to retroactively look into it later, ik you're having a lot of other service issues right now

is this resolved for you?

yeah its resolved for us

I work with him

was this a problem from railway->external or external->railway?

railway->external

based on my investigation it wasnt sending the final ack for the 3-way tcp connection

i was able to send requests, etc fine to external from my local

which service was it?

it wasnt a dns issue because from logs i saw it resolved the ip fine and even tried connecting directly to ip on our staging service

can i dm you

dont wanna share name here

or can i copy service id somehow

if you could link it to me that'd be ideal

https://railway.com/project/dfca2de8-200c-4fbb-b74c-74a8a8ee1296/service/90280ea3-d23d-47c3-9e6d-09acdfd82f26?environmentId=6170f5e3-1bf9-4a90-bd7e-7854a1460f5c

Do you know which service/domain/IP you were trying to reach?

yep

is there a more private way for us to share

internal service domain

can also check logs its obvious there

17:45 utc issue resolved

started around 16:45 utc

@Phineas is there an update on this? we want to figure out if its a railway issue, multiple users saying same points to it, but no official response from Railway

kind of a big deal to have external requests failing for an hr

Hello, I've done some digging and all of the reports (including yours) were an issue between us and the OVH network specifically. From our perspective, it looks like they had a small network outage at that time.

also related: https://discord.com/channels/713503345364697088/1468302298626134248 and yeah that external API was using OVH.