forum

[Archived] osu beatmap downloads not working

posted
Total Posts
4
Topic Starter
catron44
Problem Details:

This problem is a little complicated for me. Just since a few hours ago, when I try to download a beatmap from the website, nothing happens. At the bottom left of my chrome I get ""Waiting for bm4.ppy.sh..." and there is a loading symbol on the tab.
This problem is mirrored in game while using osu!direct. When I try to download any beat map, it just goes straight to "0%" and hangs there for a long time before closing without the downloading completing.

My internet is working completely fine as far as I can tell. I can download from elsewhere with no problem. I have tried deleting cookies. Im using the latest version of chrome and osu! cutting edge.

Video or screenshot showing the problem:

https://youtu.be/80kvBzRY-Uk

You probably wont have to watch the whole video. Just the parts where I open up chrome and show you the download not working are relevant.


osu! version: 20150624.1cuttingedge
VeilStar
Seems like you can't reach the beatmap server.
It's working fine here, not sure what's up.

Can you route trace and ping bm4.ppy.sh through the command promt and post the results here?
Topic Starter
catron44
C:\Users\User>ping bm4.ppy.sh

Pinging bm4.ppy.sh [192.99.201.125] with 32 bytes of data:
Reply from 192.99.201.125: bytes=32 time=559ms TTL=52
Reply from 192.99.201.125: bytes=32 time=536ms TTL=52
Reply from 192.99.201.125: bytes=32 time=533ms TTL=52
Reply from 192.99.201.125: bytes=32 time=540ms TTL=52

Ping statistics for 192.99.201.125:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 533ms, Maximum = 559ms, Average = 542ms


__________________


Tracing route to bm4.ppy.sh [192.99.201.125]
over a maximum of 30 hops:

1 3 ms 1 ms 1 ms NETCOMM [10.1.1.1]
2 9 ms 10 ms 10 ms lo0.bng1.syd4.on.ii.net [150.101.32.83]
3 9 ms 10 ms 9 ms ae7.cr1.syd4.on.ii.net [150.101.34.28]
4 10 ms 20 ms 10 ms ae5.br1.syd4.on.ii.net [150.101.33.48]
5 158 ms 156 ms 157 ms te0-1-1-3.br2.lax1.on.ii.net [150.101.33.195]
6 157 ms 157 ms 157 ms any2ix.coresite.com [206.72.210.214]
7 245 ms 246 ms 216 ms nwk-2-6k.nj.us [198.27.73.193]
8 * * * Request timed out.
9 322 ms 322 ms 324 ms bhs-3a-a9.qc.ca [198.27.73.94]
10 564 ms 542 ms 567 ms bm4.ppy.sh [192.99.201.125]

Trace complete.


This last trace route took a VERY long time
C:\Users\User>
TheVileOne
That's a long ping time. Probably an issue with your ISP or some other random routing issues that are temporary. It's probably resolved by now.
Please sign in to reply.

New reply