You are not logged in. Please login or register.
RME User Forum → RME Website → Issues connecting to rme-audio.de
I can reach RME fine, but maybe this is interesting, if I use my VPN I have the same issue as everybody. Always had that, thought it was some spam protection
To narrow down whether it's a DNS or routing issue, try the following:
Check which IP your Provider's DNS resolver returns:
nslookup rme-audio.deThen check against public resolvers directly:
nslookup rme-audio.de 8.8.8.8
nslookup rme-audio.de 1.1.1.1If the IPs differ, DNS propagation is not complete in your region yet.
If the IP is correct but the site is still unreachable, run a traceroute to see where the connection drops:
Windows:
tracert rme-audio.demacOS/Linux:
traceroute rme-audio.deYou can also check reachability from multiple global locations at:
https://check-host.net/check-http?host=rme-audio.de
PS: 301 (Moved Permanently) means: all fine - http is redirected to https correctly...
I also can't open it. I have cloudflair dns. 1.1.1.1 and 1.0.0.1
nslookup same on both dns
Non-authoritative answer:
Name: rme-audio.de
Address: 83.138.85.194
tracert is getting a lot of timeouts
1 <1 ms <1 ms <1 ms 192.168.2.1
2 4 ms 2 ms 2 ms 86.32.64.1
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
Another thing: i've told my brother who lives in the same city as i to open the website and it works for him.
My tracert
8 41 ms 38 ms 37 ms de-cix.hostnet.de [80.81.195.124]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
I can access it from my Android Samsung phone over my WIFI. Still can't connect from my two PCs.
C:\Users\Admin>ping rme-audio.de
Pinging rme-audio.de [83.138.85.194] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 83.138.85.194:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Thermaltake, Elf: So its clearly a routing issue, not a DNS issue.
However, without further information (I dont want dive to deep into this), it is just a guess with around 30% possibility.
What I can say: Serbia and Croatia are known for spam traffic from point of an ISP - of course, this has nothing to do with yourself...
@Thermaltake
Your provider (86.32.64.1 = A1 Hrvatska) cannot establish a route to hop3.
- Flush your routers routing table (turn off the router for a few minutes) to obtain a new IP, and the router establishes new routes to germany
- Ask your provider if they block traffic to 83.138.85.194
- Ask RME if the source 86.32.x.x is blocked (by their provider/waf/fw)
@Elf
- Unknown what provider/source IP range you use (your brother probably uses another one?)
- Try the same first: Flush your routers routing table (turn off the router for a few minutes) to obtain a new IP, and the router establishes new routes to germany
- Your traceroute breaks after hop 8 (de-cix is already in frankfurt)
- Possibleyour source IP Range is blocked by RME or by their provider/waf/fw
I can access it from my Android Samsung phone over my WIFI. Still can't connect from my two PCs.
Restart router and both PCs
Thermaltake, Elf: So its clearly a routing issue, not a DNS issue.
@Thermaltake
Your provider (86.32.64.1 = A1 Hrvatska) cannot establish a route to hop3.
- Flush your routers routing table (turn off the router for a few minutes) to obtain a new IP, and the router establishes new routes to germany
- Ask your provider if they block traffic to 83.138.85.194
- Ask RME if the source 86.32.x.x is blocked (by their provider/waf/fw)
I am not on A1... Telemach.
I tried on my mobile phone via mobile internet which is totally different network, also not working. I think it has something to do with their hosting.
I send message to them, hopefully someone could help solve this problem.
C:\Users\Admin>ping rme-audio.de
Pinging rme-audio.de [83.138.85.194] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.Ping statistics for 83.138.85.194:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Canada should work. See here:
https://check-host.net/check-http?host=rme-audio.de
Croatia, not working. At least to me.
lifeguardlloyd wrote:C:\Users\Admin>ping rme-audio.de
Pinging rme-audio.de [83.138.85.194] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.Ping statistics for 83.138.85.194:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),Canada should work. See here:
Nope!
Nope!
ping = ICMP and says absolutely nothing(!) if a website can be reached or not (ICMP can be blocked on every host/firewall/whatever although TCP (http(s)) is possible)
Canada works! (but nobody can guess your source IP/ISP).
My traceroute from 208.91.104.114 (Fortinet Inc. Vancouver/Burnaby, Kanada) to rme-audio.de, using Probe 07a043be-b00b-5105-bbfd-ce5d544a4d8c from Fortinet...
RESOLVED rme-audio.de TO 83.138.85.194
STARTED QUERY AT 2026/03/07 21:08:32 UTC
traceroute to 83.138.85.194 (83.138.85.194), 20 hops max, 60 byte packets
1 _gateway (208.91.104.113) 0.382 ms 0.305 ms
2 100.114.63.1 (100.114.63.1) 0.274 ms 0.257 ms
3 100.114.63.2 (100.114.63.2) 0.326 ms 0.367 ms
4 van-b1-link.ip.twelve99.net (62.115.154.168) 4.909 ms 4.883 ms
5 sea-b4-link.ip.twelve99.net (62.115.138.40) 6.994 ms 6.965 ms
6 sea-b1-link.ip.twelve99.net (62.115.132.157) 4.790 ms 4.763 ms
7 * *
8 * *
9 ewr-b12-link.ip.twelve99.net (62.115.135.121) 64.629 ms 64.606 ms
10 as33891-ic-389901.ip.twelve99-cust.net (62.115.41.199) 64.813 ms 64.786 ms
11 ae25-2093.fra30.core-backbone.com (81.95.9.194) 147.221 ms 147.164 ms
12 core-backbone.hostnet.de (81.95.2.30) 155.243 ms 155.227 ms
13 ledaba.han-solo.net (83.138.85.194) 155.760 ms 155.743 ms
Completed in 12.60s-> no problem.
So, what do I do?
lifeguardlloyd wrote:Nope!
ping = ICMP and says absolutely nothing(!) if a website can be reached or not (ICMP can be blocked on every host/firewall/whatever although TCP (http(s)) is possible)
Canada works! (but nobody can guess your source IP/ISP).
My traceroute from 208.91.104.114 (Fortinet Inc. Vancouver/Burnaby, Kanada) to rme-audio.de, using Probe 07a043be-b00b-5105-bbfd-ce5d544a4d8c from Fortinet...
RESOLVED rme-audio.de TO 83.138.85.194 STARTED QUERY AT 2026/03/07 21:08:32 UTC traceroute to 83.138.85.194 (83.138.85.194), 20 hops max, 60 byte packets 1 _gateway (208.91.104.113) 0.382 ms 0.305 ms 2 100.114.63.1 (100.114.63.1) 0.274 ms 0.257 ms 3 100.114.63.2 (100.114.63.2) 0.326 ms 0.367 ms 4 van-b1-link.ip.twelve99.net (62.115.154.168) 4.909 ms 4.883 ms 5 sea-b4-link.ip.twelve99.net (62.115.138.40) 6.994 ms 6.965 ms 6 sea-b1-link.ip.twelve99.net (62.115.132.157) 4.790 ms 4.763 ms 7 * * 8 * * 9 ewr-b12-link.ip.twelve99.net (62.115.135.121) 64.629 ms 64.606 ms 10 as33891-ic-389901.ip.twelve99-cust.net (62.115.41.199) 64.813 ms 64.786 ms 11 ae25-2093.fra30.core-backbone.com (81.95.9.194) 147.221 ms 147.164 ms 12 core-backbone.hostnet.de (81.95.2.30) 155.243 ms 155.227 ms 13 ledaba.han-solo.net (83.138.85.194) 155.760 ms 155.743 ms Completed in 12.60s-> no problem.
I'm not sure what to do. This has been going on for too long. I can get to every other website I want, just not RME. Wierd.
So you had this issue already for more than one week?
Went to my friend yesterday he is on A1 Hrvatska, and on his PC page is opening normally. I am on Telemach Hrvatska, still nothing.
It looks like on some providers it's working, on some still not.
So you had this issue already for more than one week?
Yes! Most frustrating!
Someone from RME did send me drivers for my new Babyface; that was appreciated.
Same from your phone or another PC? Have you tried to ping?
Same from your phone or another PC? Have you tried to ping?
See above my latest ping. All computers. PC desktop and laptop, iPad, and Android Samsung phone. Note: on data, I get some limited access.
I have reset my home router twice - no luck.
Still not working in Serbia, tried with two different providers.
RME Support wrote:Same from your phone or another PC? Have you tried to ping?
See above my latest ping. All computers. PC desktop and laptop, iPad, and Android Samsung phone. Note: on data, I get some limited access.
I have reset my home router twice - no luck.
Have you tried contacting help at your internet provider? The fact when you're on mobile data, but not your home internet, you get some access points to a network issue closer to your end. If it was closer to the RME host end we'd all be having issues.
One thing that might be interesting is if someone from RME could run a traceroute from the web host back to one of the failing client IPs. That might highlight where the packets are getting dropped if it's a return-path problem.
@lifeguardlloyd,
In #55: "I can access it from my Android Samsung phone over my WIFI. Still can't connect from my two PCs."
In #71: "All computers. PC desktop and laptop, iPad, and Android Samsung phone. Note: on data, I get some limited access"
Quite confusing... Did you mean over data via android mobile in #55?
However, if you could tell what Provider(s) you use, it should be possible to check if the routes are present...
---
@Elf,
can you tell wich provider you use? And which provider your brother uses?
@lifeguardlloyd,
In #55: "I can access it from my Android Samsung phone over my WIFI. Still can't connect from my two PCs."
In #71: "All computers. PC desktop and laptop, iPad, and Android Samsung phone. Note: on data, I get some limited access"
Quite confusing... Did you mean over data via android mobile in #55?
However, if you could tell what Provider(s) you use, it should be possible to check if the routes are present...---
Bell MTS ManitobaCubase, FF400, Babyface Pro FS, PC, Cubase Pro 15, Wavelab
---
@Elf,
can you tell wich provider you use? And which provider your brother uses?
SBB cable - both my brother and i
Yettel mobile - my provider
EDIT: It's working now! 
It works for me now too.
Seems the providers got the memo eventually...
It's finally starting to work again. Not all the pages. There's hope!
Seems the providers got the memo eventually...
nice. ...surprise surprise 
RME User Forum → RME Website → Issues connecting to rme-audio.de
Powered by PunBB, supported by Informer Technologies, Inc.