I have been trying for weeks to get on Sprinco's website, with no luck. I have tried from my tablet and my laptop. I have tried different browsers, no luck. Has anyone else had this problem? Is Sprinco still in business?
Came straight up for me.
http://www.sprinco.com/
Doesn't work for me at all.
Perfect here.
No issue for me
It worked for me. Check here: http://www.downforeveryoneorjustme.com/
Try clearing your cache and browser history.
.
Either of you guys that can't get to it familiar with ping or trace route?
Took my tablet to a local McDonalds and got on their Wifi( a different provider than mine) and got on Sprinco's website with no problem. I wonder if my provider had some wonky filter that is stopping it?
Came right up for me on our desk top
SavageOne,
I can't find much about Windstream blocking access to websites or filtering, unless the account owner creates the filters.
If the problem persists, then you might contact you ISP. Or, if you are adventuresome, here are the steps I would take:
Check domain name resolution. Using a utility, like nslookup on the command line/prompt, check to ensure the domain name actually resolves to an address. Here is what I get:
[fs-mbp-2:~] Yes, Master? nslookup sprinco.com
Server: 10.0.0.1
Address: 10.0.0.1#53
Non-authoritative answer:
Name: sprinco.com
Address: 216.222.204.91
[fs-mbp-2:~] Yes, Master?
If the name doesn't resolve, you need to work with your ISP to fix this issue. If you are comfortable doing a local over-ride, you could change your local nameserver settings to point to Google's nameservers at 8.8.8.8
If it does resolve, then on to the next step, ping:
[fs-mbp-2:~] Yes, Master? ping sprinco.com
PING sprinco.com (216.222.204.91): 56 data bytes
64 bytes from 216.222.204.91: icmp_seq=0 ttl=57 time=176.726 ms
64 bytes from 216.222.204.91: icmp_seq=1 ttl=57 time=73.497 ms
64 bytes from 216.222.204.91: icmp_seq=2 ttl=57 time=72.844 ms
^C
--- sprinco.com ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 72.844/107.689/176.726/48.817 ms
[fs-mbp-2:~] Yes, Master?
If this works, then the site should load fine. If not, then we need to figure out if there is a routing issue. For this we will use traceroute*:
[fs-mbp-2:~] Yes, Master? traceroute sprinco.com
traceroute to sprinco.com (216.222.204.91), 64 hops max, 52 byte packets
1 XXXXXXXXXX (10.0.0.1) 1.069 ms 0.893 ms 0.754 ms
2 XXX.XXX.XXX.XXX (XXX.XXX.XXX.XXX) 24.381 ms 24.212 ms 23.685 ms
3 xxx-xxx.inet.xxx.net (XXX.XXX.XXX.XXX) 23.418 ms 24.098 ms 24.310 ms
4 xxx-xxx.inet.xxx.net (XXX.XXX.XXX.XXX) 64.639 ms 65.600 ms 83.346 ms
5 209.211.30.42 (209.211.30.42) 66.196 ms 69.148 ms 65.642 ms
6 ten1-7-4.upa-core.expedient.com (209.166.144.210) 71.041 ms 70.211 ms 71.079 ms
7 myhostcenter-gw-primary.cust.e-xpedient.com (66.11.1.179) 70.920 ms 70.452 ms 70.154 ms
[fs-mbp-2:~] Yes, Master?
I obfuscated the first couple of lines of the traceroute in a futile attempt to mask my identity. And, my trace was swallowed by myhostcenter-gw-primary. Yours will probably do the same.
*traceroute, I think is tracert or trace-rt on Windows.
If you aren't familiar with the command line/prompt, give customer service a call for your ISP.