Transfer.sh is currently down #262

Closed
opened 2026-01-19 18:29:39 +00:00 by michael · 5 comments
Owner

Originally created by @linuxct on GitHub.

Title self explanatory. Seems to be an outage that's causing a service degradation from Spain, and Germany as far as I can tell.

Originally created by @linuxct on GitHub. Title self explanatory. Seems to be an outage that's causing a service degradation from Spain, and Germany as far as I can tell.
Author
Owner

@paolafrancesca commented on GitHub:

this repo has no connection with the http://transfer.sh hosted service and there's nothing I could do about it

@paolafrancesca commented on GitHub: this repo has no connection with the http://transfer.sh hosted service and there's nothing I could do about it
Author
Owner

@paolafrancesca commented on GitHub:

also: I've just tested and it works properly from germany

@paolafrancesca commented on GitHub: also: I've just tested and it works properly from germany
Author
Owner

@paolafrancesca commented on GitHub:

the repo is hosted on github and I'm the maintainer. I never had any control on https://transfer.sh that was maintained and hosted by dutchcoders but it is now hosted by storj with totally independence (as far as I know they don't use the service from the repo code baseline)
I've no connection with storj and I've never been in contact with them

@paolafrancesca commented on GitHub: the repo is hosted on github and I'm the maintainer. I never had any control on https://transfer.sh that was maintained and hosted by dutchcoders but it is now hosted by storj with totally independence (as far as I know they don't use the service from the repo code baseline) I've no connection with storj and I've never been in contact with them
Author
Owner

@linuxct commented on GitHub:

The repo may not be intrinsically connected to https://transfer.sh, but it's being hosted by DutchCoders, who also are the owners of the repo. Correct me if I'm wrong.

Still getting ERR_CONNECTION_TIMED_OUT from our Spain and Germany front servers. Will wait to see if we get escalated any other network issue or if it's just this specific case.

@linuxct commented on GitHub: The repo may not be intrinsically connected to https://transfer.sh, but it's being hosted by DutchCoders, who also are the owners of the repo. Correct me if I'm wrong. Still getting ERR_CONNECTION_TIMED_OUT from our Spain and Germany front servers. Will wait to see if we get escalated any other network issue or if it's just this specific case.
Author
Owner

@linuxct commented on GitHub:

Thank you, I've emailed storj to notify them.

@linuxct commented on GitHub: Thank you, I've emailed storj to notify them.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dutchcoders/transfer.sh#262