| Blocked address range? I use Millenicom over a Sprint tower, I think this is the appropriate forum.
Yesterday I lost the ability to connect to a site with an ip of 72.20.28.xxx.
A ping shows "Reply from 144.232.3.58: Destination net unreachable."
I get this with any 72.20 address as well as 72.30.
Is this a temporary problem or is there some type of block in place?
If its a block, could 72.20.28.xxx be excluded?
Thanks,
Chuck |
|
Reviews:
 ·SureWest Internet
| I'm showing the same here, but i'm able to ping the site from all my servers just fine.
From Sprint
Pinging 72.20.28.20 with 32 bytes of data:
Reply from 144.232.23.103: Destination net unreachable.
Reply from 144.232.23.103: Destination net unreachable.
Request timed out.
Request timed out.
Ping statistics for 72.20.28.20:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Tracing route to 72.20.28.20 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1
2 80 ms 71 ms 63 ms 68.28.81.69
3 86 ms 88 ms 90 ms 68.28.81.91
4 114 ms 193 ms 76 ms 68.28.83.54
5 94 ms 67 ms 67 ms 68.28.87.9
6 * * * Request timed out.
7 73 ms 66 ms 69 ms 68.28.85.69
8 sl-crs1-kc-0-0-0-1.sprintlink.net [144.232.23.103] reports: Destination ne
t unreachable.
Trace complete.
From one of my servers.
powerspec@rtorrent:~$ ping 72.20.28.20
PING 72.20.28.20 (72.20.28.20) 56(84) bytes of data.
64 bytes from 72.20.28.20: icmp_seq=1 ttl=52 time=87.8 ms
64 bytes from 72.20.28.20: icmp_seq=2 ttl=52 time=87.4 ms
64 bytes from 72.20.28.20: icmp_seq=3 ttl=52 time=87.6 ms
64 bytes from 72.20.28.20: icmp_seq=4 ttl=52 time=87.4 ms
^C
--- 72.20.28.20 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3014ms
rtt min/avg/max/mdev = 87.432/87.614/87.848/0.163 ms
powerspec@rtorrent:~$ traceroute 72.20.28.20
traceroute to 72.20.28.20 (72.20.28.20), 30 hops max, 40 byte packets
1 69.197.175.113 (69.197.175.113) 0.652 ms 1.073 ms 1.524 ms
2 69.30.209.125 (69.30.209.125) 0.551 ms 0.768 ms 0.946 ms
3 upnllc.com.108.82.208.in-addr.arpa (208.82.108.201) 0.300 ms 0.294 ms 0.269 ms
4 ge-6-14.car1.KansasCity1.Level3.net (4.53.32.25) 0.476 ms 0.491 ms 0.546 ms
5 ae-5-5.ebr2.Dallas1.Level3.net (4.69.135.230) 15.061 ms 15.035 ms 15.120 ms
6 ae-2-70.edge2.Dallas3.Level3.net (4.69.145.76) 10.187 ms ae-3-80.edge2.Dallas3.Level3.net (4.69.145.140) 26.834 ms ae-1-60.edge2.Dallas3.Level3.net (4.69.145.12) 10.262 ms
7 abovenet-levle3-xe.dallas3.level3.net (4.68.63.38) 10.253 ms 10.221 ms 10.288 ms
8 xe-1-2-0.er1.iah1.us.above.net (64.125.30.57) 15.734 ms 15.896 ms 15.872 ms
9 xe-1-0-0.er2.iah1.us.above.net (64.125.28.2) 15.855 ms 15.815 ms 15.799 ms
10 xe-2-2-0.er2.lax9.us.above.net (64.125.30.50) 47.966 ms 47.928 ms 47.641 ms
11 * * *
12 edge14-ge.lax1.staminus.net (72.20.0.25) 49.846 ms 49.824 ms 49.809 ms
13 * * *
14 . (72.20.5.110) 51.813 ms 50.742 ms 52.103 ms
15 i.hacked.the.inter.n3t.cn (72.20.28.20) 87.888 ms 87.435 ms 88.759 ms
Not the best RDNS name, plus a china domain?
If this is your server/host, have you talked to them?
Whois
OrgName: Staminus Communications
OrgID: STAMIN-2
Address: 502 S. Harbor Blvd.
City: Fullerton
StateProv: CA
PostalCode: 92832
Country: US
NetRange: 72.20.0.0 - 72.20.63.255
CIDR: 72.20.0.0/18
NetName: STAMINUS-COMMUNICATIONS
NetHandle: NET-72-20-0-0-1
Parent: NET-72-0-0-0-0
NetType: Direct Allocation
NameServer: NS1.STAMINUS.NET
NameServer: NS2.STAMINUS.NET
Comment:
RegDate: 2004-12-15
Updated: 2009-11-30
OrgAbuseHandle: ABUSE2456-ARIN
OrgAbuseName: ABUSE
OrgAbusePhone: +1-949-202-5305
OrgAbuseEmail: abuse@staminus.net
OrgNOCHandle: NOC11206-ARIN
OrgNOCName: NOC
OrgNOCPhone: +1-949-202-5305
OrgNOCEmail: support@staminus.net
OrgTechHandle: TECH380-ARIN
OrgTechName: TECH
OrgTechPhone: +1-949-202-5305
OrgTechEmail: support@staminus.net
--
»twitter.com/powerspec | »blog.kcmogaming.net | »speedtest.kcmogaming.net
Home Internet: Sprint Mobile Broadband, DSL line: AT&T 6/768
Server: 100Mbps with Cogent/Level3, Work: 750Mbps Total with AT&T and EverestKC/Surewest |
|
| reply to Chuck35
I thought I was alone with this issue. I've had the same problem for a few days now. Whole ranges are unreachable with my Sprint service. Right now, the affected hosts seem to be Gigeservers and Staminus. I can reach these sites via proxy so they're not down.
Using Sprint's Looking Glass service (»www.sprint.net/lg/) I can't ping or traceroute nearly anything hosted on Gigeservers and Staminus regardless of the Sprintlink server origin chosen. I don't see any maintenance windows in their list that'd indicate an issue that would be related to this problem.
said by Chuck35:A ping shows "Reply from 144.232.3.58: Destination net unreachable." That IP reverses to sl-crs3-fw-0-1-2-0.sprintlink.net. Doing my own traceroutes to affected sites, it dies at sl-crs1-kc-0-0-15-0.sprintlink.net or something similar depending on my own ip.
I wonder if Sprint's having peering issues or something. Like the Cogent issue from a year or two ago... |
|
| I have the same problem. I use an air card from Sprint and I can not reach any sites hosted by "STAMINUS-COMMUNICATIONS". I have called Sprint multiple times and they tell me it's not there fault!! If anyone has had luck figuring this out please e-mail me at aeroshade@hotmail.com THANKS!! |
|
 Jim_in_VA
join:2004-07-11
Cobbs Creek, VA
kudos:4 | I have no problem accessing any site related to Staminus Commications via Google .. all of them load just fine
--
... need help? »evdo-tips.com/ |
|
| reply to Chuck35
Are you on Sprint? |
|
|
|
1 edit | i cant seem to delete this post |
|
| reply to Aeroshade
said by Aeroshade :
Are you on Sprint?
I'm on Sprint via Millenicom, a third party reseller.
The block appears to be gone now. |
|
