I spent a lot of time getting this right years ago and have worked a lot with delancer to do that and have done a lot of my own debugging. I need it for work so I don't play around.
It has been mostly good for me still but has dropped off a little bit lately, mostly late night and early morning. They are upgrading some equipment so likely you are experiencing that they have routers offline but the low end techs in the field never know what the managers and engineers are doing so they just want to replace the modem or the wire.
I had not had a single issue that lasted more than a couple of seconds for the last year plus. But my new location is very close to their hub so that helps. Less chance of issues with cables in the streets.
A lot of the time that they have issues it is not on their end, but on the U.S. side, at least for me. I have a higher speed connection and it drops my link directly at a U.S. location (Columbus Net) in Florida so that my IP actually appears as if it is from them. And I run pings every time it goes out and what I find most of the time is I can ping to Delancer and to Colubmus Net, but nothing beyond them. So calling Delancer in that case won't help and the low-end techs won't know anything.
I usually talk to the manager directly when I have to and if it is something on their end he will actually know about it already or start figuring it out. They all know me by now as I was a constant complainer in the beginning but since I have also helped them out with some tech stuff so it has become a good relationship and I get the attention of the right people when I call.
Some things you can ping to see where your problem might be.
1. your router - don't know your router's IP but you should know it. If you can't even ping your router then reset/fix the router.
2. your modem - don't know your's either but you can find it if you do a tracert to anything (e.g. tracert
Google). The modem will be the second IP address on the list. If you can't ping the modem then reset it and if it is still no good call delancer.
3. delancer (router at their office). 10.9.10.1 is the IP for the faster connection. The slower connections route to a different device. I don't remember that IP but if you look at tracert it will be the third IP in the list. If you can't ping delancer then reset the modem and if still no good call delancer.
4. Columbus Net. If you have the fast connection you are getting dropped here. 69.79.26.101. I'm pretty sure you can ping them even if you aren't on the fast connection as I think they are open to the internet. If you were pinging delancer but not Columbus Net the problem could be delancer but not on your end. It would be on their end at the office or beyond that point or the problem could be with Columbus Net. Either way there is nothing you can do and it won't help to call delancer. If they aren't already aware of the problem on their end they will be soon enough. The last thing you want is for them to mess with or switch out your working modem.
5.
Google. Just anything on the other side of Columbus Net. If you can get to Columbus Net but not google then the problem is Columbus Net. But then probably your DNS also isn't working so you'll find it hard to get anywhere if you don't know the IP which you probably don't for most web sites and for email and stuff. At this point there is nothing delancer can do.
Also, I have noticed sometimes there are issues with DNS even though connectivity is good. I don't accept the DNS defaults that pass down from the modem to the router. I set my primary DNS in my router to 8.8.8.8. It is very reliable. I set the secondary to 10.9.10.1. The secondary is at delancer. That way if the primary is unreachable because of a problem with Columbus Net I can still resolve and get to Dominican web sites. Obviously if Columbus Net is down I can't get to anything outside of the DR anyway.
